From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Theodore Tso <tytso@mit.edu>, Tomas Carnecky <tom@dbservice.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5/5] ACPI: add DMI to enable OSI(Linux) on ThinkPad T61
Date: Tue, 22 Jan 2008 00:37:53 -0500 [thread overview]
Message-ID: <200801220037.53381.lenb@kernel.org> (raw)
In-Reply-To: <20080121193755.GA11492@srcf.ucam.org>
On Monday 21 January 2008 14:37, Matthew Garrett wrote:
> On Mon, Jan 21, 2008 at 02:00:41PM -0500, Theodore Tso wrote:
>
> > Well, unless until Video card vendors give us their secret interfaves
> > to reinitialize their cards, we're never going to figure it out,
> > right?
>
> There's (not yet mainline) code to do this on Intel, and it looks like
> AtomBios based ATIs (some r400s, all r500s and later) should be trivial.
> The work the Nouveau people have been doing is also very promising, and
> I suspect we can do cold boot there before too long. I was going to do
> some work on this this week, but my ATI machine got stolen...
>
> > At least for vendors like Lenovo, where some laptops will be
> > shipping with Intel cards where we will eventually be able do our own
> > video reinit after suspend, and some with Nvidia chipsets where it
> > doesn't seem terribly likely until someone at Nvidia has a change of
> > heart, the BIOS won't be able to use the "please reinit video" as a
> > general "Linux" indicator, since they will need to support laptops
> > with Good as well as Evil graphics chipsets. :-)
>
> The problem is that we don't inherently know if we can support
> reinitialising video natively until the video driver is loaded, and
> there's a high probability that that's going to come from a module.
> We're already executing ACPI by then, so the firmware's had the
> opportunity to stash an incorrect value and can blow everything up later
> on.
Right, if we go down this path, we'd have to do it as a boot parameter
in order to enable/disable the hook before any platform AML
gets a chance to see it.
note that acpi_osi=string and acpi_osi=!string
are available starting in 2.6.23. You get to add
up to 1 string, and you get to remove as many pre-existing
strings as you like.
of course, this trick would require the distro installer
to know tha a native-video driver were present, and
modify the bootparms accordingly.
> If vendors want their laptops to work on Linux, then the best thing
> they can do is help us get our drivers working properly.
True. For Intel graphics, Intel/OTC is working on getting this fixed.
It has not been a quick fix -- the pipeline is long...
Maybe the quick fix is to enhance the workarounds
in s2ram and simply deal with it that way until native video
drivers are available?
> Now, stuff like a standardised entrypoint into ACPI that reinitialises
> the video - that would be helpful, since we could choose whether to call
> it or not which means whether or not something gets screwed up is
> determined by us and not the vendor.
Even if we (Linux) proposed this and it got added to the spec,
it wouldn't have any real effect b/c windows doesn't need it,
so most machines wouldn't implement it. Smarter native video
drivers is clearly the preferred path.
-Len
next prev parent reply other threads:[~2008-01-22 5:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 10:24 [PATCH 0/5] improved knobs to deal with OSI(Linux) Len Brown
2008-01-17 10:24 ` [PATCH 1/5] DMI: move dmi_available declaration to linux/dmi.h Len Brown
2008-01-17 10:24 ` [PATCH 2/5] DMI: create dmi_dump_entries() Len Brown
2008-01-17 10:24 ` [PATCH 3/5] ACPI: use dmi_dump_entries() instead of requesting dmidecode output Len Brown
2008-01-17 10:24 ` [PATCH 4/5] ACPI: OSI(Linux) cmdline and DMI BIOS workarounds Len Brown
2008-01-17 10:24 ` [PATCH 5/5] ACPI: add DMI to enable OSI(Linux) on ThinkPad T61 Len Brown
2008-01-17 12:28 ` Matthew Garrett
2008-01-17 14:46 ` Henrique de Moraes Holschuh
2008-01-17 20:04 ` Len Brown
2008-01-17 21:31 ` Theodore Tso
2008-01-19 7:40 ` Len Brown
2008-01-19 12:08 ` Henrique de Moraes Holschuh
2008-01-19 14:17 ` Theodore Tso
2008-01-19 15:33 ` Henrique de Moraes Holschuh
2008-01-19 15:43 ` Matthew Garrett
2008-01-19 23:19 ` Theodore Tso
2008-01-20 4:13 ` Len Brown
2008-01-20 11:16 ` Rafael J. Wysocki
2008-01-20 12:03 ` Tomas Carnecky
2008-01-20 18:31 ` Len Brown
2008-01-20 19:21 ` Tomas Carnecky
2008-01-21 1:52 ` Theodore Tso
2008-01-21 9:50 ` Matthew Garrett
2008-01-21 19:00 ` Theodore Tso
2008-01-21 19:37 ` Matthew Garrett
2008-01-22 5:37 ` Len Brown [this message]
2008-01-20 19:49 ` Henrique de Moraes Holschuh
2008-02-18 16:58 ` Thomas Renninger
2008-02-18 19:17 ` Henrique de Moraes Holschuh
2008-02-19 0:00 ` Thomas Renninger
2008-02-19 0:26 ` Theodore Tso
2008-02-19 6:34 ` Thomas Renninger
2008-02-19 13:24 ` Henrique de Moraes Holschuh
2008-02-19 10:26 ` Thomas Renninger
2008-02-19 14:24 ` Henrique de Moraes Holschuh
2008-02-20 1:43 ` Thomas Renninger
2008-02-20 2:47 ` Henrique de Moraes Holschuh
2008-01-19 7:50 ` [PATCH 6/5] ACPI: DMI blacklist for OSI(Linux) Len Brown
2008-01-19 8:16 ` Andi Kleen
2008-01-20 4:18 ` Len Brown
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=200801220037.53381.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=tom@dbservice.com \
--cc=tytso@mit.edu \
/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).