From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Michael Wu" <flamingice@sourmilk.net>
Subject: Re: [WIP] cfg80211 infrastructure for channels/bitrates, mac80211 and b43 conversion
Date: Fri, 14 Dec 2007 09:20:50 -0500 [thread overview]
Message-ID: <43e72e890712140620h90676b5x831563376ccbc1ec@mail.gmail.com> (raw)
In-Reply-To: <1197631004.16079.25.camel@johannes.berg>
On Dec 14, 2007 6:16 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
>
> This patch creates new cfg80211 wiphy API for channel and bitrate
> registration and converts mac80211 (and, as an example and for testing,
> b43) to the new API. The old mac80211 API is completely ripped out.
>
> So far, it has survived all my testing: only active scanning :)
>
> Note that this has one major regression: with this patch you will have
> all hardware channels available because I completely ripped out the
> regulatory "enforcement" code. I believe that is for the better because
> then we can cleanly add new regulatory enforcement code to cfg80211.
>
> I've also ripped out all power adjustment and antenna gain fields/code,
> this too will have to be added back, again I believe part of new
> regulatory enforcement code.
>
> Along with the regulatory code I've also ripped out the
> IEEE80211_HW_DEFAULT_REG_DOMAIN_CONFIGURED flag, I believe it to be
> unnecessary if the hardware simply gives us whatever channels it wants
> to support and we then enable/disable them as required, which is pretty
> much required for travelling. Those with varying EEPROMs will obviously
> have to allocate the array dynamically for each wiphy.
>
> Here are a few more TODOs:
> * do ERP stuff again, this is currently pretty broken (even before the
> patch)
> * do basic rate handling again, this is probably broken before the
> patch
> * do mandatory rate handling again (probably broken as well, partially
> done)
> * reimplement channel use calculations... they looked too broken to
> worry about right now
>
> Luis, please see the API in include/net/wireless.h. You'll have to add
> to that for the regulatory stuff.
Looks great, I'm glad I don't have to deal with these changes now :)
just a few questions and observations:
* I didn't see the definition for ieee80211_channel_to_frequency() and
its counter part, where are those defined?
* This patch didn't have b43 changes
* I'd like to base work on these patches, where can I find them the
complete series to wget
Luis
next prev parent reply other threads:[~2007-12-14 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 11:16 [WIP] cfg80211 infrastructure for channels/bitrates, mac80211 and b43 conversion Johannes Berg
2007-12-14 12:24 ` Johannes Berg
2007-12-14 14:20 ` Luis R. Rodriguez [this message]
2007-12-14 14:40 ` Johannes Berg
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=43e72e890712140620h90676b5x831563376ccbc1ec@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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