From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: corsac@debian.org, ak@linux.intel.com, rui.zhang@intel.com,
nokos@gmx.net, linux-acpi@vger.kernel.org, hmh@debian.org
Subject: Re: Do not return true to all kind of Windows OSI calls
Date: Sat, 2 Aug 2008 18:48:15 +0200 [thread overview]
Message-ID: <200808021848.16457.trenn@suse.de> (raw)
In-Reply-To: <20080802165952.GA30580@srcf.ucam.org>
On Saturday 02 August 2008 06:59:52 pm Matthew Garrett wrote:
> On Sat, Aug 02, 2008 at 06:57:57PM +0200, Thomas Renninger wrote:
> > ThinkPads store OSI calls in separate variables and later
> > check for NT/XP/VISTA specific code to process.
> >
> > I lately saw a line on a ThinkPad checking for XP and VISTA
> > at video device specific code.
> >
> > So currently some ThinkPads run into code paths which should
> > either run on XP or VISTA, but Linux might execute them both
> > or in a way that is not intended by BIOS developers.
>
> Could you please show the code in question? I think you're misdiagnosing
> the issue.
If (CondRefOf (\_OSI, Local0))
{
If (\_OSI ("Windows 2001"))
{
Store (0x01, \WNTF)
Store (0x01, \WXPF)
Store (0x00, \WSPV)
}
If (\_OSI ("Windows 2001 SP1"))
{
Store (0x01, \WSPV)
}
If (\_OSI ("Windows 2001 SP2"))
{
Store (0x02, \WSPV)
}
If (\_OSI ("Windows 2006"))
{
Store (0x01, \WVIS)
}
}
...
# Only process this on XP, not on Linux and Vista
If (LAnd (\WXPF, LNot (\WVIS)))
{
Notify (\_SB.PCI0, Arg1)
}
Else
{
Notify (\_SB.PCI0.VID, Arg1)
}
}
...
# Only process this on XP, not on Linux and Vista
If (LAnd (LNot (\WXPF), \WNTF))
{
Store (0x00, \_SB.PCI0.LPC.C4C3)
}
...
Device (HPET)
{
Name (_HID, EisaId ("PNP0103"))
Method (_STA, 0, NotSerialized)
{
...
# Only disable HPET on NT, not on Linux
If (LAnd (\WNTF, LNot (\WXPF)))
{
Return (0x00)
}
Amazing, it looks like they already check for Linux by checking if
OSI returned true on two major Windows versions which would indicate
Linux running.
So yes, everything looks fine and it seems this was not luck, but
they already realized Linux does not return true for OSI(Linux)
anymore.
Why must we force vendors to implement such a madness, the OSI
implementation is so wrong.
So this seems to get the state-of-the-art then..., check whether several
Windows versions return true and you do not need to process broken code
which is only intended to run on a very specific broken Windows version.
Thomas
next prev parent reply other threads:[~2008-08-02 17:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 15:37 Check for ACPI backlight support otherwise use vendor ACPI drivers - version 4 Thomas Renninger
2008-08-01 15:37 ` [PATCH 01/10] ACPI: video: Ignore devices that aren't present in hardware Thomas Renninger
2008-08-01 15:37 ` [PATCH 02/10] Check for ACPI backlight support otherwise use vendor ACPI drivers Thomas Renninger
2008-08-04 1:56 ` Zhang Rui
2008-11-14 22:27 ` Bjorn Helgaas
2008-11-16 22:07 ` Thomas Renninger
2008-11-17 19:51 ` Bjorn Helgaas
2008-11-18 2:31 ` Thomas Renninger
2008-08-01 15:37 ` [PATCH 03/10] Acer-WMI: fingers off backlight if video.ko is serving this functionality Thomas Renninger
2008-08-01 21:52 ` Carlos Corbacho
2008-08-01 15:37 ` [PATCH 04/10] asus-acpi: " Thomas Renninger
2008-08-01 15:37 ` [PATCH 05/10] compal: " Thomas Renninger
2008-08-01 15:37 ` [PATCH 06/10] eeepc-laptop: " Thomas Renninger
2008-08-01 15:38 ` [PATCH 07/10] fujitsu-laptop: " Thomas Renninger
2008-08-01 15:38 ` [PATCH 08/10] msi-laptop: " Thomas Renninger
2008-08-01 15:38 ` [PATCH 09/10] sony-laptop: " Thomas Renninger
2008-08-01 15:38 ` [PATCH 10/10] thinkpad_acpi: " Thomas Renninger
2008-08-01 17:50 ` Henrique de Moraes Holschuh
2008-11-08 5:45 ` Len Brown
2008-08-01 20:49 ` Check for ACPI backlight support otherwise use vendor ACPI drivers - version 4 Andi Kleen
[not found] ` <1217632817.4610.6.camel@hidalgo>
2008-08-02 16:57 ` Do not return true to all kind of Windows OSI calls Thomas Renninger
2008-08-02 16:59 ` Matthew Garrett
2008-08-02 16:48 ` Thomas Renninger [this message]
2008-08-02 17:31 ` Matthew Garrett
2008-08-02 17:30 ` Thomas Renninger
2008-08-02 19:48 ` Matthew Garrett
2008-08-03 4:43 ` Henrique de Moraes Holschuh
2008-08-03 6:33 ` Matthew Garrett
2008-08-03 13:31 ` Thomas Renninger
2008-08-03 14:12 ` Matthew Garrett
2008-08-03 16:24 ` Thomas Renninger
2008-08-06 17:12 ` Moore, Robert
2008-08-02 16:57 ` [PATCH 1/2] ACPI: Provide a OSI interface that does not return true for Windows Thomas Renninger
2008-08-02 16:57 ` [PATCH 2/2] patch acpi_lenovo_thinkpad_only_return_vista.patch Thomas Renninger
2008-08-02 16:28 ` Thomas Renninger
2008-08-04 1:16 ` Check for ACPI backlight support otherwise use vendor ACPIdrivers - version 4 Zhang Rui
2008-08-04 6:09 ` Yves-Alexis Perez
2008-08-04 6:20 ` Yves-Alexis Perez
2008-08-04 10:20 ` Thomas Renninger
2008-08-04 10:39 ` Yves-Alexis Perez
2008-08-04 11:19 ` Thomas Renninger
2008-08-04 13:24 ` Matthew Garrett
2008-08-04 13:30 ` Yves-Alexis Perez
2008-08-04 13:40 ` Thomas Renninger
2008-08-04 13:47 ` Yves-Alexis Perez
2008-08-05 0:01 ` Henrique de Moraes Holschuh
2008-08-05 5:55 ` Yves-Alexis Perez
2008-08-05 9:13 ` Thomas Renninger
2008-08-05 12:00 ` Yves-Alexis Perez
2008-08-05 13:37 ` Henrique de Moraes Holschuh
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=200808021848.16457.trenn@suse.de \
--to=trenn@suse.de \
--cc=ak@linux.intel.com \
--cc=corsac@debian.org \
--cc=hmh@debian.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=nokos@gmx.net \
--cc=rui.zhang@intel.com \
/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