[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] porting to arm
I think I have the same problem when sending l2cap_connect_rsp and req, for
example at the server side:
Current state of (64:65) is W4_L2CA_CONNECT_RSP
L2CAP l2ca_connect_ind : remote cid : 65 psm 0x3
RFCOMM get_new_rfcomm_con: rfcomm_con -> tty0
L2CAP l2cap_connect_rsp : rcid:65 lcid:64 result:0 status:0
set_acl_hdr (data=0x3391f "", len=16, pb=2 '\002', bc=0 '\000', hci_hdl=1)
0x02 0x01 0x20 0x10 0x00 0x00 0x03 0x01 0x08 0x00 0x40 0x00 0x41 0x00
0x00 0x00 0x00 0x00 0x00
This l2cap_connect_rsp is messed up after the hci header. How have you guys
that have seen this problem solved it?
I'm using arm-elf-gcc as a cross compiler.
> > Hello, I have difficulties to port the rfcomm part of the
> sources to arm.
> > In fact, I think we are in trouble as soon as we use
> bitfields (which are
> > often used in RFCOMM) e.g in a structure :
> Damn straight.
> The good new is, the problem is solved.
> The bad new is, I can't mail the patch. I try, but it never shows up.
> I'll try again.
> I won't send the patch with this mail, I'll send another one
> after this.
> Otherwise you might not get this message.
> To unsubscribe from this list: send the line "unsubscribe
> bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com