On Mon, Jun 23, 2014 at 9:26 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > On Mon, Jun 23, 2014 at 08:14:43PM +0300, Arik Nemtsov wrote: >> On Thu, Jun 19, 2014 at 2:34 AM, Luis R. Rodriguez >> <mcgrof@xxxxxxxxxxxxxxxx> wrote: >> > On Tue, Jun 10, 2014 at 11:55 PM, Arik Nemtsov <arik@xxxxxxxxxx> wrote: >> >> Allow driver and user hints to set the "world" regulatory domain, >> > >> > NACK - as expressed in the other patch, letting the drivers to use the >> > new API to set the world regulatory domain doesn't make sense as we >> > have custom apply stuff, and the world regulatory domain is not >> > something dynamic. >> >> Well we want to set the world regdomain from FW. This obviously >> happens after wiphy registration, so I don't think the custom apply >> can be used here? (since we generally want cfg80211 to own the >> regdomain settings). > > Can the driver not obtain the world regulatory domain from firmware > prior to wiphy registration? Why not? Since the FW is not running yet :) > > One thing to be careful on all this new API design is to ensure that > upon disconnect we want the driver to go back to the original state, > whatever that is. This particular part is unrelated to connection state AFAICT. It just allows someone (driver, user) to set the "00" regdomain. Arik -- 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
