[lkml]   [2005]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: swsusp 'disk' fails in bk-current - intel_agp at fault?

    > > > Btw, I dont think that doing selective resume (as opposed to selective
    > > > suspend and Nigel's partial device trees) would be so much
    > > > complicated. You'd always resume sysdevs and then, when iterating over
    > > > "normal" devices, just skip ones not in resume path. It can all be
    > > > contained in driver core I believe (sorry but no patch, for now at
    > > > least).
    > >
    > > :-) I think we can simply make device freeze/unfreeze fast enough.
    > > [We do not need to do full suspend/resume; freeze is enough].
    > It is not suspend/freeze here that gets us but resume and with resume
    > the driver (at least for now) does not have any idea if it is
    > "unfreeze" or "full-resume". I mean I could have serio just ignore
    > "unfreeze" requests (as I doubt anyone would ever try to suspend over
    > PS/2 port ;) ) but I think it should be really handled by the core.

    Please just always do full-resume... for now. Patches that enable you
    to detect "unfreeze" are not in, yet. If something fails, just printk
    with big enough severity and continue, as you don't have method of
    signaling error, anyway.
    People were complaining that M$ turns users into beta-testers...
    ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-04-06 13:31    [W:5.471 / U:0.080 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site