From: Sebastian Henschel <shensche-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Patch] DSDT in initrd
Date: Tue, 6 May 2003 12:09:49 +0200 [thread overview]
Message-ID: <20030506100949.GC973@enigma.daemon.sh> (raw)
In-Reply-To: <Pine.LNX.4.53.0305052221420.8540-qopfHk9/S+VQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
hi markus...
Received at 2003-05-06 / 09:02 by Markus Gaugusch:
> I've implemented my patch to put the DSDT into the initial ramdisk.
> It uses the same approach as bootsplash: just use the raw initrd data.
hey, it seems to work here. my ac_adapter is back with my custom DSDT
from the initrd. :) thank you very much.
> 1.) enable CONFIG_BLK_DEV_INITRD and CONFIG_ACPI_INITRD
perhaps you should also say that the ramdisk support has to be
included statically (CONFIG_BLK_DEV_RAM=y). i had it as a module and was
looking for these options to no avail. :)
> Then reboot.
> The message "Looking for DSDT in initrd... found!" should be in your dmesg
> after next boot. (for some reason <6> is before "found", but I'm sure
> that someone will be able to give me the right pointers to fix that).
i do not know much about printk, but possibly, KERN_INFO (<6>) is only
parsed when it is at the beginning of a line. so your "found" or "not
found" statements would also be printed out with KERN_INFO as subsequent
calls of printk without a newline, although the do not start with
KERN_INFO. just a wild guess. :)
cheers,
sebastian
--
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-05-06 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:48 [Patch] DSDT in initrd Markus Gaugusch
[not found] ` <Pine.LNX.4.53.0305052221420.8540-qopfHk9/S+VQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-06 10:09 ` Sebastian Henschel [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=20030506100949.GC973@enigma.daemon.sh \
--to=shensche-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=markus-z+rTbpWsRgbk7+2FdBfRIA@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