From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <linville@tuxdriver.com>, <johannes@sipsolutions.net>,
<linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: [PATCH 0/6] cfg80211: few regulatory updates
Date: Wed, 29 Oct 2008 18:19:48 -0700 [thread overview]
Message-ID: <1225329594-21704-1-git-send-email-lrodriguez@atheros.com> (raw)
Here's a set of updates to cfg80211 for regulatory.
This paves the way for 11d support and also addresses
recent complaints about no working 5 GHz channels. I believe
the compromise is reasonable.
I haven't tested this yet though, but I'll let you know tomorrow
how they go. Just wanted to get these out for review for now.
I've tested intersection in userspace on CRDA, check out running
./intersect regulatory.bin for an example of it intersecting
all regulatory domains. Special review with this is greatly
appreciated.
Working on 11d should be fairly easy after this.
Luis
next reply other threads:[~2008-10-30 1:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 1:19 Luis R. Rodriguez [this message]
2008-10-30 1:19 ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Luis R. Rodriguez
2008-10-30 1:19 ` [PATCH 2/6] cfg80211: Add regulatory domain intersection capability Luis R. Rodriguez
2008-10-30 1:19 ` [PATCH 3/6] cfg80211: make print_regdomain_info() static Luis R. Rodriguez
2008-10-30 1:19 ` [PATCH 4/6] cfg80211: make use of reg macros on REG_RULE Luis R. Rodriguez
2008-10-30 1:19 ` [PATCH 5/6] cfg80211: Add kdoc for struct regulatory_request Luis R. Rodriguez
2008-10-30 1:19 ` [PATCH 6/6] cfg80211: enable 5 GHz band for world regulatory domain Luis R. Rodriguez
2008-10-30 9:24 ` Johannes Berg
2008-10-30 16:09 ` Luis R. Rodriguez
2008-10-30 17:18 ` Johannes Berg
2008-10-30 17:43 ` Luis R. Rodriguez
2008-10-30 18:12 ` Jouni Malinen
2008-10-30 9:22 ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Johannes Berg
2008-10-30 19:40 ` 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=1225329594-21704-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.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