linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Morrison <bdm@fenrir.org.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: [ipw3945-devel] iwl3945: Disabled channels
Date: Mon, 21 Apr 2008 16:01:41 +0100	[thread overview]
Message-ID: <480CAC55.1000704@fenrir.org.uk> (raw)
In-Reply-To: <1208788898.26186.105.camel@johannes.berg>

Johannes Berg wrote:
> 
> I can't say I particularly care about France, but even from the
> wikipedia page you linked previously it is rather clear that we cannot
> define a "EU" regulatory domain because Spain and France are in the EU
> yet have not adopted the "European" regulatory requirements.

That makes it all very difficult, I think that an EU domain is OK 
provided that there is also a Spanish domain. Or maybe the EU domain 
should actually be named ETSI (which was my original preference, it was 
John Linville that said EU hence why I used it).

I'll have to see if I can work out what the allowable domains are for 
the Ralink RT2500 drivers, under Windows for instance. I know that are 
are considerable number of choices, certainly more than US/EU/JP. That 
might provide a good clue.

I'm beginning to wonder if anyone has this correct in their shipping 
products, especially from a power point of view. The regulatory stuff is 
supposed to be prevented from manipulation by the user, but if I were in 
the US and I entered "JP" for the regdom, then I can break the regs with 
nothing to stop me anyway. You couldn't operate with a worldwide lowest 
common denominator approach, it would be the equivalent of turning the 
wireless hardware off!

Does anyone know how the EEPROM contents are supposed to work for the 
Intel hardware? How they are queried and compared with kernel and 
userspace programs?

-- 

Brian

  reply	other threads:[~2008-04-21 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fuhkfp$mnk$1@ger.gmane.org>
2008-04-21  9:14 ` [ipw3945-devel] iwl3945: Disabled channels Brian Morrison
2008-04-21 13:50   ` Johannes Berg
2008-04-21 14:19     ` Brian Morrison
2008-04-21 14:41       ` Johannes Berg
2008-04-21 15:01         ` Brian Morrison [this message]
2008-04-21 15:12           ` Johannes Berg
2008-04-21 15:36             ` Brian Morrison
2008-04-21 14:28     ` Brian Morrison
2008-04-21 15:38   ` Thomas Bächler

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=480CAC55.1000704@fenrir.org.uk \
    --to=bdm@fenrir.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).