From: Nathan Gray <n8gray-7GExONQZ6ZKVc3sceRu5cw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: ACPI source releases updated (20030509)
Date: Mon, 12 May 2003 17:48:22 -0700 [thread overview]
Message-ID: <b9pf9o$jjs$1@main.gmane.org> (raw)
In-Reply-To: F760B14C9561B941B89469F59BA3A84725A299@orsmsx401.jf.intel.com
Grover, Andrew wrote:
> Can you help me understand what problem putting the DSDT in initrd
> fixes?
It solves the problem of having to recompile your kernel in order to change
your DSDT. Switching to a new DSDT becomes as simple as:
cp initrd_backup.img initrd.img
cat marker >> initrd.img # Mark the start of the DSDT
cat DSDT.aml >> initrd.img
reboot
It's very handy.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-13 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 22:18 ACPI source releases updated (20030509) Grover, Andrew
2003-05-13 0:48 ` Nathan Gray [this message]
2003-05-13 8:54 ` Sebastian Henschel
[not found] ` <20030513085421.GB1338-adzhR0EPeY/7X6WiDY61Ug@public.gmane.org>
2003-05-13 9:38 ` Markus Gaugusch
[not found] ` <Pine.LNX.4.53.0305131133540.10441-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-13 13:34 ` Christian Zoz
2003-05-13 11:26 ` Gunter Ohrner
2003-05-13 18:38 ` Nathan Gray
2003-05-13 18:55 ` Richard Black
2003-05-14 11:12 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 20:47 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847E96E70-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-05-12 21:18 ` Markus Gaugusch
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='b9pf9o$jjs$1@main.gmane.org' \
--to=n8gray-7gexonqz6zkvc3sceru5cw@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