public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Moles <jeremy-9vekgGPT+OA7YuNMryXyOw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: ACPI+Userspace
Date: Mon, 13 Jun 2005 19:37:36 -0400	[thread overview]
Message-ID: <1118705856.3814.6.camel@localhost> (raw)

Hello all--quick question.

As bad as it may seem, I was wondering if it is possible to generate
ACPI events in userspace? That is: propogate any arbitrary "string" up
through the ACPI subsystem, eventually getting dumped
to /proc/acpi/event which, in our case, is being watched and acted on by
the userspace util ACPID.

The obvious answer is: "Call /etc/acpi/hander with your string!"--which
is always an option--but I'd like to know if it's possible simply to use
for testing/debugging. I could write a driver supporting ioctls to pass
stuff via acpi_bus_generate_event (I think?), but that's wayyy too much
work for what I'm wanting this for. I'm sure there are reasons this
isn't a good idea, and I'd be glad to hear those too (to increase my
understanding of ACPI!).

Anyway--thanks ahead of time. Weee.



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20

             reply	other threads:[~2005-06-13 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 23:37 Jeremy Moles [this message]
2005-06-19 18:05 ` ACPI+Userspace Jeremy Moles
2005-06-19 18:08   ` ACPI+Userspace Jeremy Moles
2005-06-19 18:19     ` ACPI+Userspace Jeremy Moles

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=1118705856.3814.6.camel@localhost \
    --to=jeremy-9vekggpt+oa7yunmryxyow@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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