LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA> To: "Jiri Kosina" <jikos@jikos.cz>, "Marcel Holtmann" <marcel@holtmann.org> Cc: <linux-kernel@vger.kernel.org> Subject: RE: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793 Date: Tue, 27 Feb 2007 11:12:06 -0500 [thread overview] Message-ID: <8E8F647D7835334B985D069AE964A4F7028FE5B0@ECQCMTLMAIL1.quebec.int.ec.gc.ca> (raw) In-Reply-To: Pine.LNX.4.64.0702271648190.10496@twin.jikos.cz > > we understand the original CSR HID proxy dongles, but for the Logitech > ones, it is wild guesses. The current support in hid2hci has been > tested on Logitech diNovo first generation and I have no other > Logitech hardware to verify it with. We might simply need > the full HID report descriptor to see who is at fault. > > As far as I can see from a quick look, the device IDs are > unchanged (0x046d/0xc70e for the keyboard), but the report > descriptor seems to differ from the one you have at > http://www.holtmann.org/linux/bluetooth/logitech.html - that > seems pretty sad. > > What puzzles me a bit is a fact that both the bugreporters > seem to state pretty clearly that this started happening > after some update, am I right? > > Or did the hardware before work all the time in the HID mode, > without even being attempted to switch to HCI (which seems to > cause the bug)? > Actually it's the first time I'm trying this keyboard and mouse. - vin
next prev parent reply other threads:[~2007-02-27 16:12 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-16 12:03 [KJ][PATCH] is_power_of_2 in ia64mm Vignesh Babu BM 2007-02-16 15:02 ` [KJ] [PATCH] " Richard Knutsson 2007-02-16 15:13 ` Andreas Schwab 2007-02-16 15:57 ` Richard Knutsson 2007-02-16 15:59 ` Andreas Schwab 2007-02-16 16:40 ` Richard Knutsson 2007-02-16 16:43 ` Andreas Schwab 2007-02-16 17:06 ` Robert P. J. Day 2007-02-16 17:36 ` Richard Knutsson 2007-02-16 16:58 ` Robert P. J. Day 2007-02-16 15:27 ` Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793 Fortier,Vincent [Montreal] 2007-02-18 21:23 ` Jiri Kosina 2007-02-19 0:25 ` Marcel Holtmann 2007-02-19 9:36 ` Jiri Kosina 2007-02-27 15:54 ` Jiri Kosina 2007-02-27 16:12 ` Fortier,Vincent [Montreal] [this message] [not found] ` <Pine.LNX.4.64.0702271713220.10496@twin.jikos.cz> 2007-02-27 20:35 ` Fortier,Vincent [Montreal] 2007-02-20 2:11 Fwd: " Veronique & Vincent 2007-02-20 8:02 ` Jiri Kosina 2007-02-22 2:50 ` Pete Zaitcev 2007-02-22 8:04 ` Jiri Kosina 2007-02-22 10:38 ` Veronique & Vincent 2007-02-22 10:46 ` Jiri Kosina 2007-03-05 19:19 Amedee Van Gasse 2007-03-05 21:54 ` Jiri Kosina [not found] ` <1173191358.9292.4.camel@saruman> 2007-03-06 14:44 ` Jiri Kosina 2007-03-23 9:15 ` Jiri Kosina
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=8E8F647D7835334B985D069AE964A4F7028FE5B0@ECQCMTLMAIL1.quebec.int.ec.gc.ca \ --to=vincent.fortier1@ec.gc.ca \ --cc=jikos@jikos.cz \ --cc=linux-kernel@vger.kernel.org \ --cc=marcel@holtmann.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).