netdev
[Top] [All Lists]

Re: ipw2100 wireless driver

To: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>
Subject: Re: ipw2100 wireless driver
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 11 Aug 2004 11:44:37 +0100
Cc: Pavel Machek <pavel@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Jeff Chua <jeffchua@xxxxxxxxxxxxxxxxxxx>, Tomas Szepe <szepe@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, kernel list <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <4119F203.1070009@xxxxxxxxxxxxxxx>; from jketreno@xxxxxxxxxxxxxxx on Wed, Aug 11, 2004 at 05:16:35AM -0500
Mail-followup-to: Christoph Hellwig <hch@xxxxxxxxxxxxx>, James Ketrenos <jketreno@xxxxxxxxxxxxxxx>, Pavel Machek <pavel@xxxxxxx>, Jeff Chua <jeffchua@xxxxxxxxxxxxxxxxxxx>, Tomas Szepe <szepe@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, kernel list <linux-kernel@xxxxxxxxxxxxxxx>
References: <20040714114135.GA25175@xxxxxxxxxx> <Pine.LNX.4.60.0407141947270.27995@xxxxxxxxxxxxxxxxxxxxx> <20040714115523.GC2269@xxxxxxxxxx> <20040809201556.GB9677@xxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0408101258130.1290@xxxxxxxxxxxxxxxxxxxxx> <20040810075558.A14154@xxxxxxxxxxxxx> <20040810101640.GF9034@xxxxxxxxxxxxxxxxxxxxxxxx> <4119F203.1070009@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Wed, Aug 11, 2004 at 05:16:35AM -0500, James Ketrenos wrote:
> We're currently working to clean up ipw2100 and ieee80211 code for submission 
> to 
> netdev for discussion and hopefully inclusion in the future.  The ieee80211 
> code 
> is still being heavily developed, but its usable.  If anyone wants to help 
> out, 
> or if folks feel its ready as-is to get pulled into wireless-2.6, let me know.

Maybe we should switch to your ieee802.11 for a generic wireless stack then
instead of the original hostap code.  At least it seems more actively
maintained right now and supports two drivers already.

Btw, I've looked at the ipw2100 and have to concerns regarding the firmware,

 a) yo'ure not using the proper firmware loader but some horrible
    handcrafted code using sys_open/sys_read & co that's not namespace
    safe at all
 b) the firmware has an extremly complicated and hard to comply with license,
    I'm not sure we want a driver that can't work without a so strangely
    licensed blob in the kernel. Can you talk to intel lawyers and put it on
    simple redristribution and binary modification for allowed for all purposes
    license please?
    

 
> Thanks,
> James
> 
> 
> 
---end quoted text---

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