On Sun, Dec 08, 2002 at 08:49:45PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > > > Doesn't that imply your fix is broken to begin with?
> > > > >
> > > > > ACPI/S4 support needs swsusp. ACPI/S3 needs big part of
> > > > > swsusp. Splitting CONFIG_ACPI_SLEEP to S3 and S4 part seems like
> > > > > overdesign to me, OTOH if you do the work it is okay with me.
> > > >
> > > > You broke the design. S3 support was developed long before swsusp was in
> > > > the kernel, and completely indpendent of it. It should have remained that
> > > > way.
> > > >
> > > > S3 support is a subset of what is need for S4 support.
> > >
> > > That's not true. acpi_wakeup.S is nasty piece of code, needed for S3
> > > but not for S4. Big part of driver support is only needed for S3.
> > >
> > > > swsusp is an implementation of S4 support. In theory, there could be
> > > > multiple implementations that all use the same core (saving/restoring
> > > > state).
> > >
> > > There were patches for S4bios floating around, but it never really
> > > worked, IIRC.
> >
> > No. It work. I do not resubmmited patches because I think that
> > swsusp is better.
>
> I think that s4bios is nice to have. Its similar to S3 and easier to
> set up than swsusp... It would be nice to have it.
for me:
pros:
-----
1- it is really really more easier to implement than S4;
2- we can even have it with 2.4 kernels (it seems that it work without
the need of freezing processes, but I suspect that this statement
is 'wrong' by nature).
cons:
-----
1- it is much slower (especially at save time) than your swsusp;
2- end users must setup their systems (need to create a suspend partition,
or to keep a vfat partition as the really first one (/dev/hda1));
3- we use a bios function. Actually, everything can happen...
That why I prefer swsusp at this time, or any other implementation of S4 (I
think about an implementation of S4 via LKCD).
Cheers,
-- Ducrot Bruno http://www.poupinou.org Page profaissionelle http://toto.tu-me-saoules.com Haume page - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/