lkml.org 
[lkml]   [2004]   [Aug]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ipw2100 wireless driver
Pavel Machek wrote:
> Hi!
>
>>>>ipw2100 0.51 from ipw2100.sf.net builds using gcc-2.95.3 "out of the box."
>>>
>>>Well, this is really good news!
>>>
>>>I just downloaded 0.51 compiled with gcc-2.95.3 and got it working on my
>>>IBM X31 with WEP. Even better, 0.51 doesn't need hostap-driver.
>>
>>Btw, any vounteer for merging the hostap-based generic ieee80211_* files
>>from the ipw2100 driver with the hostap driver in the wireless-2.6 tree?
>
> I know very little about wireless-2.6 tree (where to get it without
> bitkeeper?), but...
>
> task is to take ipw2100 driver, drop ieee80211_* files from it, and
> make it work with ieee80211* files from wireless-2.6?

The ieee80211_* files in the ipw2100 were partially based on the hostap source,
with any HW specific code pulled out. It handles Tx and Rx right now for BSS,
IBSS, and MONITOR mode, supporting wep, etc. It doesn't have all the hooks
needed for the host based AP mode that Host AP currently has, nor does it
support wpa yet.

We're also using the stack for the ipw2200 project (which we hope to get another
snapshot release out soon) We've been talking about pulling ieee80211 into its
own project as others have expressed an interest in using it in their drivers as
well.

The general goal for the ieee80211 stack has been to be able to take an skb from
the xmit handler, fragment and encrypt that skb, and provide that list of those
802.11 fragments to the driver for transmission. On the Rx side, the ieee80211
stack expects a standard 802.11 data frame which it then performs any decrypt /
defrag and then passes up to the kernel.

Additional frame code is slowly being added to ieee80211 to support handling of
probe response / beacons to manage scan results, etc. and provide default WE
handlers for exposing that information.

ieee80211_wx provides some generic implementation for the WE handlers that every
driver has to implement the same way.

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.

Thanks,
James


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.124 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site