From: Pavel Machek <pavel@suse.cz>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Brown, Len" <len.brown@intel.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: Sun, 31 Oct 2004 22:29:14 +0100 [thread overview]
Message-ID: <20041031212914.GH5578@elf.ucw.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC000@pdsmsx403>
Hi!
> >> On IA64 platform, ACPI interpreter seems to be mandatory for those
> >> stuff, but IA32 is not. So, the ram disk is the generic solution
> >> for loading user space interpreter for boot.
> >
> >In two sentences: If you want to play with moving the interpreter
> >to user-space, please do so, and do it on ia64, so you have to
> >deal with the interesting problems.
> >
> >And this whole thing is a gigantic tangent that is only distracting
> >attention from the real question at hand, namely, Alex's dev_acpi
> >patch, which exists today and enables some very interesting new
> >functionality.
> >
>
> Yes, I agree Alex's dev_acpi is interesting, which could result in
> the removal of some acpi specific drive such as battery.c, button.c,
> fan.c, thermal.c .... So, I raised the question of userspace ACPI
> interpreter. Intuitively, userspace is the right place for interpreter.
I do not think you want to put thermal/fan into userspace. If you boot
machine with init=/bin/bash, you should have working system. System
without fan fail... fast.
Plus you want to do suspend/resume.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-10-31 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 2:51 Userspace ACPI interpreter ( was RE: [RFC] dev_acpi: support for userspace access to acpi) Yu, Luming
2004-10-31 21:29 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-28 4:04 Userspace ACPI interpreter ( was RE: [ACPI] " Yu, Luming
2004-10-28 5:37 ` Len Brown
2004-10-28 15:24 ` Userspace ACPI interpreter ( was " Theodore Ts'o
2004-10-29 4:48 ` Userspace ACPI interpreter ( was RE: [ACPI] " Len Brown
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=20041031212914.GH5578@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox