On Wed, Jan 29, 2014 at 12:17 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2014-01-28 at 11:42 -0800, Luis R. Rodriguez wrote: > >> > You mean we should introduce: >> > iw wlanX reg get? >> >> Sure, and iw dev reg get can also display what it does now but then >> also iterate over all wiphys and also display all wiphy's own regd if >> they have any. > > I'm not really sure I see much point in all this - what userspace > eventually cares about isn't the reg data but the channel list that can > be obtained with (the equivalent of) iw list. That's true if you don't consider important the data that applied the rules. This can be useful and if not exposed by userspace API I can at least see this useful for debugfs. As for userspace API -- the data reflects *calibrated* phy data, I see no reason why it shouldn't be exposed just as other attributes of the phy, but I can see this growing to other subjective areas, but I think we have things down with a general usable generic regulatory domain data structure. I can't say I care though :D just my $0.02 from a parking distance. 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
