From: James Ketrenos <jketreno@linux.intel.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Netdev <netdev@oss.sgi.com>
Subject: [Announce] Update on ipw2100, ipw2200, and support for Intel PRO/Wireless 2915ABG
Date: Tue, 31 Aug 2004 16:08:58 -0500 [thread overview]
Message-ID: <4134E8EA.9080605@linux.intel.com> (raw)
It's been a while since I've updated lkml and netdev on the progress of
the ipw projects. Given the recent announcement by Intel for the
introduction of Intel PRO/Wireless 2915 ABG Network Connection miniPCI
adapter, I thought now was a good time...
First, thanks to everyone that has been contributing, using, testing,
and reporting feedback for the projects described below. The support
by folks in the community has been terrific -- the drivers wouldn't be
anywhere near as feature rich and stable as they are today if not for
the contributions of everyone.
The ipw2100 project (802.11b) has progressed very well. We are in the
process of cleaning up the driver for submittal to netdev for eventual
inclusion into the kernel. The driver currently supports wep, 802.1x,
monitor mode, adhoc, infrastructure, etc. Suspend/resume isn't quite
functioning yet, but we'll get there soon. This project is hosted at
http://ipw2100.sf.net.
The ipw2200 project (802.11bg), which was launched back in May, is
quickly catching up to the ipw2100 project in terms of functionality.
It currently supports wep and 802.1x in infrastructure mode. Currently
it will only associate at B data rates; hooking in the G capabilities
is going on right now. We'll then tackle adhoc and remaining feature
gaps. We had been planning on holding off submittal for kernel
inclusion until we were feature complete. However, several folks have
requested that we accelerate that plan and get it in sooner rather than
later. To that end we're working to try and get it ready for submittal
along with the ipw2100 project. This project is hosted at
http://ipw2200.sf.net.
The ipw2100 and ipw2200 projects currently share the 802.11 frame
handling stack for Tx/Rx and some management frame processing. That
code has been pulled into its own module suite (ieee80211), based on
work from the Host AP project. That code needs to be resync'd with the
Host AP code (and vice versa where appropriate) so that then all of
those drivers will be able to leverage a single wireless network stack.
Anyway, this brings me to announcing Linux support for the Intel
PRO/Wireless 2915 ABG Network Connection adapter. As of next week, the
ipw2200 project will also begin supporting the ABG adapter. From the
driver's perspective, the only change between the two cards is the
addition fo the A radio on the 2915. So, adding support for the ABG is
just a matter of updating the firmware used by the ipw2200 project,
adding PCI id's, and putting in support for A. That work will progress
as we continue to bring full support for the ipw2200 project.
At some point in the near future we will rename the ipw2200 project to
something more appropriate to identify it as supporting both the 2200
and 2915 adapters.
Thanks,
James
next reply other threads:[~2004-08-31 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 21:08 James Ketrenos [this message]
2004-09-01 7:02 ` [Announce] Update on ipw2100, ipw2200, and support for Intel PRO/Wireless 2915ABG Arjan van de Ven
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=4134E8EA.9080605@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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).