From: John Belmonte <john@neggie.net>
To: Alex Williamson <alex.williamson@hp.com>
Cc: acpi-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: [PATCH] filling in ACPI method access via sysfs namespace
Date: Fri, 09 Apr 2004 21:52:29 -0400 [thread overview]
Message-ID: <4077535D.6020403@neggie.net> (raw)
In-Reply-To: <1081549317.2694.25.camel@patsy.fc.hp.com>
Alex Williamson wrote:
> Here's another approach that's far less ugly than the last and is
> much more powerful. The code is a little over half the size as a
> bonus. Rather than specifically poking for certain methods and exposing
> them, this patch exposes everything. The down side is that all reading
> and writing of the files need to use binary acpi data structures. This
> interface certainly provides "shoot yourself in the foot" potential, but
> the access to the namespace from userspace is hard to beat. Any
> thoughts on this approach versus the last? This interface and a simple
> set of libraries to go along with it has a lot of potential. Thanks,
The limitation of this interface is that it's not able to call an ACPI
method with some arguments and get the return value, correct?
-John
--
http:// if ile.org/
next prev parent reply other threads:[~2004-04-10 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 19:49 [PATCH] filling in ACPI method access via sysfs namespace Alex Williamson
2004-04-09 22:21 ` Alex Williamson
2004-04-10 1:52 ` John Belmonte [this message]
2004-04-10 3:12 ` [ACPI] " Alex Williamson
2004-04-10 5:31 ` John Belmonte
2004-04-10 20:42 ` Alex Williamson
2004-04-11 3:20 ` Alex Williamson
2004-04-11 22:29 ` Matthew Wilcox
2004-04-12 3:31 ` Alex Williamson
2004-04-19 15:45 ` Alex Williamson
2004-05-06 10:02 ` Pavel Machek
2004-04-10 5:32 ` Alex Williamson
[not found] <fa.n5srcao.1k1orra@ifi.uio.no>
[not found] ` <fa.e0sva3e.u5k09i@ifi.uio.no>
2004-04-12 4:13 ` Andy Lutomirski
2004-04-12 4:32 ` Alex Williamson
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=4077535D.6020403@neggie.net \
--to=john@neggie.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).