From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Stefan Schweizer <sschweizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [Fwd: [Fwd: patch to include a custom dsdt]]
Date: 09 Aug 2004 15:41:08 -0400 [thread overview]
Message-ID: <1092080468.5021.27.camel@dhcppc4> (raw)
In-Reply-To: <e7963922040809112873fd7be4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 2004-08-09 at 14:28, Stefan Schweizer wrote:
> On 09 Aug 2004 12:59:16 -0400, Len Brown <len.brown <at> intel.com>
> wrote:
> > This looks handy.
> > comments?
>
> You should take the patch of Michael Blumenstein for initrd support:
>
> http://gaugusch.at/kernel.shtml
>
> http://gaugusch.at/acpi-dsdt-initrd-patches/acpi-dsdt-initrd-patch-v0.4-2.6.7.patch
>
> I use it and I can confirm that it works :)
Yes, the dsdt-in-initrd patch works.
Yes, it is perfect for the unfortunate but determined soul who
administers a variety of broken machines where they all run the same
kernel and require a different DSDT -- I really do feel sorry for that
person and look forward to the day they find non-broken hardware.
But DSDT overrides are for developers, not end-users, not customers.
Nobody can support the OEM's firmware, or a modified version of it
except the OEM themselves. If a developer happens to fix an OEM's
firmware and sends the OEM the fix, that happy situation is purely
between the end-user and the OEM. Distros should absolutely never
be in the business of supporting hardware running modified firmware.
I think that one major Distro pulled the dsdt-in-initrd patch, and I
think it was a mistake for them to do so -- they can't support it.
That said, it is useful for developers to be able to override the DSDT.
There are two methods -- re-build kernel or re-build kernel and also
modify the initrd.
Kernel re-build is (I think) simple enought. I think the patch at hand
takes it from simple to trivial.
Kernel re-build + initrd update I dislike because it depends on the
existence of an initrd (not everybody uses has an initrd, I haven't used
an initrd in over a year), and worse, it depends on the format of the
initrd, which we don't control.
Anyway, I hope that my position, and the reason I haven't pulled the
perfectly functional and useful dsdt-in-initrd patch before is clear.
Any comments on the patch at hand?
thanks,
-Len
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-09 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 16:59 [Fwd: [Fwd: patch to include a custom dsdt]] Len Brown
2004-08-09 17:49 ` Karol Kozimor
[not found] ` <20040809174935.GA20719-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-08-09 19:23 ` Dominik Brodowski
2004-08-09 18:28 ` Stefan Schweizer
[not found] ` <e7963922040809112873fd7be4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-08-09 19:41 ` Len Brown [this message]
2004-08-09 20:02 ` Stefan Schweizer
2004-08-09 20:07 ` Karol Kozimor
2004-08-09 20:30 ` Herman Sheremetyev
2004-08-11 6:20 ` Stefan Seyfried
2004-08-16 7:20 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1092080468.5021.27.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sschweizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox