netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: NetDev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org, okir@suse.de
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 08:41:39 +0000	[thread overview]
Message-ID: <20060225084139.GB22109@infradead.org> (raw)
In-Reply-To: <43FF88E6.6020603@linux.intel.com>

On Fri, Feb 24, 2006 at 04:29:58PM -0600, James Ketrenos wrote:
> As a result of this change, some of the capabilities currently required
> to be provided on the host include enforcement of regulatory limits for
> the radio transmitter (radio calibration, transmit power, valid
> channels, 802.11h, etc.) In order to meet the requirements of all
> geographies into which our adapters ship (over 100 countries) we have
> placed the regulatory enforcement logic into a user space daemon that
> we provide as a binary under the same license agreement as the
> microcode.  We provide that binary pre-compiled as both a 32-bit and

the regualatory problems are not true.  they are completely focused on
the users.  Someone who wants to change it can always do it, may it be
by binary patching.  I don't know of a single country that forbids
implementing those bits in source code shipped, and in those countries
we alredy couldn't distribute the kernel.

A binary daemon is completely unacceptable and unless you fix that there
is zero chance the driver could get into mainline.  I'd also like to
urge the distributors to not put this crap in to weaken our free drivers
future.  Intel, please stop this madness and play by the rules.

  parent reply	other threads:[~2006-02-25  8:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 22:29 [Announce] Intel PRO/Wireless 3945ABG Network Connection James Ketrenos
2006-02-24 23:34 ` Dax Kelson
2006-02-24 23:48 ` Jeff V. Merkey
2006-02-25 13:26   ` Michael Buesch
2006-02-25  8:41 ` Christoph Hellwig [this message]
2006-02-25 10:49   ` Gene Heskett
2006-02-25 10:53     ` Christoph Hellwig
2006-02-25 11:19       ` Gene Heskett
2006-02-25 13:19         ` Michael Buesch
2006-02-26  1:09         ` Stephen Evanchik
2006-02-25 12:29       ` Stefan Rompf
2006-02-25 14:19     ` Jan Engelhardt
2006-02-25 22:07       ` Matthieu CASTET
2006-02-25 22:19         ` John Stoffel
2006-02-25 22:28           ` matthieu castet
2006-02-25 22:47             ` Larry Finger
2006-02-26 20:20           ` Alejandro Bonilla
2006-02-26  0:58   ` Alan Cox
2006-02-27 17:10     ` Christoph Hellwig
2006-02-27 17:34       ` Stephen Hemminger
2006-03-03 20:04       ` Kasper Sandberg
2006-03-03 20:31         ` Jeff Garzik
2006-02-26 17:54 ` Pavel Machek

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=20060225084139.GB22109@infradead.org \
    --to=hch@infradead.org \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=okir@suse.de \
    /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).