|To:||Jeff Garzik <jgarzik@xxxxxxxxx>|
|Subject:||Re: [PATCH 2.6] Intersil Prism54 wireless driver|
|From:||James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>|
|Date:||Wed, 10 Mar 2004 17:37:16 -0600|
|Cc:||jt@xxxxxxxxxx, Christoph Hellwig <hch@xxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx, Linux kernel mailing list <linux-kernel@xxxxxxxxxxxxxxx>|
|References:||<20040304023524.GA19453@bougret.hpl.hp.com> <20040310165548.A24693@infradead.org> <20040310172114.GA8867@bougret.hpl.hp.com> <404F5097.firstname.lastname@example.org> <20040310175200.GA9531@bougret.hpl.hp.com> <404F5744.email@example.com>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4|
Jeff Garzik wrote:
> Yes, it would be good to end the cycle of re-implementing 802.11 over > and over again ;-)
< snip >
> * start working on generic 802.11 stack in wireless-2.6 queue
As we're currently walking the path of implementing the same thing for the IPW2100 driver, being able to re-use this code would be _very nice_.
I'd like to get WEP into IPW2100 as soon as possible, and would like to do so in a way that would make transitioning to a common 802.11 layer seamless (or at least reasonably isolated). Any suggestions on how to best do this, or where we might be able to help, would be much appreciated.
I'm very interested in these discussions, so if they move to or are being discussed on another list (besides netdev), please let me know where.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH AND RFC_PATCH] 1. Leak corking option in ipv4 2. ipv6 opt panic, David S. Miller|
|Next by Date:||Re: linux-wireless mailing list, Jean Tourrilhes|
|Previous by Thread:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Jeff Garzik|
|Next by Thread:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Jouni Malinen|
|Indexes:||[Date] [Thread] [Top] [All Lists]|