From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl-Daniel Hailfinger Subject: Re: Re: Samsung P35 and S3 suspend Date: Thu, 16 Dec 2004 19:28:27 +0100 Message-ID: <41C1D3CB.5010805@gmx.net> References: <41BFC3AD.5030001@gmx.net> <41C0FFF3.4010902@gmx.net> <41C19BD8.7050201@gmx.net> <200412161832.09711.stefandoesinger@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <200412161832.09711.stefandoesinger-RbZlAiThDcE@public.gmane.org> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: =?ISO-8859-1?Q?Stefan_D=F6singer?= Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Matthias Hentges , Oliver Dawid List-Id: linux-acpi@vger.kernel.org Stefan Dösinger schrieb: >>OK, I got S3 working with all kernels since 2.6.9 (well, your patches >>had to be modified slightly). Right now I'm running on the latest >>Linus -bk tree. >> >>I will now try other configurations and a full bootup. > > Just a note about 2.6.10-rc2/3 kernels: I also had some Problems with them. > snd-Intel8x0 needs an update concerning PCI config save/restore and ehci-hcd > causes problems after resume. uhci-hcd suspend/resume works for me, except > that I must not plug or unplug usb devices while the system is supended. Could you go into more detail? Changing the hardware config while suspended is obviously not recommended, but what are the exact problems occuring besides that? >>Besides that, I think we could convince the X.Org developers that >>the "get display working" bug is their problem ;-) >>It seems they have merged some suspend/resume bugfixes for Radeon and >>will merge at least one more bugfix in the next few days. Basically, >>it should be possible that the normal Radeon Xserver rePOSTs the card >>itself once it detects a resume event. If that is done properly, we >>could get rid of the hack completely and would only have to live with >>the text console. > > No, I think it's the kernels problem. The various framebuffer drivers should > know how to wake up the card. > There were some discussions on the linux-fbdev-devel list about writing a > lightwhight(20-30k) 8086 emulator for the kernel to avoid real mode hacks. > As far as I know, this should be based on the 8086 emulator XFree/X.org uses. Yes, but for that to work we should have a procedure in place which allows us to get the card working again without having to crash a secondary vesa xserver. If boot-radeon could be extended to do the things the crashing vesa xserver does, we would be much better off. That could be folded a) into the kernel framebuffer drivers b) into the radeon xserver. Regards, Carl-Daniel -- http://www.hailfinger.org/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/