On Mon, Mar 1, 2010 at 8:17 PM, Sujith <Sujith.Manoharan@xxxxxxxxxxx> wrote: > Luis R. Rodriguez wrote: >> Interesting approach, instead of having two modules you linked lib.o >> twice to two separate modules, ath9k.ko and ath9k_htc.ko. While this >> does reduce module proliferation is there any advantage to that over >> the approach of stuffing these into one common module shared between >> both? >> >> The benefit of doing it as a module is if both are built-in you reduce >> the final kernel size. On my box with debugging this is 256 KB. > > The built-in case would be mostly useful in embedded systems (SoC etc ..). > And it is likely to be either ath9k or ath9k_htc. I don't think that > both family of chipsets can exist simultaneously. ChromeOs builds everything as built-in so in that case you will have both eventually enabled. > And since the code that is shared is very minimal (a few general routines and crypto), > it felt reasonable to just stuff into a common library. Although it may be a few common helpers it could grow to share common mac80211 helpers. After all, there are a few calls which could simply be shared. Luis -- 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
