On Wednesday 08 December 2010, Par-Gunnar Hjalmdahl wrote: > > Marcel did previously suggest a bus-driver sort of a structure, where > > the transport are sort of adapter drivers, the data interpretation > > logic like splitting HCI-events, FM CH-8 packets all fall into the > > algos drivers and the actual Bluetooth driver or GPS or FM-V4L2 > > drivers falling into the client/protocol drivers.... > > What the cg2900 driver has now turned into is almost like the > cg2900_core acting as a bus, identifying which chip is connected and > choosing correct chip driver from this. This cg2900_core module should > not contain any vendor specific code. When identified, the chip driver > then uses MFD to setup channels according to the functionality it > supports (one MFD device per H4 channel). It's hard to explain > everything of the new architecture here. I would like you to check the > new patch set I'm trying hard to create at the moment. I will try to > get it out on Friday, but it's hard to promise anything (there is a > lot of work to do with it). There you could then see if it is > something you could consider useful. It sounds really good, I'm looking forward to your new patch set! If it's generic enough to replace the ti-st code, that would be a clear sign that you are on the right track ;-) I'm not asking to fix their code yourself, but it might be good to look at it and see if it would work. Arnd -- 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
