From: James Ketrenos <jketreno@linux.intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeff Chua <jeffchua@silk.corp.fedex.com>,
Tomas Szepe <szepe@pinerecords.com>,
netdev@oss.sgi.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw2100 wireless driver
Date: Wed, 11 Aug 2004 05:16:35 -0500 [thread overview]
Message-ID: <4119F203.1070009@linux.intel.com> (raw)
In-Reply-To: <20040810101640.GF9034@atrey.karlin.mff.cuni.cz>
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
next prev parent reply other threads:[~2004-08-11 10:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 11:41 ipw2100 wireless driver Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55 ` Pavel Machek
2004-08-09 20:15 ` Tomas Szepe
2004-08-10 5:02 ` Jeff Chua
2004-08-10 6:55 ` Christoph Hellwig
2004-08-10 10:16 ` Pavel Machek
2004-08-10 10:34 ` Christoph Hellwig
2004-08-11 12:17 ` Pavel Machek
2004-08-11 17:54 ` Jeff Garzik
2004-08-11 20:27 ` Pavel Machek
2004-08-11 22:01 ` Jeff Garzik
2004-08-11 10:16 ` James Ketrenos [this message]
2004-08-11 10:44 ` Christoph Hellwig
2004-08-11 10:53 ` Wichert Akkerman
2004-08-11 10:59 ` Christoph Hellwig
2004-08-11 16:21 ` James Ketrenos
2004-08-11 16:30 ` Stephen Hemminger
2004-08-11 16:33 ` Tomas Szepe
2004-08-11 16:51 ` Christoph Hellwig
2004-08-11 17:02 ` Tomas Szepe
2004-08-11 17:11 ` Christoph Hellwig
2004-08-11 17:22 ` Tomas Szepe
2004-08-11 18:55 ` John Stoffel
2004-08-11 23:55 ` Jeff Chua
2004-08-12 3:47 ` Luis R. Rodriguez
2004-08-11 17:51 ` Jeff Garzik
2004-07-14 12:30 ` Tomas Szepe
2004-07-14 12:27 ` Pavel Machek
2004-07-14 13:15 ` Vojtech Pavlik
2004-07-14 13:42 ` Pavel Machek
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=4119F203.1070009@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=hch@infradead.org \
--cc=jeffchua@silk.corp.fedex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pavel@suse.cz \
--cc=szepe@pinerecords.com \
/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).