From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: acpi-devel@lists.sourceforge.net
Cc: "Matthias Hentges" <mailinglisten@hentges.net>,
"Oliver Dawid" <od@fet.uni-hannover.de>,
"Stefan Dösinger" <stefandoesinger@gmx.at>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: Samsung P35 and S3 suspend
Date: Wed, 22 Dec 2004 03:06:01 +0100 [thread overview]
Message-ID: <41C8D689.3020502@gmx.net> (raw)
In-Reply-To: <41C1CFA2.20304@gmx.net>
Carl-Daniel Hailfinger wrote:
> 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.
>
> OK, it is working perfectly with the latest Linus -bk tree and
> everything configured in (SuSE .config, comparable to allmodconfig).
It turns out that (at least for 2.6.10-rc3 and later) the kernel
resumes from S3 perfectly regardless of .config as long as
- no framebuffer console is activated (kernel param video=vesa:off )
- pci-resume-2.6.10.patch and resume-finish-split-2.6.10.patch
are applied
- suspend and resume happen with an active TEXT console (chvt 2)
- VESA registers are saved before suspend
- the radeon card is POSTed after resume
- the VESA registers are restored after that
- now you are free to change back to X if you want.
You do NOT need
- a patched X server
- a special kernel .config
- sacrifices of any kind.
See my other mail to acpi-devel for details about how to save/restore
the VESA registers and POST the card.
Question for the framebuffer experts: Is it possible to forbid access
to the video card after resume until the card has been POSTed and all
registers are restored? Any access to the card before that will freeze
the machine.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
parent reply other threads:[~2004-12-22 2:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <41C1CFA2.20304@gmx.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C8D689.3020502@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglisten@hentges.net \
--cc=od@fet.uni-hannover.de \
--cc=stefandoesinger@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox