netdev
[Top] [All Lists]

Re: [PATCH 2.6] Intersil Prism54 wireless driver

To: Pavel Machek <pavel@xxxxxx>
Subject: Re: [PATCH 2.6] Intersil Prism54 wireless driver
From: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>
Date: Mon, 15 Mar 2004 14:55:38 -0800
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>, Jouni Malinen <jkmaline@xxxxxxxxx>, James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx, Linux kernel mailing list <linux-kernel@xxxxxxxxxxxxxxx>
E-mail: jt@xxxxxxxxxx
In-reply-to: <20040315221826.GA305@xxxxxxxxxx>
Organisation: HP Labs Palo Alto
References: <20040304023524.GA19453@xxxxxxxxxxxxxxxxxx> <20040310165548.A24693@xxxxxxxxxxxxx> <20040310172114.GA8867@xxxxxxxxxxxxxxxxxx> <404F5097.4040406@xxxxxxxxx> <20040310175200.GA9531@xxxxxxxxxxxxxxxxxx> <404F5744.1040201@xxxxxxxxx> <404FA6AC.7040009@xxxxxxxxxxxxxxxxxx> <20040311023141.GB3738@xxxxxxxxx> <404FD23C.4020205@xxxxxxxxx> <20040315221826.GA305@xxxxxxxxxx>
Reply-to: jt@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Mon, Mar 15, 2004 at 11:18:26PM +0100, Pavel Machek wrote:
> On St 10-03-04 21:43:08, Jeff Garzik wrote:
> > Jouni Malinen wrote:
> > >done, I would hope to get the code merged into the kernel tree either
> > >with full Host AP driver or separately. One option would be to first add
> > >Host AP driver in its current structure (i.e., everything in
> > >drivers/net/wireless) and then create a new directory (net/ieee80211 ?)
> > >for generic IEEE 802.11 functionality and start moving things like the
> > >IEEE 802.11 encryption into the new location.
> > 
> > Given the discussion today, I think my preference is to merge all of 
> > HostAP into the wireless-2.6 tree I just created, then submit patches to 
> > that which create and populate net/802_11.  Once the work on that is 
> > mostly done, it can get merged back into the main upstream tree.
> 
> Can we have net/wifi? 802_11 looks ugly. 802.11 would be better, but
> wifi seems best.
>                                                               Pavel

        IEEE 802.11 is a technical standard. WiFi is a marketing
certification. There are 802.11 products which are not WiFi certified
(actually, there is one such driver already in the kernel).
        By the way, I don't really care about the final name, I'm hust
being pedantic ;-)
        Have fun...

        Jean


<Prev in Thread] Current Thread [Next in Thread>