All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Leffler <sam@errno.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] Add new regulatory framework for Linux wireless
Date: Thu, 10 Jul 2008 08:52:46 -0700	[thread overview]
Message-ID: <4876304E.9070508@errno.com> (raw)
In-Reply-To: <20080710152415.GK17936@ruslug.rutgers.edu>

Luis R. Rodriguez wrote:
> The industry currently has different techniques for parsing and using
> Country IEs. What I currently propose is to take the common denominator
> between what the AP provides, what CRDA has and what the driver can
> provide privately through its callback. So the wireless core can keep
> as the common denominator between the AP's Country IE and what CRDA
> has for the alpha2 provided by the Country IE. Drivers themselves can
> further enhance regulatory enforcement by relying on private driver
> data if they wish so.
>
>   
Can you elaborate on the first sentence?  Are you just saying that some 
software blindly trusts the contents of the country IE and doesn't 
constrain it's use (as you describe)?  Or are you saying drivers 
interpret the contents of the country IE in ways different than spec'd?

    Sam


  reply	other threads:[~2008-07-10 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 15:24 [RFC] Add new regulatory framework for Linux wireless Luis R. Rodriguez
2008-07-10 15:52 ` Sam Leffler [this message]
2008-07-10 19:38   ` Luis R. Rodriguez
2008-07-10 20:34     ` Sam Leffler
2008-07-10 20:45       ` Luis R. Rodriguez
2008-07-10 16:22 ` Johannes Berg
2008-07-10 19:34   ` Luis R. Rodriguez
2008-07-10 19:38     ` Johannes Berg
2008-07-10 19:58       ` Luis R. Rodriguez
2008-07-10 19:51     ` 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=4876304E.9070508@errno.com \
    --to=sam@errno.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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 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.