linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>
Subject: Re: [PATCH] iwl3945: added channel sysfs entry
Date: Fri, 26 Sep 2008 11:54:02 +0800	[thread overview]
Message-ID: <1222401242.2510.519.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1222334592.10563.59.camel@johannes.berg>

On Thu, 2008-09-25 at 03:23 -0600, Johannes Berg wrote:
> Not that I understand why you need that since iw shows all channels
> you
> are registering (albeit with possibly a few more flags like
> "disabled"),
> but yeah, if anything all this stuff should be in debugfs.

The real user for the function is the automated test cases of our
validation team running nightly. Greppig dmesg is not reliable and iw is
not mature enough (at least not included in major distros). We will move
it to debugfs for now. After iw is as common as iwconfig, we will
eventually remove this.

> There's also
> this little fact that this channel list shouldn't ever get used, you
> should be (and afaik are since I fixed it) using what the regdomain is
> enforcing, and you're already printing the channel list when enough
> debugging flags are set on driver load.

This is used for debugging especially during the time regdomain is under
development. I've received quite a few bug reports that is due to
CONFIG_WIRELESS_OLD_REGULATORY is not enabled. I need at least a way to
tell the users this is due to your misconfig your regdomain or your
hardware is not capable to work on that channel.

Thanks,
-yi


  parent reply	other threads:[~2008-09-26  3:54 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 [this message]
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
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=1222401242.2510.519.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=abhijeet.kolekar@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).