linux-kernel - Re: [RFC] Include ACPI DSDT from INITRD patch into mainline

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: <1165055116.3233.144.camel@laptopd505.fenrus.org>
Date:	Sat, 02 Dec 2006 11:25:16 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Dave Jones <davej@...hat.com>
Cc:	Ben Collins <ben.collins@...ntu.com>,
	Alan <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	Eric Piel <eric.piel@...mplin-utc>
Subject: Re: [RFC] Include ACPI DSDT from INITRD patch into mainline

On Fri, 2006-12-01 at 19:21 -0500, Dave Jones wrote:
> On Fri, Dec 01, 2006 at 03:58:14PM -0500, Ben Collins wrote:
>  > On Fri, 2006-12-01 at 19:53 +0000, Alan wrote:
>  > > > > The whole approach of using filp_open() not the firmware interface
>  > > > > is horribly ugly and does not belong mainstream. 
>  > > > 
>  > > > What about the point that userspace (udev, and such) is not available
>  > > > when DSDT loading needs to occur? Init hasn't even started at that
>  > > > point.
>  > > 
>  > > Does that change the fact it is ugly ?
>  > 
>  > No, but it does beg the question "how else can it be done"?
>  > 
>  > Distros need a way for users to add a fixed DSDT without recompiling
>  > their own kernels.
> 
> There already is a way. It's called beating up the braindead bios authors,
> and pressuring motherboard vendors to push out updates.

and it includes pointing them at the linux-ready firmware developer kit
(URL in sig) so that it's really easy for them to test Linux with their
bios. 

If you or anyone else experience bios horkage that's not caught, please
let us know, so that we can add tests....

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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