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: Tue, 15 Jun 2004 11:48:07 +0200	[thread overview]
Message-ID: <1087292887.13792.81.camel@pegasus> (raw)
In-Reply-To: <40CEC020.6050107@thomae-privat.de>

Hi Matthias,

> > it is a problem of the HID parser. If you enable debugging with "#define
> > DEBUG" in net/bluetooth/hidp/hid.h then you should see those lines with
> > dmesg:
> > 
> > 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
> > 
> > Do you see it, too?
> 
> Yes, I see exactly the same.

someone has to fix the HID parser to get it working with the keyboard
and the presenter from EPoX. I am a little bit busy in getting the boot
protocol support ready, so that we can at least include HID boot support
into the mainline kernel. The full report protocol support has to wait
until the kernel gets its device independent HID support.

> > Please send me the output of your mouse too and use
> 
> I`ll send it tonight, 'cause I haven't got it with me now.
> 
> > 	sdptest records 00:04:61:xx:xx:xx > file
> > 
> > from the utils2 CVS to get the full SDP record information.
> 
> It's attached. Do you need the same from the mouse, too?
> Anything else I can do?

Please do so. I want to compare it with my devices. The keyboard looks
the same as mine. It seems they only choosed a newer CSR firmware.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-15  9:48 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 [this message]
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
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=1087292887.13792.81.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