linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>,
	Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] iwl3945: added channel sysfs entry
Date: Fri, 26 Sep 2008 13:28:04 +0800	[thread overview]
Message-ID: <1222406884.2510.534.camel@debian.sh.intel.com> (raw)
In-Reply-To: <43e72e890809252113h624a8d91jd859935ae5afed10@mail.gmail.com>

On Thu, 2008-09-25 at 21:13 -0700, Luis R. Rodriguez wrote:
> CONFIG_WIRELESS_OLD_REGULATORY is a temporary solution, the right
> solution for you is to build the regulatory domain with the provided
> API as discussed at OLS. Additionally distributions can start picking
> up iw and crda. I can also see NetworkManager asking the kernel to set
> the regulatory domain just as with iw, based on the user's defined
> country somewhere.

You brought it up. And I also want to discuss it. We do want to support
it. But the 3945/4965/5000 hardwares doesn't have the alpha2 information
in their EEPROMs (btw, 2100/2200 does support that). Instead, they have
a band/channel table including freq, tx power, etc in the EEPROM. So a
simple regulatory_hint() API doesn't work. We need a way to export the
channel details to CRDA.

Thanks,
-yi


  parent reply	other threads:[~2008-09-26  5:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  5:57 [PATCH] iwl3945: added channel sysfs entry Zhu Yi
2008-09-24  5:57 ` [PATCH] iwlwifi: don't fail if scan is issued too early Zhu Yi
2008-09-24  8:44 ` [PATCH] iwl3945: added channel sysfs entry Johannes Berg
2008-09-24 10:52   ` Dan Williams
2008-09-25  7:34   ` Zhu Yi
2008-09-25  9:23     ` Johannes Berg
2008-09-25 11:04       ` Tomas Winkler
2008-09-25 11:21         ` Johannes Berg
2008-09-25 11:50           ` Tomas Winkler
2008-09-26  3:54       ` Zhu Yi
2008-09-26  4:13         ` Luis R. Rodriguez
2008-09-26  5:13           ` Zhu Yi
2008-09-26  5:16             ` Zhu Yi
2008-09-26  5:28           ` Zhu Yi [this message]
2008-09-26  5:39             ` Luis R. Rodriguez
2008-09-26  5:40               ` Luis R. Rodriguez
2008-09-26  5:44               ` Zhu Yi

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=1222406884.2510.534.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=abhijeet.kolekar@intel.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).