From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Michael Buesch <mb@bu3sch.de>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Dan E <trg_info@mailhaven.com>, Jouni Malinen <j@w1.fi>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Hostapd doesn't like crda
Date: Mon, 29 Dec 2008 13:27:36 -0500 [thread overview]
Message-ID: <1230575256.22537.3.camel@dv> (raw)
In-Reply-To: <20081229161828.GT5944@tesla>
On Mon, 2008-12-29 at 08:18 -0800, Luis R. Rodriguez wrote:
> > I think this wouldn't be hackish, but do we actually _know_ when crda has finished
> > uploading regulatory information? Does it do it all in one step?
>
> It would go in through another nl80211 command, NL80211_CMD_SET_REG. nl80211 eventually
> calls set_regdom() and this will set it, so if all goes well we can remove the timer
> at the end if its active (other means can call CRDA like for 802.11d or the wireless core
> upon initialization).
Can we have a command to _get_ regulatory settings? I think it would be
useful. Then hostapd could wait until the correct settings are active.
If it doesn't happen after some time, hostapd should exit with an error.
It would be even better if hostapd could wait for an event notifying of
the regulatory settings change.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-12-29 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 21:08 Hostapd doesn't like crda Michael Buesch
2008-12-27 22:08 ` Jouni Malinen
2008-12-28 13:26 ` Michael Buesch
2008-12-29 3:45 ` Dan E
2008-12-29 10:28 ` Michael Buesch
2008-12-29 15:56 ` Luis R. Rodriguez
2008-12-29 16:04 ` Michael Buesch
2008-12-29 16:18 ` Luis R. Rodriguez
2008-12-29 18:27 ` Pavel Roskin [this message]
2008-12-29 18:43 ` Luis R. Rodriguez
2008-12-29 19:21 ` Jouni Malinen
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=1230575256.22537.3.camel@dv \
--to=proski@gnu.org \
--cc=Luis.Rodriguez@Atheros.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mb@bu3sch.de \
--cc=trg_info@mailhaven.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).