> > Well I think that some userspace programs like network manager want to > > get a notification when for whatever reason the regdomain changes, and > > they want to be able to query which one is currently set, and things > > should be changeable. So you need at least three messages, NEW, GET, > > SET, no? > > Then I see us requiring: > > SET and GET, but not NEW. If only need to "set" "one" regulatory domain, > not create one and then set one. What do you think? Which message are you going to use to notify userspace that it changed? I'd say "NEW". > > > This is in case we wanted to support letting userspace query the kernel > > > what alpha2 it has set. I'm OK with not supporting this though but it > > > seemed it may have come in handy, hopefully not for abuse for other > > > things. > > > > Yeah true, we may want to be able to force a certain regdomain. > > Huh? I was talking about querying from userspace to the kernel for the > currently set alpha2, in case userspace may want to know what the kernel > last used to ask CRDA for a regdomain. > > How did this change to being able to fore a certain regdomain? Never mind. > Anyway, the only valid case where I see us needing to set a regdomain > manaullay is if an access point doesn't have an 802.11d country > information element. Which BTW -- soon we'll have to decide how we want > to implement, as we could either respect the IE with the channels passed > or just ask CRDA for the alpha2 given. Yeah, I dunno, either option seems possible. Maybe both? That is, ask the crda and then restrict to what the AP said (since that'll only be useful anyway) but then.. Hmm could get into trouble that way if AP is then on an unsupported channel ;) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
