From: Michael Wu <flamingice@sourmilk.net>
To: netdev@oss.sgi.com
Cc: Jouni Malinen <jkmaline@cc.hut.fi>,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
James Ketrenos <jketreno@linux.intel.com>,
"Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: 2.6.x wireless update and status
Date: Wed, 23 Mar 2005 19:20:07 -0500 [thread overview]
Message-ID: <200503231920.13459.flamingice@sourmilk.net> (raw)
In-Reply-To: <20050323055243.GU8648@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Wednesday 23 March 2005 12:52 am, Jouni Malinen wrote:
> > Moving forward, the next "todo" for kernel wireless hackers is to get
> > ieee80211 common code lib into shape, namely:
> > * Merge Intel ipw drivers, which use ieee80211
> > * Update HostAP to use ieee80211
> > * Merge/convert other drivers to use ieee80211?
>
> I'll be working on HostAP driver next; and ieee80211 code of course at
> the same time, since it is likely to need some changes for this. As far
> as other drivers are concerned, I'd like to see Atheros cards working
> with the generic ieee80211 code. They would be a good test target since
> they are an example of design where very large part of functionality is
> in the driver/network stack (no firmware used). This would be a good
> test to verify that the 802.11 code is generic enough for such a design.
>
The ADM8211 would be a good test too. So far, the main thing I see missing
from the 802.11 code is software scanning/authentication/association. Is all
of that being moved to userspace? I prefer having a little bit of that in the
kernel so minimal managed, adhoc, and WEP features can be used without a
daemon.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-24 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 1:46 2.6.x wireless update and status Jeff Garzik
2005-03-23 5:52 ` Jouni Malinen
2005-03-24 0:20 ` Michael Wu [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=200503231920.13459.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--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