[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F715BCF.8050808@zytor.com>
Date: Mon, 26 Mar 2012 23:18:55 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Thomas Renninger <trenn@...e.de>, eric.piel@...mplin-utc.net,
vojcek@...n.pl, dsdt@...gusch.at, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org,
Lin Ming <ming.m.lin@...el.com>, lenb@...nel.org,
robert.moore@...el.com, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] ACPI: Implement overriding of arbitrary ACPI tables via
initrd
On 03/26/2012 09:46 PM, Peter Stuge wrote:
> H. Peter Anvin wrote:
>> There are a lot of bootloaders, and one of the most commonly used ones
>> has a very adversarial relationship with the kernel maintainers.
>
> A couple of less commonly used ones, by or near the coreboot project,
> haven't exactly been embraced by kernel maintainers. Dunno if it's
> because coreboot doesn't much like ACPI, and thinks that it would
> be interesting to explore and innovate firmware on x86.
>
> //Peter
I think it is more because coreboot has tried to do things in
nonstandard ways rather than fill in the gaps they have. This is
getting a *lot* better, as far as I can tell, but in a sane world there
shouldn't be any need for "bootloaders by or near the coreboot project"
since any standard x86 bootloader should Just Work[TM].
I like to draw parallels with how we dealt with holes in applications in
the early days of Linux. For example, when Linux wasn't providing the
interfaces that X needed, we didn't add a bunch of Linux-specific code
to X, *we added the standard interfaces to Linux*.
-hpa
--
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/
Powered by blists - more mailing lists