[lkml]   [2004]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [SoftwareSuspend-devel] 2.6 Suspend PM issues

> > By what was discussed wrt ALSA issue I gather that you still resume _all_
> > drivers after doing the atomic copy?
> >
> > As explained earlier this year, if this is the case, it is firstly
> > unacceptable as it will result in loss of data in many applications and
> > secondly very clumsy.
> >
> > Example With 2.4 OK, with 2.6 It would fail:
> > A datalogger connected to a seral port of a notebook in the field. Data
> > transfer in progress which can be put on hold bo lowering RTS (HW handshake)
> > but _cannot_ be restarted. Battery low, must suspend to change battery, upon
> > resume transfer can continue.
> >
> > Will this be taken care of?

Driver will get enough info in its resume routine ("hey, it is resume,
but it is only resume after atomic copy"), so it can ignore the resume
if it really needs to.

But this is 2.6.11 material.
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-03-22 14:08    [W:0.062 / U:1.140 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site