On 7 May 2014 08:46, Xīcò <x...@atelo.org> wrote: > On Wed, May 07, 2014 at 03:51:17PM +0200, Lars Engels wrote: >> IIRC Rui (CC'ed) did some work on implementing new ACPI key events in >> acpi_asus for the first EeePC. > > Looking around the acpi drivers, some hard-encode actions associated to > the events (like brightness control), some emit messages for devd (like > sound control for the asus), and most mix the two options. > > Emitting devd events is both easy and highly user configurable. But it > still does not solve the problem of reinjecting the special keys as > generic keyboard events, for instance to let the user configure them > through xorg. Writing a virtual keyboard in each acpi driver seems a lot > of duplication, and maybe too heavy. IMHO acpi drivers should just emit > information to be caught by devd. Maybe with a single format, so that a > shared other component can listen to them and reinject them as generic > keyboard events.
Indeed. Hack it up, send through patches. :) -a _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"