From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problems using bluetooth keyboard with Nokia N800...
Date: Wed, 31 Oct 2007 17:22:15 +0100 [thread overview]
Message-ID: <1193847735.32459.45.camel@violet> (raw)
In-Reply-To: <a8e1da0710292006u7082d22bo1da87fefe23a7222@mail.gmail.com>
Hi Dave,
> > < ACL data: handle 44 flags 0x02 dlen 12
> > L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > ACL data: handle 44 flags 0x02 dlen 12
> > L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> > < ACL data: handle 44 flags 0x02 dlen 12
> > L2CAP(s): Connect req: psm 17 scid 0x0040
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > ACL data: handle 44 flags 0x02 dlen 16
> > L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
> > Connection successful
> > < ACL data: handle 44 flags 0x02 dlen 16
> > L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
> > MTU 48
> > > ACL data: handle 44 flags 0x02 dlen 16
> > L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
> > MTU 48
> > < ACL data: handle 44 flags 0x02 dlen 18
> > L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
> > Success
> > MTU 48
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > ACL data: handle 44 flags 0x02 dlen 18
> > L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 1 clen 4
> > MTU 128
> > < ACL data: handle 44 flags 0x02 dlen 16
> > L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
> > MTU 48
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > ACL data: handle 44 flags 0x02 dlen 18
> > L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 1 clen 4
> > MTU 128
> > < ACL data: handle 44 flags 0x02 dlen 12
> > L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> > > HCI Event: Number of Completed Packets (0x13) plen 5
> > handle 44 packets 1
> > > ACL data: handle 44 flags 0x02 dlen 12
> > L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> > < HCI Command: Disconnect (0x01|0x0006) plen 3
> > handle 44 reason 0x13
> > Reason: Remote User Terminated Connection
> > > HCI Event: Command Status (0x0f) plen 4
> > Disconnect (0x01|0x0006) status 0x00 ncmd 1
> > > HCI Event: Disconn Complete (0x05) plen 4
> > status 0x00 handle 44 reason 0x16
> > Reason: Connection Terminated by Local Host
> >
> Modify the head file :
> /usr/include/bluetooth/hidp.h:
> #define HIDP_DEFAULT_MTU 128
>
> Then rebuild the hidd. This is a hardcode change, just have a try.
this looks like a bug in the keyboards firmware. The minimum MTU of 48
must be accepted and then use segmentation and reassembly within the
protocol. However if that works, we can change the default MTU value.
Looking at the bluez-utils-3.22 input service source, I just see that we
disabled the MTU requirement code completely for now. So use
bluez-utils-3.22 and use the input service.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-10-31 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 1:32 [Bluez-users] Problems using bluetooth keyboard with Nokia N800 Scott Bambrough
2007-10-30 3:06 ` Dave Young
2007-10-31 16:22 ` 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=1193847735.32459.45.camel@violet \
--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