On Mon, Oct 20, 2008 at 9:02 PM, Zhu Yi <yi.zhu@xxxxxxxxx> wrote: > On Mon, 2008-10-20 at 19:37 -0700, Luis R. Rodriguez wrote: >> The real problem here is you are not providing 5 GHz regulatory rules >> on a 2 GHz capable built-in card because you currently handle >> regulatory definitions by intersecting with hardware capabilities >> *and* the issue is what happens when a user plugs in a 5 GHz capable >> card. For >= iwlagn you have only a few SKUs so if you want you can >> put these definitions in the driver. As Tomas points out for iwl3945 >> and iwl4965 your SKUs are more complicated. Regulatory *is* >> complicated, and that is the current outsourcing of db.txt to >> userspace tries to accomplish. So the solution isn't to try to "fix" >> the regulatory infrastructure to handle your particular issue when a >> single Intel 2 GHz band card is present and you connect a dual band >> card by changing its overall design, because we already provide a >> mechanism to deal with overriding regulatory rules to help the user be >> more compliant. > > The real problem is you are forcing a device to provide a SKU even it is > not capable of. We would be if we didn't provide a db.txt with public regulatory definitions which people can contribute to, but we do have such db. > An SKU is not always necessary as long as the hardware > provides other ways to comply with regulatory. I do not agree. Consider old devices with built-in regulatory rules in hardware which go out of date. The regulatory framework accounts for such flaws and *helps* to remain compliant. >To solve the problem, What problem? > I'd > suggest a special regdomain named EVERYTHING. In the case the driver or > firmware enforces reg_rules, the core wireless reg_rules are safe to be > bypassed. You mean we add a flag to allow cfg80211 to ignore applying its central regulatory definition to a wiphy? I disagree -- consider outdated set of rules. > EVERYTHING can always be overwritten by other regdomains. For > example, when the user inserts a second card with regdomain of EU, EU > becomes the global regdomain. EU is not an ISO3166 alpha2 though, but I understand your point here, however the goal of building a central regulatory infrastructure for wireless was so it applies to all wiphys, not just mac80211 drivers. > A driver should only claim to use > EVERYTHING when it has its own way to enforce regulatory. Now the > concept changes to "the first non-EVERYTHING regdomain wins". > Thoughts? Yeah, again, I think this proposal is trying to solve the wrong problem. >> The proper solution is to either add 5 GHz regulatory rules to your >> regulatory_hint() and/or rely on crda to enable the 5 GHz channels >> required for the country the user is in. It is true that you need >> manual intervention and the way I am trying to resolve that is not by >> changing the design of the current regulatory infrastructure, instead >> I want to add country selection support to say wpa_supplicant or >> Network Manager. That, IMO, is how to address the problem correctly. I >> also suggested a temporary solution which a distribution can use which >> requires absolutely no manual user intervention, that of determining >> the country through whatever means the distribution deems more fit and >> calling iw reg set on $COUNTRY. > > See Marcel's comment on supporting new kernels with old applications. Old userspace still works, we can however require new userspace for new features. A compliant regulatory infrastructure is a feature. I'm inclined to believe a patch to add country selection on wpa_supplicant is the right next step. 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
