Re: [Bluez-devel] HID initiated connections and input service

Bastien Nocera
2007-06-18T16:00:02Z

On Mon, 2007-06-18 at 15:36 +0100, Bastien Nocera wrote:
> On Mon, 2007-06-18 at 16:00 +0200, Pascal wrote:
> > Bastien Nocera wrote:
> > > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x84) pressed.
> > > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x82) pressed.
> > > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x82) released.
> >
> > This typically occurs when the kernel thinks the device
> > is reporting in "boot protocol" mode, for example when
> > net/bluetooth/hidp/core.c:hidp_add_connection() fails to
> > parse the report descriptor and consequently initializes
> > session->input instead of session->hid.
> >
> > Another possible cause is that your kernel does not have
> > HIDP support at all (2.6.20 or earlier).
>
> Absolutely ancient FC6 kernel (2.6.19-1.2895.fc6 because of the crappy
> driver, for my crappy wireless card).
>
> Will test on my rawhide laptop. Thanks for the pointer!

On the laptop, after getting the authorisation dialogue, I get this
message from the input service:
Jun 18 16:27:12 snoogens input[4052]: New input device 00:19:C1:7D:2E:FA ()

But no device is actually created.

The class show up in the bluez files as 0x000508, which seems to be
correct for a gamepad.
The kernel has HIDP support built in to a module, and seems to be
getting automatically loaded.

Could it be that I'm not setting the device flags to
HIDP_BOOT_PROTOCOL_MODE? (Incidentally, is there any way to check
whether a device is in this mode, or in full HID mode?)

Any idea on how to debug this?