From: Stefan Rompf <stefan@loplof.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: cfg80211 take 7
Date: Mon, 9 Oct 2006 14:52:06 +0200 [thread overview]
Message-ID: <200610091452.07098.stefan@loplof.de> (raw)
In-Reply-To: <1160394555.3258.3.camel@ux156>
Am Montag, 9. Oktober 2006 13:49 schrieb Johannes Berg:
> Yeah, probably makes sense. Though, maybe not just the band but a set of
> channels instead?
Yes, this would allow us to keep the definition of a band out of kernel. But
to distinguish between 802.11 b and g, we'd need a set of channels and
allowed modulations. I haven't looked at Larry's regulatory domain stuff yet,
but maybe band selection could use the same data structure. cfg80211 would
then just calculate the intersection of user supplied set and set permitted
by regulations.
Hopefully there is no country that forbids the user *NOT* to scan a specific
channel ;)
Stefan
next prev parent reply other threads:[~2006-10-09 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 14:59 cfg80211 take 7 Johannes Berg
2006-10-06 15:07 ` Johannes Berg
2006-10-09 11:22 ` Stefan Rompf
[not found] ` <200610091322.10495.stefan@loplof.de>
2006-10-09 11:49 ` Johannes Berg
2006-10-09 12:52 ` Stefan Rompf [this message]
2006-10-09 14:16 ` Larry Finger
2006-10-09 18:38 ` David Kimdon
2006-10-09 22:01 ` 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=200610091452.07098.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=johannes@sipsolutions.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).