From: James Ketrenos <jketreno@linux.intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] d80211: Allow drivers to configure default regulatory domain
Date: Mon, 19 Feb 2007 12:37:16 -0800 [thread overview]
Message-ID: <45DA0A7C.5010001@linux.intel.com> (raw)
In-Reply-To: <20070219204938.29520759@griffin.suse.cz>
Jiri Benc wrote:
> On Sun, 18 Feb 2007 00:31:33 -0500, Michael Wu wrote:
>> This patch allows drivers to configure the default set of channels if the
>> device reports its default regulatory domain.
>
> How is a driver supposed to handle this? By walking through the channel
> list and based on some value obtained from its EEPROM (or firmware or
> whatever) set appropriate flags?
Yes.
> That sounds like a need for duplicate code in drivers.
Unfortunately it is vendor and device specific. I think we can
generalize things to provide helper functions and macros such that each
driver does it roughly the same way, but the stack itself can't do it.
> Shouldn't the stack accept a regdomain code (defined
> as an enum of integers or so) instead?
The hardware needs to tell the stack all the channels it supports and
the restrictions on those channels. The stack can then further restrict
the set of channels based on the user input to a "standard" set of
countries.
"regdomains" are not static maps; they evolve over time as governments
change their regulations. The channels and features supported by
hardware is static based on what the device was certified for.
James
next prev parent reply other threads:[~2007-02-19 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 5:31 [PATCH] d80211: Allow drivers to configure default regulatory domain Michael Wu
2007-02-19 19:49 ` Jiri Benc
2007-02-19 20:37 ` James Ketrenos [this message]
2007-02-19 20:59 ` Jiri Benc
2007-02-19 20:48 ` Michael Wu
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=45DA0A7C.5010001@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.