From: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: DSDT loading patch
Date: Mon, 6 Dec 2004 10:14:32 -0500 [thread overview]
Message-ID: <200412061014.33191.barr.156@osu.edu> (raw)
In-Reply-To: <200412061435.23333.david.goodenough-6b45v/Ft3lbby3iVrkZq2A@public.gmane.org>
On Monday 06 December 2004 9:35 am, David Goodenough wrote:
[...]
> Thanks for the reply. I am glad that some feature to get this in is now
> getting in to the standard kernel, but it does strike me that this
> in-initrd method means that normally you would not have to rebuild your
> kernel just because you have a buggy DSDT every time you put up a new
> kernel. Normally these days I can work with the stock Debian kernels, and
> so I do not need to rebuild the kernel every time.
>
> Do you know who decided this and why?
>
> Regards
>
> David
You'll only need to rebuild your kernel if your DSDT changes and is still
buggy: for example, if Samsung updates their BIOS and you upgrade, and
they've changed the DSDT but not fixed the bugs that the ACPI subsystem had
problems with.
The initrd method is only adventageous if you are in the process of fixing
your DSDT and you'd like to test different DSDTs and don't want to recompile
your kernel each time. The in-kernel method is actually better for me; that
way I don't have to remeber to append the DSDT to the generated initrd.
The initrd method is no longer used for technical reasons I don't remember
exactly.
Andrew
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-12-06 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 9:07 DSDT loading patch David Goodenough
[not found] ` <200412060907.53079.david.goodenough-6b45v/Ft3lbby3iVrkZq2A@public.gmane.org>
2004-12-06 12:40 ` Andrew Barr
[not found] ` <200412060740.25524.barr.156-ZbGKxL/pcrQ@public.gmane.org>
2004-12-06 14:35 ` David Goodenough
[not found] ` <200412061435.23333.david.goodenough-6b45v/Ft3lbby3iVrkZq2A@public.gmane.org>
2004-12-06 15:14 ` Andrew Barr [this message]
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=200412061014.33191.barr.156@osu.edu \
--to=barr.156-zbgkxl/pcrq@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