Hi Marcel,
please give me an example of such a packet. I am currently failing to see what is wrong with the code and how this patch would actually help.
Is this for vendor packet types or does this actually happen with standard H:4 packet types?
Yes, this is for some vendor specific packets.
For example, I have to deal with LPM packet with the following format:
|0xf1|opcode|dlen|data|
This kind of packet can be easily added to the h4_recv_pkt list.
However, some of these packets don't have any data (just PM ack packet):
0xf1|0x03|0x00
If we receive this packet, the h4_recv_buf function will retrieve the
dlen (0) and just wait for more data. As long as there is not new data
received (new packet), the LPM packet is not transmitted to the bt core.
Regards,
Loic
--
Intel Open Source Technology Center
http://oss.intel.com/
--
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
