From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [ACPI] Re: [2.5.50, ACPI] link error Date: Tue, 10 Dec 2002 21:40:31 +0100 Sender: linux-kernel-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Message-ID: <20021210204031.GF20049@atrey.karlin.mff.cuni.cz> References: <1039481341.12046.21.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1039481341.12046.21.camel-MMxVpc8zpTQVh3rx8e9g/fyykp6/JSeS3vcXtXqGYxw@public.gmane.org> To: Alan Cox Cc: "Grover, Andrew" , 'Ducrot Bruno' , Pavel Machek , Ducrot Bruno , Patrick Mochel , Linux Kernel Mailing List , ACPI mailing list List-Id: linux-acpi@vger.kernel.org Hi! > > I concur with your pros and cons. This makes me think that if S4BIOS support > > ever gets added, it should get added to 2.4 only. And S4BIOS will never get added to 2.4 since it needs driver model :-(. > That assumes no box exists where S4bios works an S4 doesnt (eg due to > bad tables or "knowing" what other-os does) We have full control over S4 (== swsusp), so we can fix that in most cases. S4BIOS is still little friendlier to the user -- no need to set up swap partition and command line parameter, can't go wrong if you boot without resume=, etc. Pavel -- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic.