Hi! > > > > Here's prototype code for swsusp3. It seems to work for me, but don't > > > > try it... yet. Code is very ugly at places, sorry, I know and will fix > > > > it. This is just proof that it can be done, and that it can be done > > > > without excessive ammount of code. > > > > > > No comments on the code sorry. Instead I want to ask, could you please > > > find a different name? swsusp3 is going to make people think that it's > > > Suspend2 redesigned. Since there hasn't been a swsusp2 (so far as I > > > know), how about using that name instead? At least then we'll clearly > > > differentiate the two implementations and you won't confuse/irritate > > > users. > > > > swsusp2 can't be used, it is already "taken" by suspend2 (25000 hits > > on google). I was actually hoping that you would release suspend4 > > (using swsusp3 infrastructure) :-). > > You could reclaim it. There are 10 times as many hits (239,000) for > suspend2, and I've never wanted it to be called swsusp2 anyway :). As > for suspend4, at the moment, I'm not planning on ever progressing beyond > 2.x. Sorry, have to ask... "not planning on progressing" == version number stays "2" no matter what changes, or "not planning on progressing" == not plan to use swsusp3/uswsusp infrastructure? > > I guess I could call it "uswsusp". > > u as in micro? Originaly I thought about it as "userland-swsusp", but micro-swsusp sounds nice, too. Pavel -- if you have sharp zaurus hardware you don't need... you know my address
