From: Alan Cox <firstname.lastname@example.org>
To: Patrick Mochel <email@example.com>
Cc: "Grover, Andrew" <firstname.lastname@example.org>,
Benjamin Herrenschmidt <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: RE: Subtle semantic issue with sleep callbacks in drivers
Date: 17 Apr 2003 14:35:50 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Mer, 2003-04-16 at 19:39, Patrick Mochel wrote:
> I completely agree with Andy. We should not re-POST the video hardware, no
> matter what. The idea behind ACPI is that the OS takes care of everything,
> including video save/restore.
Outside of happyville ivory towers you probably have no choice. Only the
BIOS knows stuff like the RAM timings, and some windows drivers just use
the BIOS, others rely on being shipped compiled for the right variant of
card they came with.
We keep the BIOS segment data so you can re-post the card on the 16bit
resume path. Probably there should be a flag for relevant frame buffer
drivers to set that says "don't re-Post but call me later"
> We may not have the documentation to properly do that for all hardware
> currently, but that is something that we have to suck up and deal with.
> For now, we go with hardware that we're able to handle.
Thats pretty close to "there isnt any"
> The drivers that cannot support reinitialization will not be able to
> support suspend-to-RAM. When we get to a point where it really becomes an
> issue (i.e. after we have decent working code), then we concentrate on
> getting the appropriate docuementation (or code itself, source or binary)
> to do it correctly.
X people have been trying to do this for multihead setups for years.
You'll get Matrox, you'll get 3DFX voodoo1/2, you might get early SiS.
Intel - dunno, but the rest - no chance.
> Trying to figure out if we need to POST or not for different hardware,
> based what the driver knows, is going to become quite a mess real fast. I
> don't want to deal with the pain, and would rather take the high ground,
> even if it means suffering in the short term.
Short, long and forever. I agree we want drivers to be able to say "Don't POST
I can hack this one", however we need to accept the real world that most
hardware wants posting and that in many cases its what the windows driver
next prev parent reply other threads:[~2003-04-17 14:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 21:09 Subtle semantic issue with sleep callbacks in drivers Grover, Andrew
2003-04-16 18:39 ` Patrick Mochel
2003-04-16 19:36 ` Benjamin Herrenschmidt
2003-04-17 13:35 ` Alan Cox [this message]
2003-04-17 14:48 ` Jeff Garzik
2003-04-17 15:09 ` John Bradford
2003-04-17 15:09 ` Jeff Garzik
2003-04-17 15:47 ` John Bradford
2003-04-17 15:56 ` Jeff Garzik
2003-04-17 16:24 ` Alan Cox
2003-04-18 7:37 ` Greg KH
2003-04-18 7:51 ` John Bradford
2003-04-18 9:10 ` Russell King
2003-04-18 11:18 ` Alan Cox
2003-04-18 11:30 ` Alan Cox
2003-04-29 8:28 ` Pavel Machek
2003-04-17 14:59 ` John Bradford
2003-04-17 15:04 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:07 Grover, Andrew
2003-04-14 19:18 ` Benjamin Herrenschmidt
2003-04-14 19:56 ` Alan Cox
2003-04-23 15:34 ` Pavel Machek
2003-04-14 17:09 Grover, Andrew
2003-04-14 17:40 ` Benjamin Herrenschmidt
2003-04-23 15:29 ` Pavel Machek
2003-04-14 10:00 Benjamin Herrenschmidt
2003-04-14 10:11 ` Benjamin Herrenschmidt
2003-04-16 18:31 ` Patrick Mochel
2003-04-16 19:29 ` Benjamin Herrenschmidt
2003-04-23 15:32 ` Pavel Machek
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).