Hi Andres, > > > I discovered that if EMBEDDED=y, one can accidentally build a > > > mac80211 stack and drivers w/ no rate control algorithm. For > > > drivers like RTL8187 that don't supply their own RC algorithms, > > > this will cause ieee80211_register_hw to fail (making the driver > > > unusable). > > > > > > This will tell kconfig to provide a warning if no rate control > > > algorithms have been selected. That'll at least warn the user; > > > users that know that their drivers supply a rate control algorithm > > > can safely ignore the warning, and those who don't know (or who > > > expect to be using multiple drivers) can select a default RC > > > algorithm. > > > > this is not an acceptable policy. You are generating false positives > > now for drivers that have been fine before. > > > > Unacceptable how? It's a warning, not a requirement. It's > telling the user to double-check their config. and why not either whitelist drivers with their own rate control or have the ones without rate control depend on a selection. You can't really expect all users to know which driver comes with rate control and which doesn't. Regards Marcel -- 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
