From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: jt@hpl.hp.com, Jouni Malinen <jkmaline@cc.hut.fi>,
netdev@oss.sgi.com, hostap@shmoo.com,
Pedro Ramalhais <ramalhais@serrado.net>
Subject: Re: Updated WE-18 (WPA) proposal
Date: Mon, 30 Aug 2004 18:20:01 -0400 [thread overview]
Message-ID: <4133A811.1010009@pobox.com> (raw)
In-Reply-To: <20040830220105.GY22126@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> On Mon, Aug 30, 2004 at 01:55:52PM -0400, Jeff Garzik wrote:
>
>>Jean Tourrilhes wrote:
>
>
> <-- snip -->
>
>>> Also, I'm not clear how the stuff in wireless-2.6 is supposed
>>>to trickle into the other trees (netdev-2.6, -mm and Linus's), and how
>>>to better link it with the CVS of the various drivers involved.
>>
>>Less of a trickle than a flood: wireless-2.6 should be the target for
>>development of shared wireless stack code. As several drivers are
>>currently using bits of HostAP, for example, wireless-2.6 should be a
>>focal point for patches that modify these drivers to instead share the
>>same code.
>>
>>Once this generic work is done, it would get pushed all at once to
>>netdev-2.6, where it would receive testing in -mm. Then, later, pushed
>>to mainline.
>>
>> Jeff
>
>
> Beides wpa_supplicant from hostap code (which is actually going into
> WE18) what other code re-use is on the roadmap as of yet for wireless-2.6?
Intel Centrino driver is re-using chunks of HostAP, and I'm looking at
doing so for the RealTek 8180 driver I am about to publish.
> Also who is coordinating this?
The same person who coordinates the kernel at large... no one ;-)
Jeff
next prev parent reply other threads:[~2004-08-30 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 4:54 Updated WE-18 (WPA) proposal Jouni Malinen
2004-08-30 16:50 ` Jean Tourrilhes
2004-08-30 17:28 ` Jeff Garzik
2004-08-30 17:42 ` Jean Tourrilhes
2004-08-30 17:55 ` Jeff Garzik
2004-08-30 22:01 ` Luis R. Rodriguez
2004-08-30 22:20 ` Jeff Garzik [this message]
2004-08-31 8:54 ` Luis R. Rodriguez
2004-08-31 15:33 ` Pedro Ramalhais
2004-08-31 15:48 ` Vladimir Kondratiev
2004-08-31 21:04 ` Luis R. Rodriguez
2004-08-31 0:49 ` Pedro Ramalhais
2004-08-31 1:30 ` Jouni Malinen
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=4133A811.1010009@pobox.com \
--to=jgarzik@pobox.com \
--cc=hostap@shmoo.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=ramalhais@serrado.net \
/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).