From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hid keyboard events get lost
Date: Tue, 29 May 2007 06:02:08 +0200 [thread overview]
Message-ID: <1180411328.21432.111.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <465B4079.8000509@imperial.ac.uk>
Hi Konrad,
> yes, i totally agree not to screw things up for a non-standard device.
> however, to understand things better, could you explain to me why l2cap
> sends more config requests to change the mtu although it already agreed
> on the one suggested by the keyboard (hcidump is in one of my recent
> postings), or do i misinterpret what's going on?
I removed the L2CAP MTU settings from the input service. So this one
should now work for you perfectly fine. However your kernel should some
weird behavior with a MTU size of 0. That is strange. Can you test a
2.6.22-rc3 kernel, because that contains a fix for the MTU config
setting.
It also contains the full HID report support. This means that the
missing report id in front of the report should be handled correctly. If
not than we need a quirk for that. My understanding is that even if this
is valid according to the HID specification, it is not valid for
Bluetooth based HID devices.
Regards
Marcel
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-05-29 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 15:16 [Bluez-users] hid keyboard events get lost Konrad Kieling
2007-05-28 12:19 ` Konrad Kieling
2007-05-28 13:55 ` Marcel Holtmann
2007-05-28 20:50 ` Konrad Kieling
2007-05-29 4:02 ` Marcel Holtmann [this message]
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=1180411328.21432.111.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox