All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@cwazy.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Norbert van Nobelen <Norbert@edusupport.nl>,
	Raphael Jacquot <raphael.jacquot@imag.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Thu, 06 Jan 2005 16:39:56 -0500	[thread overview]
Message-ID: <41DDB02C.1030205@cwazy.co.uk> (raw)
In-Reply-To: <1105045205.15823.4.camel@krustophenia.net>

Lee Revell wrote:
> On Thu, 2005-01-06 at 20:32 +0100, Norbert van Nobelen wrote:
> 
>>100mWatt antenna (-: Gives 4 mile range (-:
>>Make it USB powered (-: (so that the pcmcia card does not overheat!!)
> 
> 
> Ah, this reminds me, isn't there some kind of issue with open source
> wireless and FCC (or whatever your local equivalent is) regulations?  Or
> was that just an excuse the vendors used for their closed source
> drivers?
> 
> Lee
> 

A little of both, methinks.  Most vendors build their hardware to the most 
powerful that any law (or engineering limits) will allow.  They then use 
country-specific drivers to keep tha hardware operating within legal limits.

Open-source drivers would make it trivial to make the hardware operate beyond its 
legal limits - and could potentially land them in trouble with the FCC/whatever. 
IANAL, but I'm pretty sure that there hasn't been a case of open-source wireless 
drivers tweaked beyond the legal limits landing someone with a fine.

  parent reply	other threads:[~2005-01-06 21:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050105192447.GJ5159@ruslug.rutgers.edu>
2005-01-05 20:05 ` Open hardware wireless cards Luis R. Rodriguez
2005-01-05 20:14   ` Lennart Sorensen
2005-01-05 20:48     ` linux-os
2005-01-05 21:35       ` Lennart Sorensen
2005-01-05 21:09     ` Tomasz Torcz
2005-01-08 20:47       ` Adrian Bunk
2005-01-09  9:59         ` Norbert van Nobelen
2005-01-09 22:28           ` Bernd Petrovitsch
2005-01-09 23:00           ` Alan Cox
2005-01-05 20:17   ` Raphael Jacquot
2005-01-05 20:26     ` Luis R. Rodriguez
2005-01-06  8:02       ` Norbert van Nobelen
2005-01-06 17:24         ` Luis R. Rodriguez
2005-01-06 17:37           ` Lee Revell
2005-01-06 17:38             ` Luis R. Rodriguez
2005-01-06 17:42               ` Lee Revell
2005-01-06 19:06                 ` Norbert van Nobelen
     [not found]                   ` <1105044024.15770.7.camel@krustophenia.net>
2005-01-06 20:51                     ` Norbert van Nobelen
2005-01-06 17:59             ` Alan Cox
2005-01-06 20:25               ` Lee Revell
2005-01-07 10:37               ` Aaron Lehmann
2005-01-06 19:11           ` Raphael Jacquot
2005-01-06 19:32             ` Norbert van Nobelen
2005-01-06 21:00               ` Lee Revell
2005-01-06 21:24                 ` Lennart Sorensen
2005-01-06 21:39                 ` Jim Nelson [this message]
2005-01-06 21:42                   ` Norbert van Nobelen
2005-01-08 11:58                   ` Paul Jakma
2005-01-06 21:43                 ` Christoph Hellwig
2005-01-05 20:22   ` [Prism54-users] " Steve Hill
2005-01-05 20:36     ` Luis R. Rodriguez
2005-01-05 22:19   ` christos gentsis
2005-04-19 19:07   ` Karel Kulhavy

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=41DDB02C.1030205@cwazy.co.uk \
    --to=james4765@cwazy.co.uk \
    --cc=Norbert@edusupport.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raphael.jacquot@imag.fr \
    --cc=rlrevell@joe-job.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.