linux-kernel - Re: Loading DSDT from initrd, can it be done from grub instead?

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: <4832BF97.2070405@googlemail.com>
Date:	Tue, 20 May 2008 14:09:59 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Alan Jenkins <aj504@...york.ac.uk>
CC:	David Härdeman <david@...deman.nu>,
	linux-kernel@...r.kernel.org
Subject: Re: Loading DSDT from initrd, can it be done from grub instead?

Alan Jenkins wrote:

> David Härdeman wrote:
>> In commit 9a9e0d685553af76cb6ae2af93cca4913e7fcd47 the
>> ACPI_CUSTOM_DSDT_INITRD option was removed.
>>
>> I was wondering if it'd be feasible to hack grub to load a custom DSDT
>> instead (since grub can read filesystems) and then pass a pointer to a
>> memory location containing the DSDT to the kernel?
> 
> Um, why?  What stops you from reverting the offending commit?
> 
> Without further info, I'd assume the feature was removed on policy
> grounds.  I.e. it's not nice to be effectively patching the BIOS
> yourself, and vendors have fixed most of their BIOS's / linux is
> slightly more tolerant to broken ones.  I don't know whats wrong with
> reading files from the initrd.


It was reverted because the code was not really ready and caused some problems.

> 
> Alan

Gabriel

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