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: <12c511ca0805271641r68d50d3do9f6427a8dc6ad469@mail.gmail.com>
Date:	Tue, 27 May 2008 16:41:59 -0700
From:	"Tony Luck" <tony.luck@...el.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"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

I'm not sure that sharing drivers/acpi/blacklist.c between different
architectures is wise idea.  There are entries in there that make
blanket decisions for all machines made by an OEM.

It seems quite possible that an OEM that makes boxes using
different processor architectures might make different mistakes
in the respective BIOS teams.

-Tony
--
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/