Return-Path: MIME-Version: 1.0 In-Reply-To: <1326140173.6454.168.camel@aeonflux> References: <1325893697.6454.113.camel@aeonflux> <1325900406.6454.116.camel@aeonflux> <1326138887.6454.165.camel@aeonflux> <1326140173.6454.168.camel@aeonflux> Date: Mon, 9 Jan 2012 17:10:34 -0800 Message-ID: Subject: Re: Bluetooth 2.1 keyboard not sending keypress notifications From: Scott James Remnant To: Marcel Holtmann Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 List-ID: On Mon, Jan 9, 2012 at 12:16 PM, Marcel Holtmann wrot= e: > > 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. > Ok, so here's what's happening: When it sees that it's pairing with an Apple keyboard, OS X makes an L2CAP connection to the HID Interrupt PSM (0x13) between the initial connection to the keyboard and the authentication request. This connection receives a notification every time a key is pressed (any key, OS X doesn't care, it moves along to the next). Once authentication is complete, OS X drops this L2CAP connection Scott -- Scott James Remnant=A0|=A0Chrome OS Systems=A0|=A0keybuk@google.com=A0|=A0G= oogle