On Mon, 2008-10-20 at 21:58 -0700, Luis R. Rodriguez wrote: > 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. That's another story. For these devices, you can do what you want in user space. But for other correct behavioured devices, bypass regulatory framework is necessary. Because you have to trust the driver anyway. > >To solve the problem, > > What problem? The problem a driver is not able to give a SKU as regulatory hint. > > 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. It has nothing to do with ourdated rules. If a reg_rule is "wrong" in a device, it will still be wrong after the regulatory_hint() call. The current regulatory framework 100% trust the alpha2 or regdomain the driver provided. Thus it should also trust a hint from driver "bypass your regulatory check, I'll handle it myself". Thanks, -yi -- 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
