From: Len Brown <len.brown@intel.com>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Moore, Robert" <robert.moore@intel.com>,
Alex Williamson <alex.williamson@hp.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net
Subject: Re: Userspace ACPI interpreter ( was RE: [ACPI] [RFC] dev_acpi: support for userspace access to acpi)
Date: Thu, 28 Oct 2004 01:37:52 -0400 [thread overview]
Message-ID: <418085B0.30208@intel.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041ABFFA@pdsmsx403>
One way to experiment with a user-mode ACPI interpreter would be to
continue to use the kernel-mode interpreter for boot up , and cut over
to the user-mode interpreter at /sbin/init. The kernel-mode interpreter
could be sent the way of free_initmem() which is called just before
/sbin/init is invoked.
-Len
next prev parent reply other threads:[~2004-10-28 5:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 4:04 Userspace ACPI interpreter ( was RE: [ACPI] [RFC] dev_acpi: support for userspace access to acpi) Yu, Luming
2004-10-28 4:04 ` Yu, Luming
2004-10-28 5:37 ` Len Brown [this message]
[not found] ` <418085B0.30208-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2004-10-28 15:24 ` Userspace ACPI interpreter ( was " Theodore Ts'o
2004-10-28 15:24 ` Userspace ACPI interpreter ( was RE: [ACPI] " Theodore Ts'o
2004-10-29 4:48 ` Len Brown
2004-10-29 4:58 ` Userspace ACPI interpreter ( was " Andi Kleen
2004-10-29 4:58 ` Userspace ACPI interpreter ( was RE: [ACPI] " Andi Kleen
2004-10-28 15:18 ` Userspace ACPI interpreter ( was " Bjorn Helgaas
2004-10-28 15:18 ` Userspace ACPI interpreter ( was RE: [ACPI] " Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 2:40 Yu, Luming
2004-10-29 2:51 Yu, Luming
2004-10-31 21:29 ` 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=418085B0.30208@intel.com \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=robert.moore@intel.com \
/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.