public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Echtler <echtler@fs.tum.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Disabling HID Boot Protocol
Date: Mon, 25 Oct 2004 10:37:03 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0410250918550.25313@block.bubble> (raw)
In-Reply-To: <1098676850.6465.76.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> > However, still no reaction from the multimedia keys, at least none
> > in hcidump. Perhaps I should try 2.6.9-mh1?
> You see nothing in hcidump, when you press them? That is strange. What
> are the first HIDP messages for the keyboard in hcidump?
The first HIDP thing the keyboard says after connection:

> ACL data: handle 0x002c flags 0x02 dlen 14
    L2CAP(d): cid 0x41 len 10 [psm 19]
      HIDP: Data: Input report
      01 00 00 2C 00 00 00 00 00 
> ACL data: handle 0x002c flags 0x02 dlen 14
    L2CAP(d): cid 0x41 len 10 [psm 19]
      HIDP: Data: Input report
      01 00 00 00 00 00 00 00 00 

I recorded a BT dump which shows the keyboard connecting and two
keypresses (Space and the mute button). If desired, I can send it
to you personally.

Yours, Florian
- -- 
Homo homini lupus.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBfLsy7CzyshGvatgRAlE/AKCper8BaJ0etNXCu4Saa3SxMprNTwCgwSAf
aXZusBCfbu3mcSaNMSd+Ooc=
=+QKh
-----END PGP SIGNATURE-----

      reply	other threads:[~2004-10-25  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24 11:11 [Bluez-users] Disabling HID Boot Protocol Florian Echtler
2004-10-24 11:49 ` Marcel Holtmann
2004-10-24 16:34   ` Florian Echtler
2004-10-25  4:00     ` Marcel Holtmann
2004-10-25  8:37       ` Florian Echtler [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=Pine.LNX.4.61.0410250918550.25313@block.bubble \
    --to=echtler@fs.tum.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.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