linux-kernel - Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080526190553.1d37e17d@infradead.org>
Date:	Mon, 26 May 2008 19:05:53 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Pavel Machek <pavel@...e.cz>,
	Taku Izumi <izumi.taku@...fujitsu.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on
 PRIMEQUEST

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!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/