Date: Tue, 27 Jul 2004 12:59:15 -0400 From: Anish Mistry <mistry.7@osu.edu> To: acpi@FreeBSD.org Subject: Re: Generic hotkey script (was: Re: Panasonic acpi driver) Message-ID: <200407271259.24724.mistry.7@osu.edu> In-Reply-To: <20040724221344.GE85709@fasolt.home.paeps.cx> References: <20040712.200815.74734634.nyan@jp.FreeBSD.org> <40FE9BEA.7060802@root.org> <20040724221344.GE85709@fasolt.home.paeps.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 24 July 2004 06:13 pm, Philip Paeps wrote:
> On 2004-07-21 09:38:02 (-0700), Nate Lawson <nate@root.org> wrote:
> > I don't want us to import any device-specific hotkey scripts (i.e., asus,
> > panasonic, toshiba, etc.) but instead have a single general-purpose
> > script and have the kernel translate device-specific tables of hotkey
> > values to generic ones. That way a single script can look for the
> > generic "volume up/down" buttons and act accordingly.
> >
> > Please email me if you're interested in working on that.
>
> I've been thinking about this a while ago, but it somehow got itself stuck
> on my 'maybe later' stack. My idea was to have devd do the magic here.
> Agree on some constants (ACPI_VOLUME_UP, ACPI_VOLUME_MUTE,
> ACPI_HOTKEY_1,...) that the specific drivers could send to devd using
> acpi_UserNotify().
>
> We could then have a devd script (much like we also have power_profile, or
> we could rename that to 'acpi_event' or something similar) to catch these
> events.
>
> notify 10 {
> match "system" "ACPI";
> match "subsystem" "HOTKEY";
> action "/etc/rc.d/acpi_event $notify";
> };
>
> To avoid having a notify section for every different device specific acpi
> driver, we could either have them all be ACPI_MODULE_NAME("HOTKEY"), or we
> could register them under an umbrella hotkey driver. The latter approach
> might be nicer. Then we could also add other non-acpi hotkey gadgets (ir
> remote controls maybe? :-)) under it?
>
> I'd be interested in hacking at this.
>
> - Philip
This would be nice. I'd be able to put some time into this since it would be
good to get it committed before the freeze. I think the
ACPI_MODULE_NAME("HOTKEY") way would be best for now since you could always
just have other non-acpi devices use another devd entry that would just call
the acpi_hotkey script action. I'll try on modifying my script for the
acpi_fuji driver to be generic.
- --
Anish Mistry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBBonrxqA5ziudZT0RAqSVAJ9nyHHgDMWuGjIn4zIBYVsvq1pH9wCgqtRi
EwA61QFdGmY+dpVKhleZ6Dc=
=z16N
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407271259.24724.mistry.7>