From owner-acpi-jp@jp.FreeBSD.org Tue Jan 13 10:29:30 2004
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id i0D1TUi85424;
	Tue, 13 Jan 2004 10:29:30 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from root.org (root.org [67.118.192.226])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with SMTP/inet id i0D1TTC85328
	for <acpi-jp@jp.FreeBSD.org>; Tue, 13 Jan 2004 10:29:29 +0900 (JST)
	(envelope-from nate@root.org)
Received: (qmail 58841 invoked by uid 1000); 13 Jan 2004 01:29:25 -0000
From: Nate Lawson <nate@root.org>
To: acpi-jp@jp.FreeBSD.org
cc: freebsd-current@freebsd.org
In-Reply-To: <200401121945.59585.mistry.7@osu.edu>
Message-ID: <20040112172739.H58453@root.org>
References: <200401121945.59585.mistry.7@osu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Mon, 12 Jan 2004 17:29:25 -0800
X-Sequence: acpi-jp 3000
Subject: [acpi-jp 3000] Re: Fujitsu Function Button ACPI Module (FJEX)
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: nate@root.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+031216

On Mon, 12 Jan 2004, Anish Mistry wrote:
> I've been sitting on this for a while waiting to hear back from the primary
> author, but no word after a few weeks, so I'm posting it to see what
> people think.  This module allows a program to receive events when the
> function buttons are pressed.  It's companion userland program fujiapp
> hooks in and receives and event when a button is pressed and show the
> level.  It has only been tested on the Fujitsu P2000 series laptops, but
> may work on other models with the FJEX acpi device.
>
> Sean's website:
> http://www.stalker.org/~sean/freebsd-p2040/FujiApp/
>
> My modifications to make it a loadable module:
> http://am-productions.biz/docs/acpi_fjex.tgz
> and just fujiapp without the module source included:
> http://am-productions.biz/docs/fujiapp-1.1.tgz

You should use acpi_UserNotify() to send events to userland.  The events
will appear on /dev/devctl and can be parsed by devd.  If you can do what
you want via devd.conf, fine.  If you want to have your own program
reading /dev/devctl, you'll have to implement device cloning for
/dev/devctl first or not run devd. (A current deficiently in devctl is
that only one reader can be present at a time.)

-Nate
