From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: Patrick Mochel <mochel@osdl.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: RE: Subtle semantic issue with sleep callbacks in drivers
Date: 14 Apr 2003 21:18:27 +0200 [thread overview]
Message-ID: <1050347907.5575.89.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A261@orsmsx401.jf.intel.com>
> All I am saying is that on Windows, the driver gets no help from the
> BIOS, APM, or ACPI, but yet it restores the video to full working
> condition. I understand that this sounds complicated, but since there is
> an implementation that already does this then I think we have to assume
> it's possible. :) Perhaps we should start with older, simpler gfx hw, or
> maybe POST the bios, but only as an interim solution until gfx drivers
> get better in this area.
It's definitely possible as MacOS does that as well. But I doubt
the card vendors will ever provide us with the necessary informations...
Ben.
next prev parent reply other threads:[~2003-04-14 19:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:07 Subtle semantic issue with sleep callbacks in drivers Grover, Andrew
2003-04-14 19:18 ` Benjamin Herrenschmidt [this message]
2003-04-14 19:56 ` Alan Cox
2003-04-14 21:07 ` Kernel Sockets Programming: closing sockets? Lamont Granquist
2003-04-23 15:34 ` Subtle semantic issue with sleep callbacks in drivers Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 21:09 Grover, Andrew
2003-04-16 18:39 ` Patrick Mochel
2003-04-16 19:36 ` Benjamin Herrenschmidt
2003-04-17 13:35 ` Alan Cox
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
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
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=1050347907.5575.89.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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;
as well as URLs for NNTP newsgroup(s).