From: Herman Sheremetyev <herman-6MNMYbGzEYJWk0Htik3J/w@public.gmane.org>
To: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [Fwd: [Fwd: patch to include a custom dsdt]]
Date: Mon, 09 Aug 2004 16:30:44 -0400 [thread overview]
Message-ID: <1092083444.1846.28.camel@camel> (raw)
In-Reply-To: <1092080468.5021.27.camel@dhcppc4>
On Mon, 2004-08-09 at 15:41, Len Brown wrote:
<snip>
> 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.
</snip>
Just a quick comment on this, the DSDT-initrd patch doesn't require an
initrd per se, i.e. using mkinitrd to create one, just the initrd option
in the kernel. It allows you to specify the compiled DSDT file as the
initrd itself making it very easy to change DSDTs without recompiling
the kernel - just compile the DSDT and tell the boot-loader where to
find it with the initrd option. It also has the ability to detect the
DSDT when it's inserted into an actual initrd but that functionality is
pretty secondary and simply makes the patch usable for those poor people
still using an initrd for some reason. I do agree that it's definitely
most useful for developers but I think having it as an option in the
main line may be handy for many "advanced users" as well.
-Herman
-------------------------------------------------------
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 20:30 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
2004-08-09 20:02 ` Stefan Schweizer
2004-08-09 20:07 ` Karol Kozimor
2004-08-09 20:30 ` Herman Sheremetyev [this message]
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=1092083444.1846.28.camel@camel \
--to=herman-6mnmybgzeyjwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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