Hi Mat,
On Wed, Aug 10, 2011 at 8:38 PM, Mat Martineau <mathewm@xxxxxxxxxxxxxx> wrote:
>> +struct hci_chan {
>> + struct list_head list;
>> + struct hci_conn *conn;
>> + struct sk_buff_head data_q;
>> + unsigned int sent;
>> +}
>
> At the BlueZ summit last year, the group settled on using an "HCI channel"
> as an abstraction for AMP logical links. We have a hci_chan struct already
> that you could add to. Before making changes to HCI data structures, could
> we first work on upstreaming the AMP HCI changes (which also include some
> QoS-related code)?
If just you told us this before I would have not spend time
implementing it, so could you please sent this patches ASAP, otherwise
I will just send mine that just address the prioritization
Btw, the thread intent is perhaps becoming too broad, we should focus
in small steps lets say first HCI Channel, then we continue from
there.
--
Luiz Augusto von Dentz
--
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
