public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Matthias Thomae <bluez@thomae-privat.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Epox Barton keyboard: HID create error 53
Date: Mon, 28 Jun 2004 21:55:26 +0200	[thread overview]
Message-ID: <1088452526.6030.86.camel@pegasus> (raw)
In-Reply-To: <40E024AD.1000101@thomae-privat.de>

Hi Matthias,

> Well, I looked a little closer, and it seems that the debugging message
> 
> net/bluetooth/hidp/hid.c: usage index exceeded
> net/bluetooth/hidp/hid.c: hid_add_usage failed
> net/bluetooth/hidp/hid.c: item 0 2 2 2 parsing failed
> 
> is caused by the item USAGE_MAXIMUM(65280) which corresponds to "2A 00 
> FF", the 18th item of the descriptor (see below). The maximum number of 
> usages is set in net/bluetooth/hidp/hid.h
> 
> #define HID_MAX_USAGES                  1024
> 
> I tried to increase this to 65535 (FFFF), the theoretical max according 
> to HUT 1.11, but it didn't help, because then the max page size is exceeded.
> 
> But this doesn't seem reasonable anyway, since the codes E8-FFFF are not 
> defined yet (and which keyboard has several tens of thousand keys? ;).
> 
> So, can we assume the HID descriptor is "broken"? If yes, what would be 
> the way to deal with this? Can we re-set the USAGE_MAXIMUM to a 
> reasonable value?

I don't know if the descriptor is broken or if the HID parser has a bug.

The value you are talking about is 255 and not 65280. The questions is
if the descriptor encodes these values in big or in little endian. If
they must be in little endian than EPoX made a mistake here, otherwise
our HID parser is broken. Please check the specification for the used
endian encoding, because I will not have time to read it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-28 19:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 17:34 [Bluez-users] Epox Barton keyboard: HID create error 53 Matthias Thomae
2004-06-14 23:27 ` Marcel Holtmann
2004-06-15  6:26   ` Matthias Thomae
2004-06-15  7:34     ` Marcel Holtmann
2004-06-15  9:23       ` Matthias Thomae
2004-06-15  9:48         ` Marcel Holtmann
2004-06-15 19:16           ` Matthias Thomae
2004-06-15 22:48             ` Marcel Holtmann
2004-06-22  7:20               ` Matthias Thomae
2004-06-22  9:40                 ` Marcel Holtmann
2004-06-23  0:49                   ` Matthias Thomae
2004-06-28 14:01                     ` Matthias Thomae
2004-06-28 19:55                       ` Marcel Holtmann [this message]
2004-06-29  8:57                         ` Matthias Thomae
2004-06-29  9:09                           ` Marcel Holtmann
2004-06-29 19:55                             ` Matthias Thomae
2004-06-29 21:11                               ` Marcel Holtmann
2004-06-30  7:59                                 ` Matthias Thomae
2004-07-10 17:24                                 ` Matthias Thomae
2004-07-10 17:29                                   ` Marcel Holtmann

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=1088452526.6030.86.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bluez@thomae-privat.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox