Re: [Bluez-devel] About l2cap patch to handle multiple connections....

[Fabrizio Guglielmino <guglielmino@infitsrl.com>]

I have not made great progresses but I try to explain them looking some 
one can help me.
System hangs after l2cap_connect_cfm function, this is called for every 
device to which I try to connect to (in my case only 2).

In non-patched version of l2cap_connect_cfm there was a call to 
l2cap_conn_ready if status was 0x00 on a valid conn.
In patched version l2cap_conn_ready is no more called. l2cap_conn_ready 
it seems to execute the l2cap connection request so is
this a forgetfulness? I've try to insert the call but without success 
(system hangs again) so if the response to previous question is true this
is not the only problem.

I hope someone (more expert of me on this layer) can help to make me to 
work this patch.

thanks
Fabrizio

Marcel Holtmann ha scritto:
> Hi Fabrizio,
>
>   
>> Hi I'm trying to play with the patch to make it work (as Marcel said it 
>> hangs my machine).
>>
>> First I'm trying a simple debug by printing to find where it hangs...
>>
>> There is a first question about this: various BT_DBG statements that 
>> print bluetooth address
>> in string format (using batostr) print them in reverse 
>> order(00:01:02.... is printed 02:01:00).
>> My test machine is a powerpc based mac, I've used in user-space the 
>> ba2str  without problems in same architecture
>> so I'm confused about this.
>>     
>
> this is normal. We don't bother to swap the address for the debug
> messages. In Bluetooth the address is always used in the reversed order,
> but for the human eyes it is swapped.
>
>   
>> An other dubt is about following log :
>>
>> Jul 31 10:36:39 localhost kernel: [  596.604617] Bluetooth: 
>> 00:00:00:00:00:00 -> 44:53:25:E3:01:00 psm 0x300
>> Jul 31 10:36:39 localhost kernel: [  596.606752] Bluetooth: 
>> 00:00:00:00:00:00 -> 20:68:2A:2D:09:00 psm 0x300
>> (address are in reverse order as I said above)
>>
>> Why psm is 0x300? May be also the psm in reverse order and really it's 
>> 0x003 (RFCOMM) as I would have expected ?
>>     
>
> This looks like a big endian bug. The PSM value is in little endian
> order.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel