Re: [RFC v2] Bluetooth: Provide access to reassembled Rx packets

[Suraj <suraj@Atheros.com>]

Hi Marcel,

On 7/27/2010 4:12 AM, Marcel Holtmann wrote:

> So first of all, lets make something perfectly clear. All Bluetooth
> drivers are _transport_ drivers. They don't need to know what they are
> transporting. And in addition you should not look into the packets that
> you are sending or receiving. The Bluetooth core does that HCI packet
> parsing.
>
> This is how I want it and how this is going to stay. Everything else is
> an insane approach and cost every single driver overhead. In addition
> the lifetime rules of SKBs become more and more complicated. That is a
> pretty bad thing. It will result in excessive memory usage and will
> cause problems.

I understand the point that you are making. But If I am not mistaken, 
HCI transport driver is the only part of the system that could be vendor 
specific ( HCI ATH3K, HCI LL etc). So a vendor specific command or event 
makes more sense to a transport driver than anybody else.

Is there anyway this requirement can be sufficed without causing the 
issues you have mentioned above?
>
> Regards
>
> Marcel
>
>

Regards
Suraj