From: Arend van Spriel <arend@broadcom.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Sander Eikelenboom <linux@eikelenboom.it>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Julian Calaby <julian.calaby@gmail.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Avinash Patil <avinashapatil@gmail.com>
Subject: Re: [cfg80211 / iwlwifi] setting wireless regulatory domain doesn't work.
Date: Wed, 18 Dec 2013 10:16:38 +0100 [thread overview]
Message-ID: <52B167F6.5060209@broadcom.com> (raw)
In-Reply-To: <CA+55aFxQg6=MAWEkEGz64Hz8OawvPyX=fpBOjY8cGBL5XgB9WQ@mail.gmail.com>
On 12/17/2013 11:06 PM, Linus Torvalds wrote:
> We have literally had this *exact* same issue with firmware loading.
> Network drivers shouldn't try to load firmware at module load time.
> Same deal.
It is kind of a chicken and egg problem for (wireless) networking
drivers. To get IFF_UP from the network layer you have to register a
netdevice. For wireless drivers this means you have to register a wiphy
device with cfg80211 which flags capabilities and optionally are custom
regulatory domain. That information depends on the device and firmware
used. And there we have a full circle.
Regards,
Arend
next prev parent reply other threads:[~2013-12-18 9:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 17:43 [cfg80211 / iwlwifi] setting wireless regulatory domain doesn't work Sander Eikelenboom
2013-10-23 12:28 ` Sander Eikelenboom
2013-10-23 12:28 ` Sander Eikelenboom
2013-12-11 15:17 ` Sander Eikelenboom
2013-12-11 15:38 ` Luis R. Rodriguez
2013-12-11 16:53 ` Sander Eikelenboom
2013-12-11 17:14 ` Luis R. Rodriguez
2013-12-11 17:28 ` Sander Eikelenboom
2013-12-11 17:53 ` Luis R. Rodriguez
2013-12-11 18:02 ` Luis R. Rodriguez
2013-12-11 18:11 ` Sander Eikelenboom
2013-12-11 18:11 ` Sander Eikelenboom
2013-12-11 18:38 ` Luis R. Rodriguez
2013-12-11 19:06 ` Sander Eikelenboom
2013-12-18 18:54 ` Luis R. Rodriguez
2013-12-16 11:22 ` Sander Eikelenboom
2013-12-16 11:37 ` Arend van Spriel
2013-12-16 12:56 ` Sander Eikelenboom
2013-12-17 2:17 ` Julian Calaby
2013-12-17 9:45 ` Sander Eikelenboom
2013-12-17 9:45 ` Sander Eikelenboom
2013-12-17 20:33 ` Sander Eikelenboom
2013-12-17 21:27 ` Ben Hutchings
2013-12-17 21:49 ` Sander Eikelenboom
2013-12-17 22:06 ` Linus Torvalds
2013-12-18 9:16 ` Arend van Spriel [this message]
2013-12-18 9:18 ` Grumbach, Emmanuel
2013-12-18 9:18 ` Grumbach, Emmanuel
2013-12-18 9:18 ` Grumbach, Emmanuel
2013-12-18 9:25 ` Sander Eikelenboom
2013-12-18 9:26 ` Johannes Berg
2013-12-18 10:48 ` Sander Eikelenboom
2013-12-18 19:43 ` Luis R. Rodriguez
2013-12-18 19:45 ` Sander Eikelenboom
2013-12-19 4:57 ` Luis R. Rodriguez
2013-12-17 23:35 ` Julian Calaby
2013-12-18 7:50 ` Pontus Fuchs
2013-12-18 8:58 ` Arend van Spriel
2013-12-18 19:27 ` Luis R. Rodriguez
2013-12-18 18:29 ` Luis R. Rodriguez
2013-12-18 18:54 ` Sander Eikelenboom
2013-12-18 19:42 ` Luis R. Rodriguez
[not found] ` <CAJwzM1nwFa7z5gwh42aj39M2dxVXnuecDrhQkVyL+DDFAXwwbg@mail.gmail.com>
2013-12-11 17:00 ` Sander Eikelenboom
2013-12-11 17:00 ` Sander Eikelenboom
2013-12-11 17:17 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B167F6.5060209@broadcom.com \
--to=arend@broadcom.com \
--cc=avinashapatil@gmail.com \
--cc=ben@decadent.org.uk \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=julian.calaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=linville@tuxdriver.com \
--cc=mcgrof@do-not-panic.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.