On Thu, Dec 9, 2010 at 1:17 PM, Pavan Savoy <pavan_savoy@xxxxxxxx> wrote: > Gustavo, > > On Tue, Dec 7, 2010 at 3:05 AM, Vitaly Wool <vitalywool@xxxxxxxxx> wrote: >> Hi Gustavo, >> >> On Mon, Dec 6, 2010 at 10:23 PM, Gustavo F. Padovan >> <padovan@xxxxxxxxxxxxxx> wrote: >> >>> Can't you differentiate Bluetooth data in a generic way, withou looking if it >>> is ACL, SCO or HCI EVENT? That done, you can just accumulate in a buffer all >>> the Bluetooth data you received in that stream then send it to Bluetooth >>> driver after finish that stream processing. >> >> I'm afraid he can't do this because he needs to route events to the >> appropriate entity (BT/FM/GPS). I'm not sure how it can be done >> without analyzing the incoming packet. > > Think of TI-ST driver as a extension to the HCI-H4 driver or HCI-LL > with FM and GPS being the additional protocols, and more protocols > coming in future... > So some driver has to have a knowledge of the protocols which are on chip. > the basic arch can be found @ http://omappedia.org/wiki/Wilink_ST Gustavo, Marcel, Any suggestion to this? Is including net/bluetooth headers a problem? and is this a big blocking factor to try and push it to mainline? I know it would be a dumb question, but do you want me to redeclare the ACL, SCO and Event headers structures? All I need is the off-set of the structure where the payload length resides.... Please suggest ... regards, Pavan > As Vitaly rightly pointed out, the TI-ST driver needs to peek into all > the protocol's data be it BT, FM or GPS to assemble fragmented data > (say ACL data coming out of TTY in 2 fragments) or fragment multiple > protocol data (say HCI-Event + FM Channel 8 event data).... > Note: we include even the FM and GPS headers to understand protocol > frames, but they lack a standard unlike Bluetooth... > > Since there lacks a generic way to differentiate BT, FM or GPS data at > TI-ST driver layer, Âplease suggest what can be done ... > > >> Thanks, >> Â Vitaly >> -- >> 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 >> > -- 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
