Hi Marcel,
On 25.05.2012 08:55, Marcel Holtmann wrote:
I was taking a look at Core spec change request document [1] and I found this:
Erratum 4215, LE connection complete event missing exception
"... On failure, for this event, all other parameters are not valid."
It clearly states this is an expected behavior and nullify those
parameters doesn't make the adapter broken.
Thus, in case of failure, we should not rely on those parameters
(BD_ADDR included) in order to properly handle LE Connection Complete
Events.
if this is so, then we should only do that and strictly enforce only one
LE connection attempt at a time. Also then there is no need to bother
with trying to check for the BD_ADDR later.
I created patch which does not allow 2nd outgoing LE connection attempt
and also reworded commit message for this one so it does state
explicitly that we should consider BDADDR from failed LE Connection
Complete as not valid and not use it.
Please take a look at my new patches (3 in total).
BR,
Andrzej
--
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
