Hi!
>
> On Fri, 25 May 2007, Pavel Machek wrote:
> > >
> > > Equally arguably, we should just have a "resume_late()" call that can be
> > > used to do this after everything is up and running.
> >
> > Yes, we can do that. But userland will see devices "not there" for a
> > few seconds after boot.
>
> No they won't.
>
> Why the HELL cannot you realize that kernel threads are different?
>
> The right thing to do is AND HAS ALWAYS BEEN, to stop and start user
> threads only around the whole thing.
>
> Don't touch those kernel threads. Stop freezing them.
>
> Then, what you do is:
> - stop user space
> - suspend
> - resume
~~~~~~~~~~~
notice how resume of pcmcia card that poor user has needs
userspace. So this does not work.
> - start user space
My proposed solution is "fix pcmcia to load firmware before suspend
even starts"
- HERE
> - stop user space
> - suspend
> - resume
> - start user space
Maybe freezer causes cancer in small children, but lets not blame it
for this.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
