Hi Yi, > > > Does below scenario an expected behaviour? > > > > > > 0. A system with iwl3945 BG card and iwl4965 AGN card. > > > 1. insmod iwl3945 -> regulatory_hint(, 99, rd) return 0; > > > 2. insmod iwl4965 -> regulatory_hint(, 99, rd2) return -EALREADY; > > > 3. iwl4965 has no A band support! > > > > Yeah, I think this is expected, and the solution is to install crda and > > iw and set the regulatory domain manually to whatever country you're in > > rather than your cards SKU. > > Let's use the solution at this time. Just a notion that the regdomain in > kernel doesn't sort out very well in some circumstance without user > intervention. that is what Johannes and I agreed on. We do have to make this work when no userspace is present or is limited due to the design of the embedded system in question. In that case the first regulatory hint wins. Johannes, we could just add a kernel warning if we have mismatched regulatory hints and userspace was not involved until now. So at least it shows up in dmesg and can be debugged easily if needed. 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
