On Mon, 21 Mar 2011 15:27:49 +0100, RafaÅ MiÅecki <zajec5@xxxxxxxxx> wrote:
The case is, we discussed ssb/ai driver layout few days ago. George
shared idea of layout I agree with, nobody shared any objections. If
everything goes fine, we should have nicely modularized driver/project
supporting Broadcom's buses.
Hi RafaÅ,
Does this give us one module supporting both buses or does it provide two
kernel modules (my preference)? I did ask you and George this question
earlier but I seem to have missed the response from you or George.
In this situation I'm not really interested is simple ai driver
stripped from brcm80211. According to me, it would led to harder
maintenance and harder implementation of support for such a driver in
b43.
I can imagine from b43 perspective the only good implementation would be
to stick with the current b43<->ssb interface. So what will you do when
another type of SoC interconnect is introduced. Forcing that in the same
API as well? If you and George propose a new carefully considered API
covering the functional capabilities of the current (and possibly future)
interconnect buses I am all for that.
To summarize this, my main issue (and Michael's, I think) is with the
dependency being imposed between ai and ssb. Having two completely
independent modules really makes more sense.
Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the
human
mind to correlate all its contents." - "The Call of Cthulhu"
--
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
