Re: Keeping ACL link around after DBUS CreateBonding()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 2, 2008 at 11:36 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Nick,
>
>> I have memories of one of you talking about a custom change to bluez
>> to not immediately drop the ACL link once DBUS CreateBonding() has
>> finished (so that SDP can then be done on that link).
>>
>> Do you know the patch to do this? I am currently experimenting with
>> changing the timer expiry in hci_conn_put() for disc_timer. Maybe
>> there's a nicer way.
>
> do you have a trace in BTSnoop format for me. We are using L2CAP raw
> sockets for bonding and thus the default 2 seconds disconnect timeout
> applies. Enough time to get SDP started on the same link. If the remote
> side however decides to disconnect us, we are out of luck.

For this situation the ACL connection is not complete, so the 10ms
timeout applies. I have a patch to use the 2 second timeout code path
for both connecting and connected. I wonder if this would be useful in
mainline, or if this is just a strange behavior of our BRF6300 (it
completes pin code and link key before the ACL link is reported as
connected). I'll send you some logs tomorrow if that would still help.

Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux