From: Bill Davidsen <davidsen@tmr.com>
To: James Ketrenos <jketreno@linux.co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 2100 802.11b driver
Date: Thu, 11 Mar 2004 17:27:42 -0500 [thread overview]
Message-ID: <4050E7DE.2020007@tmr.com> (raw)
In-Reply-To: <404E27E6.40200@linux.co.intel.com>
James Ketrenos wrote:
> I am pleased to announce the launch of an open source development
> project for
> the Intel PRO/Wireless 2100 miniPCI network adapter. The project has been
> created and is hosted at http://ipw2100.sf.net.
>
> The driver, as it currently stands, is able to associate and communicate in
> Infrastructure mode. Support for both 2.4 and 2.6 is available. We are
> releasing this driver now as "early beta" code to get feedback and help
> in the development, so expect bugs (and please report them)! Of course
> Intel will continue the effort (as part of this Open Source project).
> We are planning to add support of all key wireless features (adhoc, WEP,
> etc)
> over the next few months, quicker with help from others in the community.
>
> NOTE: Let me reiterate -- this driver is in active development. Features
> and
> capabilities available on other operating systems have not all been
> implemented
> at this time. This includes wireless features (adhoc, wep) as well as
> performance and power savings.
>
> I look forward to working with the community to improve and enhance the
> driver.
> So if you have an Intel wireless 802.11b miniPCI network adapter in your
> laptop... download the bits, give it a whirl, and let me know how it goes.
> Please also let us know if you encounter any problems that may be
> related to
> specific distributions.
Great job! Dare we hope that in the future the news 802.11[bg] unit I
have seen mentioned would also be supported in a similar manner?
-bill
prev parent reply other threads:[~2004-03-11 22:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 20:24 [Announce] Intel PRO/Wireless 2100 802.11b driver James Ketrenos
2004-03-09 20:57 ` Arjan van de Ven
2004-03-09 22:01 ` James Ketrenos
2004-03-09 23:48 ` Marcel Holtmann
2004-03-09 21:05 ` Timothy Miller
2004-03-09 21:12 ` Dax Kelson
2004-03-10 2:46 ` James Ketrenos
2004-03-10 8:15 ` vda
2004-03-10 8:38 ` Jeff Garzik
2004-03-10 17:31 ` Timothy Miller
2004-03-10 17:26 ` Jeff Garzik
2004-03-12 0:32 ` Lincoln Dale
2004-03-11 1:07 ` Joel Jaeggli
2004-03-10 12:35 ` bert hubert
2004-03-10 18:06 ` Disconnect
2004-03-11 22:45 ` Bill Davidsen
2004-03-10 7:52 ` Jan De Luyck
2004-03-11 6:23 ` Jan De Luyck
2004-03-11 7:48 ` James Ketrenos
2004-03-11 8:05 ` Jan De Luyck
2004-03-11 18:37 ` Stephen Hemminger
2004-03-11 22:14 ` James Ketrenos
2004-03-11 22:27 ` Bill Davidsen [this message]
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=4050E7DE.2020007@tmr.com \
--to=davidsen@tmr.com \
--cc=jketreno@linux.co.intel.com \
--cc=linux-kernel@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