Comment 10 for bug 162083

Chris Irwin wrote:
> Mario
>
> I had thought that the wireless devices would still go through the
> usbhid as there seems to be no other applicable quirks file. I did not
> have an apple bluetooth keyboard to test, and it never occurred to me
> that it may not.
>
> Do you know what driver handles your keyboard then?
>
Chris,

I want to say it's just directly handled by the normal input driver interface
for the kernel.

The only relevant things that I'll see crop up are these in dmesg:

[ 44.100775] input: Apple Computer, Inc. Mighty Mouse as /class/input/input12
[ 45.108663] input: Apple Inc. Keyboard as /class/input/input14

Obviously neither of those ends up loading usbhid, usbkbd, or usbmouse.

Lots of bluetooth modules begin to load too, but its hard to determine if they
were intended for usage by the devices or because of the usb bluetooth receiver.

Also, I do have an additional hald process running for this device, and a
bluetooth input service running

107 29123 0.0 0.0 2164 900 ? S 06:44 0:00
hald-addon-keyboard: listening on /dev/input/event7
root 6021 0.0 0.0 2772 1080 ? S Dec11 0:00
/usr/lib/bluetooth/bluetoothd-service-input

So with all that being said, i'm pretty confused myself as to who is actually
responsible for the fact that the keyboard works as much as it does :)

--
Mario Limonciello
<email address hidden>