public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: lan zhu <zhu.lan.cn@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: bluetooth pairing issue in kernel 2.6.27
Date: Wed, 20 May 2009 14:44:07 +0800	[thread overview]
Message-ID: <113d36d80905192344p3caf4c3dm3ebe1a5c00eda3f9@mail.gmail.com> (raw)
In-Reply-To: <113d36d80905192341q4aa2463dyd0b1ed107792cff0@mail.gmail.com>

When pairing two Android devices which are supported by Bluez on
kernel 2.6.27, it will always fail if the user can't finish the whole
procedure in 10 seconds. After some analysis we found the root cause
is that Bluez's HCI link's time out timer is set to 10s in the kernel,
and in Bluez's create_bonding() function it calls l2raw_connect() to
create only HCI link without L2CAP channel.

One easy way to fix this issue is to create L2CAP link when creating
bonding, but this is not a final solution, because
according to Bluetooth Specification, creating L2CAP link is only
optional in the bonding establishment procedure, so the thorough way
to fix it is to alter the HCI link's time out timer when handling
bonding request.

Does anyone know has this been fixed on Bluez kernel's patch on
2.6.27, or on the 2.6.29 and later's kernel?

Thanks,
Zhu Lan

       reply	other threads:[~2009-05-20  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <113d36d80905192336i337964a9hcbaa5ccb729434b6@mail.gmail.com>
     [not found] ` <113d36d80905192341q4aa2463dyd0b1ed107792cff0@mail.gmail.com>
2009-05-20  6:44   ` lan zhu [this message]
2009-05-20  7:48     ` bluetooth pairing issue in kernel 2.6.27 Marcel Holtmann
2009-05-20 17:56       ` bluetooth pairing issue in kernel 2.6.30-rc5 balaji palaniswami
2009-05-20 19:56         ` 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=113d36d80905192344p3caf4c3dm3ebe1a5c00eda3f9@mail.gmail.com \
    --to=zhu.lan.cn@gmail.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