From: Johannes Berg <johannes@sipsolutions.net>
To: Joerg Pommnitz <pommnitz@yahoo.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: AW: API to regulatory control (1)
Date: Wed, 26 Sep 2007 09:32:08 +0200 [thread overview]
Message-ID: <1190791928.18521.346.camel@johannes.berg> (raw)
In-Reply-To: <696484.11170.qm@web51403.mail.re2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Wed, 2007-09-26 at 00:25 -0700, Joerg Pommnitz wrote:
> No reason to get testy. I thought this was about a design and I wanted to point
> out that the assumption, that the regulatory settings are global to all interfaces
> in one machine might not apply in all cases.
Sorry. It is about design, but it seems we've got far too much on our
hands with it already, and I'm not sure I want to spend a lot of effort
on this special case that likely interests nobody but you.
That said, maybe it'll be clear to you what type of restrictions are
actually needed per-device once we've got the API figured out. I'm not
convinced that you really need different API, if you're using stock
hardware you can't increase TX power by much anyway so you have to use
amplifiers and special antennas, no? And I guess that in the "debug"
regulatory that Luis added there are basically no restrictions and
you're on your own.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-09-26 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 7:25 AW: API to regulatory control (1) Joerg Pommnitz
2007-09-26 7:32 ` Johannes Berg [this message]
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=1190791928.18521.346.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pommnitz@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox