2008/2/1 Johannes Berg <johannes@xxxxxxxxxxxxxxxx>: > > > > I guess you could add a helper function that allocates a channels array > > > based on a frequency range. > > > > This is true but also it would be nice as it is the end points which > > drivers may want > > to access every now and then. I think its worth the few bytes. > > I'm not really worried about the space that needs, but I don't see why > the wiphy would need that information. Export capabilities to userspace would be the main reason. The bands can be iterated but why do iteration when we can just set the upper and lower limits? > Couldn't you keep it in your > driver's per-hw structure as it is? Sure, we could. But it seems it would be nice to have this information easily accessible to drivers and to userspace API. > Would cfg80211 be required to keep > them updated according to regulatory rules when the allowed channels > change? Nope, I'm just thinking in terms of "hw support capabilities". > I'm much more worried about all the code that would result in :) Yeah, I'm not thinking of it in terms of regulatory now. Just in terms of reasonable capability value accessible to drivers and to userspace. > But since you're not doing that right now anyway I'll just wait and see > what you come up with ;) Hey man, its tough when you have 2 laptops poop out on you in less than 2 months... this is my excuse this month. Its a new months so I get one. 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
