From: Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>,
Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>,
eric-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org
Subject: [PATCH] [1/2 DSDT via initrd or initramfs] move initramfs init before DSDT init
Date: Sun, 27 Feb 2005 20:45:35 +0100 [thread overview]
Message-ID: <4222235F.3070105@renninger.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
Hi,
This patch from Hannes Reinecke (hare-l3A5Bk7waGM@public.gmane.org) moves initialisation of
initramfs by some lines before the DSDT is parsed.
Thomas
-> linux-2.6.11-rc5
[-- Attachment #2: initramfs-before-acpi.patch --]
[-- Type: text/x-patch, Size: 1157 bytes --]
Subject: Call populate_rootfs() prior to acpi_early_init()
From: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
populate_rootfs should be called prior to acpi_early_init()
if we ever want to be able to use a custom DSDT from initramfs.
Having done this, rootfs is available during acpi_early_init()
and the ACPI code can just call sys_open() to load a custom
DSDT.
--- x/init/main.c.orig 2005-02-24 17:39:55.000000000 +0100
+++ y/init/main.c 2005-02-26 16:46:30.278718350 +0100
@@ -508,8 +508,6 @@
#endif
check_bugs();
- acpi_early_init(); /* before LAPIC and SMP init */
-
/* Do the rest non-__init'ed, we're now alive */
rest_init();
}
@@ -635,6 +633,14 @@
*/
child_reaper = current;
+ /*
+ * Do this before initcalls, because some drivers want to access
+ * firmware files.
+ */
+ populate_rootfs();
+
+ acpi_early_init(); /* before LAPIC and SMP init */
+
/* Sets up cpus_possible() */
smp_prepare_cpus(max_cpus);
@@ -644,12 +650,6 @@
smp_init();
sched_init_smp();
- /*
- * Do this before initcalls, because some drivers want to access
- * firmware files.
- */
- populate_rootfs();
-
do_basic_setup();
/*
reply other threads:[~2005-02-27 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4222235F.3070105@renninger.de \
--to=mail-smmupah/rwjm7kwft8n7nw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=eric-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org \
--cc=hare-l3A5Bk7waGM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.