From: Arjan van de Ven <arjan@infradead.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Pavel Machek <pavel@suse.cz>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST
Date: Mon, 26 May 2008 19:05:53 -0700 [thread overview]
Message-ID: <20080526190553.1d37e17d@infradead.org> (raw)
In-Reply-To: <20080527101302.4bd49e6c.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 27 May 2008 10:13:02 +0900
> BTW, PrimeQuest's firmware is designed in 2.6.18 age and _heavily_
> tested under _OSI("Linux") environments. So, the acpi layer which
> returns _OSI("Linux") is valid for PrimeQuest. I don't hear a major
> firmware update for already-sold-hosts is scheduled.
>
the problem really is that 2.6.18 isn't 2.6.25. OSI("Linux") is really
the wrong thing to do!
Not even microsoft does that.. they have very version specific OSI
strings.
Can you work with your colleges in the BIOS team to make sure that no
future BIOS will use OSI("Linux") please? If there's something they
would want to disable because of a Linux bug.. the real solution is to
fix the Linux bug!
next prev parent reply other threads:[~2008-05-27 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 10:34 BIOS _OSI(Linux) query ignored on PRIMEQUEST Taku Izumi
2008-05-23 6:36 ` [PATCH 0/2] ACPI: add "OSI(Linux) checking procedure" for ia64 machines Taku Izumi
2008-05-23 6:39 ` [PATCH 1/2] ACPI: add acpi_osi_dmi_table evaluation procedure " Taku Izumi
2008-05-23 6:43 ` [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST Taku Izumi
2008-05-25 11:43 ` Pavel Machek
2008-05-26 7:56 ` Taku Izumi
2008-05-26 8:06 ` Pavel Machek
2008-05-27 1:13 ` KAMEZAWA Hiroyuki
2008-05-27 2:05 ` Arjan van de Ven [this message]
2008-05-27 23:20 ` Andrew Morton
2008-05-27 23:41 ` Tony Luck
2008-05-27 23:50 ` Andrew Morton
2008-05-28 4:04 ` Luck, Tony
2008-05-28 0:09 ` KAMEZAWA Hiroyuki
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=20080526190553.1d37e17d@infradead.org \
--to=arjan@infradead.org \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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