From: Marcel Holtmann <marcel@holtmann.org>
To: Scott James Remnant <keybuk@google.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth 2.1 keyboard not sending keypress notifications
Date: Mon, 09 Jan 2012 12:16:13 -0800 [thread overview]
Message-ID: <1326140173.6454.168.camel@aeonflux> (raw)
In-Reply-To: <CAHZ1yCmLV6RS6EA7+p2+VDG05YNSNUxCbo8gLcq2t04Ahn2Kcw@mail.gmail.com>
Hi Scott,
> >> So it turns out that the Mac isn't doing anything special either; it's
> >> doing ordinary 2.0 authentication. But the twist is an L2CAP
> >> connection and configuration request/response before authentication is
> >> requested, this seems to enable the keyboard sending a Vendor Event
> >> every time a key is pressed during authentication.
> >
> > that is what I thought. Get your Packet Logger in OS X running and hope
> > that it decodes a bit more. However getting this integrated into BlueZ
> > might be a lot trickier. This is nasty stuff.
> >
> Right now it looks like it's just making a connection to the HID
> Interrupt PSM (0x13), and while that connection is open, seeing the
> keypresses.
>
> Is there an L2CAP debugger on the Linux side, so I can make sure I'm
> replicating what it's doing packetwise?
hcidump can record binary logfiles with -w. If you use hcidump 2.x then
it automatically record into BTSnoop format. Supported by Wireshark as
well. You can also use -R to see the raw data packets.
Regards
Marcel
next prev parent reply other threads:[~2012-01-09 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 23:43 Bluetooth 2.1 keyboard not sending keypress notifications Scott James Remnant
2012-01-06 23:48 ` Marcel Holtmann
2012-01-07 0:52 ` Scott James Remnant
2012-01-07 1:40 ` Marcel Holtmann
2012-01-09 19:37 ` Scott James Remnant
2012-01-09 19:54 ` Marcel Holtmann
2012-01-09 20:03 ` Scott James Remnant
2012-01-09 20:16 ` Marcel Holtmann [this message]
2012-01-10 1:10 ` Scott James Remnant
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=1326140173.6454.168.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=keybuk@google.com \
--cc=linux-bluetooth@vger.kernel.org \
/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