public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Kieling <konrad.kieling@imperial.ac.uk>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hid keyboard events get lost
Date: Mon, 28 May 2007 21:50:01 +0100	[thread overview]
Message-ID: <465B4079.8000509@imperial.ac.uk> (raw)
In-Reply-To: <1180360514.21432.102.camel@aeonflux.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 381 bytes --]

dear marcel,
yes, i totally agree not to screw things up for a non-standard device.
however, to understand things better, could you explain to me why l2cap
sends more config requests to change the mtu although it already agreed
on the one suggested by the keyboard (hcidump is in one of my recent
postings), or do i misinterpret what's going on?

all the best,
  konrad


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-05-28 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 15:16 [Bluez-users] hid keyboard events get lost Konrad Kieling
2007-05-28 12:19 ` Konrad Kieling
2007-05-28 13:55   ` Marcel Holtmann
2007-05-28 20:50     ` Konrad Kieling [this message]
2007-05-29  4: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=465B4079.8000509@imperial.ac.uk \
    --to=konrad.kieling@imperial.ac.uk \
    --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