Hi! > > That's actually another reason why it'd be good to differentiate between > > 'stopping' a device and 'powering it down'. We can temporarily freeze the > > video device, save it's state, then re-enable it to continue writing to > > the screen. Ditto for the swap device. > > Well, whatever you do, you don't do it by breaking the transition into > different steps. That won't work. > > You enter a state, you always go back to state 0 (resumed) before > entering another one. Period. That's the basis of why I got save_state() > removed in the first place, remember ? > > Just read the paper David did summarizing our discussions, I think it's > pretty clear the kind of callbacks we need. We really should put it somewhere in Documentation/ so this kind of discussion does not repeat... Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
