Hi Johannes, > > > 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. > > Yeah, we have to let one of them win, unless we want to add the > complexity with per-band hints as discussed in the other part of the > thread. > > > 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. > > We can probably do that, yeah, though we'd have to get the conditions > right to avoid showing that whenever you plug in a USB device to a > laptop that already has wireless built-in. I think it is fine to do so. Since plugging in an USB wireless card is expected to work and if we limit it, lets give the user at least some way to figure out why it is limited. Especially when your internal one is a BG-card and you external one is an A-card only (or combo). And you put it in to just access an A-network. 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
