Re: [Bluez-users] error on connect

[Marcel Holtmann <marcel@holtmann.org>]

Hi Marco,

> Do I get this right:
> - The ACL packet that cause the problem is sent before the connection is 
> etablished. This is ok and defined in the specification.

this is not ok and can also not happen since you only get the connection
handle from the connect complete event. In BlueZ this is indicated with
the hci_proto_connect_cfm() and only at that time the L2CAP layer starts
sending out its connect request. Please check the sender side again.

> - The received dongle is responsible to keep this packet back until the 
> connection is etablished and process them then.

In general yes, they should queue the data packet.

> - the csr dongles seem to handle this correct.

So far I've never seen this problem with a CSR dongle. Not even with the
very old ones.

> - the broadcom dongle seem to don't handle this correct. they probably 
> suffer a race condition. so they may work or may not work.

Maybe the stacks Broadcom tested their dongles with are needing some
time before they can send out the first ACL data packet. Or they do
other HCI tasks before they start L2CAP. However this is a problem with
the dongle, because the ACL data packet is not allowed at that time.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users