From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HID initiated connections and input service
Date: Mon, 18 Jun 2007 17:00:02 +0100 [thread overview]
Message-ID: <1182182402.3161.52.camel@cookie.hadess.net> (raw)
In-Reply-To: <1182177408.3161.43.camel@cookie.hadess.net>
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?
--
Bastien Nocera <hadess@hadess.net>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-06-18 16:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 16:44 [Bluez-devel] HID initiated connections and input service Bastien Nocera
2007-06-16 7:05 ` Marcel Holtmann
2007-06-16 16:35 ` Bastien Nocera
2007-06-16 19:35 ` Marcel Holtmann
2007-06-17 20:25 ` Bastien Nocera
2007-06-18 13:06 ` Bastien Nocera
2007-06-18 14:00 ` Pascal
2007-06-18 14:36 ` Bastien Nocera
2007-06-18 16:00 ` Bastien Nocera [this message]
2007-06-18 17:30 ` Pascal
2007-06-18 19:23 ` Bastien Nocera
2007-06-18 20:16 ` Pascal
2007-06-18 22:40 ` Bastien Nocera
2007-06-16 7:25 ` Marcel Holtmann
2007-06-16 16:44 ` Bastien Nocera
2007-06-16 19:24 ` Marcel Holtmann
2007-06-18 16:08 ` Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1182182402.3161.52.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.