Hi Luiz, >> (Resent in plain text; sorry for double send) >> >> I took a brief look at this error and uncovered that 6lowpan uses zero >> locks when using l2cap (should be using the channel lock). >> >> It seems like it would be better just to convert its direct use of >> l2cap channel into using an l2cap socket. > > I recall having some thought on that, I think having a socket like > RFCOMM does would be better but I don't remember why I haven't > follow-up on that, well we wanted to discontinue the bt specific > 6lowpan on the kernel side though. because sockets have their own locking issues for Bluetooth. We actually want to get rid of the internal socket usage. Regards Marcel
