netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ulrich Kunitz <kune@deine-taler.de>, netdev@vger.kernel.org
Subject: Re: proposal for new wireless configuration API
Date: Fri, 18 Aug 2006 11:00:17 -0400	[thread overview]
Message-ID: <20060818150006.GA5359@tuxdriver.com> (raw)
In-Reply-To: <1155885125.3425.11.camel@ux156>

On Fri, Aug 18, 2006 at 09:12:05AM +0200, Johannes Berg wrote:
> On Fri, 2006-08-18 at 01:29 +0200, Ulrich Kunitz wrote:
> > Or are here people, who
> > really want to freely transmit on all frequencies their RF might
> > be able to generate?
> 
> Yes :P
> Some amateur radio people asked me about extending the spectrum a bit to
> the top (apparently they're allowed to use the band just above the ISM
> band as well).
> 
> However, I don't think we need to cater them in the API. I think they
> ought to be able to live with kernel patches since we don't really know
> how far up the frequency on say the bcm43xx can go anyway before the
> card breaks/malfunctions.

I concur.  It would be best to confine the "normal" API to things
that are legitimately done without a license if at all possible.
Those who are licensed for other spectrum uses should be more than
capable of applying a patch to do so (thereby more clearly taking
regulatory responsibility upon themselves).

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-08-18 15:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 15:28 proposal for new wireless configuration API Johannes Berg
2006-08-15 16:14 ` Luis R. Rodriguez
2006-08-16  7:26   ` Johannes Berg
2006-08-15 16:29 ` Dan Williams
2006-08-15 16:38   ` Michael Buesch
2006-08-15 18:14     ` Dan Williams
2006-08-15 19:13       ` Michael Buesch
2006-08-15 19:27         ` Simon Barber
2006-08-15 19:35           ` Michael Buesch
2006-08-15 20:06             ` Dan Williams
2006-08-15 19:59         ` Dan Williams
2006-08-16  7:14           ` Johannes Berg
2006-08-17 19:39         ` Jean Tourrilhes
2006-08-17 21:24           ` Michael Buesch
2006-08-17 23:29     ` Ulrich Kunitz
2006-08-18  7:12       ` Johannes Berg
2006-08-18 15:00         ` John W. Linville [this message]
2006-08-18 21:29         ` Ulrich Kunitz
2006-08-18 22:02           ` Michael Buesch
2006-08-21  7:31             ` Johannes Berg
2006-08-16  6:51   ` Johannes Berg
2006-08-16 18:02     ` Simon Barber
2006-08-17  7:19       ` Johannes Berg
2006-08-17 16:42         ` Simon Barber
2006-08-17 23:23           ` Ulrich Kunitz
2006-08-18  7:01           ` Johannes Berg
2006-08-18 16:45             ` Simon Barber
2006-08-21  6:45               ` 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=20060818150006.GA5359@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --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).