From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Charl P. Botha" <c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: resource for S3 suspend/resume of Radeon
Date: Mon, 17 Mar 2003 17:26:24 +0100 [thread overview]
Message-ID: <20030317162624.GB2249@hell.org.pl> (raw)
In-Reply-To: <1047916074.28836.58.camel-1Jw6Eky0yc0@public.gmane.org>
Thus wrote Charl P. Botha:
> > Which radeon do you have in mind exactly? I use an M7 LW chip, and I get
> > the following: both in 2.4.x and 2.5.x the display does not power-off when
> You could try using the radeontool (google it) to remedy this.
Thanks, I will. I'm currently trying to deal with it on ACPI level, but
perhaps using radeontool is better.
No that I've tested it: it seems that radeontool goes further than ACPI,
disabling not only the backlight (as my laptop does), but also the LCD
itself. Neat.
> > in S1 (which is, I believe, expected), and during S3 it poweroffs and comes
> > back in, provided I pass the acpi_sleep=s3_bios option.
> Wow, you mean to say that you can flawlessly S3 suspend/resume with
> kernel 2.4? I would assume that this is due to your laptop's support
No, I meant S3 only in 2.5. 2.4 has no S3 code whatsoever, at least AFAIK.
> for S3 in BIOS. Not all laptops have this... see for instance what Ole
> had to do to get his working:
> http://home.cern.ch/mrohne/P2120/P2120_Linux_S3.html
Anyway, since the first 2.5 I used (2.5.59) I am able to suspend-to-RAM,
then resume. Normally, the screen is off, and the keyboard is mute, but
appending acpi_sleep=s3_bios does it for the screen, and reloading the
atkeyb module brings the keyboard back to life. NIC needs several seconds
(and several pings also) to resume (it's a rtl8139 chip).
> Drivers in the new kernel need to be able to suspend/resume (S1, S3 and
> S4) without more than the minimum required support in the BIOS.
S4 is a bit easier. See this: I have radeonfb hard-compiled in the kernel.
When I resume, the kernel that boots first initializes the display
properly, and then the kernel that is read from swap has the display
already running, so it doesn't have to worry about it. I suppose it would
be much harder when radeonfb was compiled as a module. Then, I think that
it's S3 that is the most difficult.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
next prev parent reply other threads:[~2003-03-17 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 14:42 resource for S3 suspend/resume of Radeon Charl P. Botha
[not found] ` <1047912152.28830.32.camel-1Jw6Eky0yc0@public.gmane.org>
2003-03-17 15:34 ` Karol Kozimor
[not found] ` <20030317153434.GB3936-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-03-17 15:47 ` Charl P. Botha
[not found] ` <1047916074.28836.58.camel-1Jw6Eky0yc0@public.gmane.org>
2003-03-17 16:26 ` Karol Kozimor [this message]
[not found] ` <20030317162624.GB2249-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-03-17 16:54 ` Charl P. Botha
2003-03-21 9:26 ` Pavel Machek
2003-03-18 6:36 ` Ole Myren Rohne
2003-03-17 15:35 ` Charl P. Botha
[not found] ` <1047915331.28836.45.camel-1Jw6Eky0yc0@public.gmane.org>
2003-03-17 16:20 ` Ducrot Bruno
2003-03-17 18:12 ` Patrick Mochel
2003-03-17 16:23 ` Ole Myren Rohne
[not found] ` <m3hea29d2d.fsf-ksZHQmIzGzSqwiivBfVWcw@public.gmane.org>
2003-03-17 16:52 ` Charl P. Botha
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=20030317162624.GB2249@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.org \
/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