All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.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:48:10 -0700	[thread overview]
Message-ID: <43FF9B3A.5010307@wolfmountaingroup.com> (raw)
In-Reply-To: <43FF88E6.6020603@linux.intel.com>


Awesome. Now all we need is someone to write the bcm series for wireless 
and ndiswrapper
can go away.

Jeff

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).
>
>The project is hosted at http://ipw3945.sourceforge.net.  A development
>mailing list is available (linked from the top of the IPW3945 project
>page.)  You can find the current development release for the adapter by
>following the links on the project home page.
>
>A stable [end user targetted] version is not yet available. Those
>interested in using the development version should review
>the notice linked to from the project page.  A stable version should
>be available in the next few weeks.
>
>Aside from a form factor change (our prior wireless cards were mini PCI
>while this one is mini PCI express), this project has also changed the
>division of work between what occurs on the adapter and what the host is
>responsible for performing.  The microcode and hardware provide lower
>level MAC services (timings, backoffs, transmit queue management, etc.)
>The host is responsible for middle and upper layer MAC services.
>
>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
>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.
>
>Those familiar with our prior projects may be pleased with the changes
>we have made with the license agreement for binary portions of this new
>project.  We were able to provide a more easily understood agreement
>for the binary components required for the adapter to function.  While
>this new license still restricts against reverse engineering and
>modification, it has been changed to allow easier redistribution.  You
>can find the terms of the agreement accessible from the microcode
>and daemon download page linked to from the project site.
>
>The current development snapshot contains backward compatibility code
>to allow the driver to work in older kernels.  We will be removing 
>that code prior to submitting the driver for inclusion in the kernel.
>
>Thanks,
>James
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


  parent reply	other threads:[~2006-02-24 22:52 UTC|newest]

Thread overview: 26+ 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 [this message]
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 19:09       ` Gene Heskett
2006-02-25 19:41         ` Michael Buesch
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
2006-02-27 14:27 ` Dick Streefland

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=43FF9B3A.5010307@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.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 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.