netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dax Kelson <dax@gurulabs.com>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: NetDev <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Fri, 24 Feb 2006 16:34:50 -0700	[thread overview]
Message-ID: <1140824090.3475.56.camel@mentorng.gurulabs.com> (raw)
In-Reply-To: <43FF88E6.6020603@linux.intel.com>

On Fri, 2006-02-24 at 16:29 -0600, James Ketrenos wrote:
> Intel is pleased to announce the launch of an open source project to
> support the Intel PRO/Wireless 3945ABG Network Connection mini-PCI
> express adapter (IPW3945).

Cool!

>   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
> 64-bit application.  The daemon utilizes a sysfs interface exposed by
> the driver in order to communicate with the hardware and configure the
> required regulatory parameters.

It was exciting to watch the "centrino" wireless cards go from the least
supported cards in the Linux to the near the best G and A cards from a
feature and licensing stand point (modulo the firmware restart issues).

I have a ipw2200 and have recommended it and now the ipw2915 to anyone
who has asked (myself and ipw2xxx using co-workers have taught thousands
of students and decision makers in Linux classes worldwide).

It is very disappointing to see this binary user space daemon (that must
run as root, presumably to write into /sys/) requirement. I recognize
that it is a better poison than a binary kernel module.

At the point when I'm in the market for a mini-PCI express wireless
adapter I hope there are other cards available that don't require any
kernel or userland binary pieces. I'll vote with my wallet so to speak.

Dax Kelson
Guru Labs

  reply	other threads:[~2006-02-24 23:34 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 [this message]
2006-02-24 23:48 ` Jeff V. Merkey
2006-02-25 13:26   ` Michael Buesch
2006-02-25  8:41 ` Christoph Hellwig
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=1140824090.3475.56.camel@mentorng.gurulabs.com \
    --to=dax@gurulabs.com \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).