Luis R. Rodriguez wrote: > Apart from that there's one long term objective which I noticed > was removed from my initial implementation approach. On this driver > the the hif/htc code linked all together while I had these separated. > The reason for separation was in the future different buses would be > supported and so a different HIF transport would be required. The > typical HTC Atheros driver tends to bundle HTC together and re-build > HTC for a new driver sort of how you've used lib.o for ath9k and > ath9k_htc only that each htc.o would be modified to suit each new > driver and firmware API. I think that's pointless and gross and tried > to work on a way HTC can exist as a registrar, sharing all things HTC > that are possible. Consider PCI support for a device similar to AR9271 > with, say a AR9280 MAC and radios. In such a case (and very possible) > we'd need an HIF PCI added, so you will need to eventually address > separation anyway. I am not sure what your original approach was - but a new bus implementation would just be a hif_bleh.c. HTC would remain unchanged for the most part. Well almost, except if credit distribution is required, it would be added to HTC. Or am I missing something ? Sujith -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
