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: Tue, 29 Jun 2004 11:09:05 +0200 [thread overview]
Message-ID: <1088500144.6030.249.camel@pegasus> (raw)
In-Reply-To: <40E12F15.9040805@thomae-privat.de>
Hi Matthias,
> the HID Specification 1.11 states on page 19:
>
> "Multibyte numeric values in reports are represented in little-endian
> format, with the least significant byte at the lowest address."
this makes is clear the EPoX HID descriptor is buggy and the only reason
their mouse works is, because it doesn't uses a multibyte value.
> So it really is 65280, isn't it? Also, I got this value by use of the
> HID Descriptor Tool.
> Moreover, the descriptor of the Apple keyboard, according to your web
> page, has a similar sequence the other way round: "2a ff 00"
I know. I checked my HID devices to see what the other manufacturer did
and if some other one uses multibyte.
> The funny thing is, the Windows Widcomm Bluetooth stack seems to cope
> with this, I tried it on a Thinkpad.
That is not so funny, because even the bthid was able to work with EPoX
keyboard. Everything depends on how you implement the parser. The Linux
kernel HID parser stores some values for faster access. We are inside
the kernel, we can't parse it everytime a report arrives.
> So what do we do?
I will notify EPoX about it, so they can correct their bug. We must
introduce a quirk for it, but I don't know how to trigger. The keyboard
don't uses Bluetooth DeviceID and the presenter DeviceID is also wrong.
At Cebit I told them that they should take care of DeviceID :(
For a future safe code I will implement the boot protocol, so we can use
it if the parsing of the report descriptor fails.
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
next prev parent reply other threads:[~2004-06-29 9:09 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
2004-06-29 8:57 ` Matthias Thomae
2004-06-29 9:09 ` Marcel Holtmann [this message]
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=1088500144.6030.249.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