From: Timo Veith <tv@rz-zw.fh-kl.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with BlueLogic WingKey Keyboard
Date: Tue, 22 Mar 2005 00:40:47 +0100 [thread overview]
Message-ID: <423F5B7F.9060200@rz-zw.fh-kl.de> (raw)
In-Reply-To: <1111408373.22872.54.camel@pegasus>
Marcel Holtmann wrote:
> can you try a 2.6.11-mh2 kernel first and see if that works. Otherwise I
> need the "hcidump -X -V" for your connection.
I chose the hcidump alternative first :). -X and -V are no recognized
options with my hcidump version. So I only used -x assuming that you
meant that. I typed "1" , "2", and so on as you can see and after the
"6" the mentioned behaviour started.
If this isn't enough I will get your patchset and try again.
Here is the hcidump:
tristan root # hcidump -x
HCIDump - HCI packet analyzer ver 1.9
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Mode Change (0x14) plen 6
00 29 00 00 00 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 1E 00 00 00 00
1> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 02 20 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 1F 00 00 00 00
2> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 00 00 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 02 A0 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 00 00 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 20 00 00 00 00
3> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 02 20 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 21 00 00 00 00
4> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 22 00 00 00 00
5> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 23 00 00 00 00
6> ACL data: handle 0x0029 flags 0x02 dlen 13
L2CAP(d): cid 0x41 len 9 [psm 0]
A1 01 00 00 00 00 00 00 00
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm> HCI Event: Mode
Change (0x14) plen 6
00 29 00 00 00 00
mm> HCI Event: Mode Change (0x14) plen 6
00 29 00 02 A0 00
mmmmmmmm> HCI Event: Mode Change (0x14) plen 6
00 29 00 00 00 00
> HCI Event: Mode Change (0x14) plen 6
00 29 00 02 20 03
Hmm, I don't know if this is of importance but I just noticed that if I
start bluetoothd I get an error for hid2hci. It says: No devices in HCI
mode found.
Kind regards and TIA,
Timo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-21 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 22:01 [Bluez-devel] Problem with BlueLogic WingKey Keyboard Timo Veith
2005-03-21 12:32 ` Marcel Holtmann
2005-03-21 23:40 ` Timo Veith [this message]
2005-03-21 23:51 ` Timo Veith
2005-03-22 0:59 ` Marcel Holtmann
2005-03-22 19:08 ` Timo Veith
2005-03-22 22:26 ` Marcel Holtmann
2005-03-22 1:02 ` 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=423F5B7F.9060200@rz-zw.fh-kl.de \
--to=tv@rz-zw.fh-kl.de \
--cc=bluez-devel@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