linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: Pavel Roskin <proski@gnu.org>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] crda: use strerror() to report error code verbosely
Date: Tue, 23 Dec 2008 04:14:34 -0800	[thread overview]
Message-ID: <20081223121434.GA27316@tesla> (raw)
In-Reply-To: <2da21fe50812230041q1d844215o589c79c351966e50@mail.gmail.com>

On Tue, Dec 23, 2008 at 12:41:21AM -0800, Davide Pesavento wrote:
> On Tue, Dec 23, 2008 at 07:20, Pavel Roskin <proski@gnu.org> wrote:
> > Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
> >
> >> You don't need to build this unless you want to define your own rules.
> >
> > I see.
> >
> >> And if you do and want to use the signature stuff you need to copy the
> >> RSA public key into pubkeys/ directory of CRDA. Did you try that?
> >
> > No, I just wanted to install the most current regulatory database.  Perhaps
> > the error message should be more clear.
> >
> > With both CONFIG_CFG80211_REG_DEBUG, CONFIG_WIRELESS_OLD_REGULATORY enabled
> > and modular mac80211 and cfg80211, regdomain is set correctly from udev:
> >
> > [    7.642548] cfg80211: Using static regulatory domain info
> > [    7.642551] cfg80211: Regulatory domain: US
> > [    8.697261] cfg80211: Regulatory domain changed to country: US
> >
> > However, changing it to anything doesn't work:
> >
> > [root@ct proski]# COUNTRY=00 crda
> > Failed to set regulatory domain: -22
> > [root@ct proski]# COUNTRY=US crda
> > Failed to set regulatory domain: -22
> > [root@ct proski]# COUNTRY=DE crda
> > Failed to set regulatory domain: -22
> > [root@ct proski]#
> >
> > Maybe it can only be set once?  But then -EBUSY would be more reasonable.
> >
> 
> AFAIK, you have to use `iw reg set <country>` to manually change it.

Affirmative, or you can use wpa_supplicant from the git tree and add to your conf:

COUNTRY=US

  Luis

  reply	other threads:[~2008-12-23 12:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23  5:00 [PATCH] crda: use strerror() to report error code verbosely Pavel Roskin
2008-12-23  5:25 ` ath5k: whether "txpower off" is supported ? Xu, Martin
2008-12-23  6:07   ` Luis R. Rodriguez
2008-12-23  5:27 ` [PATCH] crda: use strerror() to report error code verbosely Luis R. Rodriguez
2008-12-23  5:49   ` Pavel Roskin
2008-12-23  5:57     ` Luis R. Rodriguez
2008-12-23  6:20       ` Pavel Roskin
2008-12-23  6:22         ` Luis R. Rodriguez
2008-12-23 14:58           ` Pavel Roskin
2008-12-23 15:03             ` Luis R. Rodriguez
2008-12-23 15:05               ` Luis R. Rodriguez
2008-12-23  8:41         ` Davide Pesavento
2008-12-23 12:14           ` Luis R. Rodriguez [this message]
2008-12-23 14:41           ` Pavel Roskin
2008-12-23 14:57             ` Luis R. Rodriguez
2008-12-23 15:03               ` Pavel Roskin

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=20081223121434.GA27316@tesla \
    --to=lrodriguez@atheros.com \
    --cc=davidepesa@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=proski@gnu.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 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).