From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 17:29:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E5DE16A4CE for ; Mon, 12 Jan 2004 17:29:24 -0800 (PST) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 6BD0843D64 for ; Mon, 12 Jan 2004 17:29:23 -0800 (PST) (envelope-from nate@root.org) Received: (qmail 58841 invoked by uid 1000); 13 Jan 2004 01:29:25 -0000 Date: Mon, 12 Jan 2004 17:29:25 -0800 (PST) From: Nate Lawson To: acpi-jp@jp.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 cc: freebsd-current@freebsd.org Subject: Re: [acpi-jp 2999] Fujitsu Function Button ACPI Module (FJEX) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 01:29:24 -0000 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