All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] ieee80211 subsystem
Date: Wed, 09 Feb 2005 20:36:49 -0800	[thread overview]
Message-ID: <420AE4E1.7070204@osdl.org> (raw)
In-Reply-To: <42087751.3040806@linux.intel.com>

James Ketrenos wrote:
> Randy.Dunlap wrote:
> 
>> James Ketrenos wrote:
>>
>>> Attached is the patch against 2.6.11-rc3-mm1 that adds the ieee80211 
>>> subsystem used by the ipw2100 and ipw2200 projects.
>>>
>>> I'll be sending out the patches for ipw2100-1.0.0 and ipw2200-1.0.0 
>>> that use thist stack to the list on Monday.
>>>
>>> In terms of what the stack currently does:
>>>
>>> * HW independent -- it only knows about 802.11 data and structures
>>> * Performs an 802.3 <-> 802.11 transform for data Tx/Rx
>>> * Host based support for fragmentation, WEP, and WPA using the 
>>> kernel's crypto functions
>>> * Beacon and probe response collection and parsing
>>> * Default implementation of some of the WE handlers that can be 
>>> managed without hardware knowledge
>>>
>>> We are working to merge in Dave Miller's p80211 code into the 
>>> ieee80211 subsystem so that it hooks into the kernel as a true 
>>> network layer as opposed to a mutated offspring of ethernet.
>>> Once that is done, hopefully the skb to txb code can be reworked and 
>>> 802.11 fragments can be treated either as normal skbs, or skbs can be 
>>> modified to directly support them (ideally so that encrypted 802.11 
>>> frames in support of IP packets can be cached by the stack instead of 
>>> having to be re-encrypted on TCP retries)
>>>
>>> Support for HW/FW crypto and fragmentation offload, in a HW 
>>> independent fashion, is also on the short-term list.
>>>
>>> When you look through the patch you'll likely notice the #ifdef 
>>> NOTYET/#endif sequences surrounding portions of code from the hostap 
>>> project.  Portions of this subsystem were based on an earlier version 
>>> of the hostap project.  Those areas that weren't directly supported 
>>> by the ipw* projects weren't ported to be completely hardware 
>>> independent (since I don't have the hardware to test it), and so are 
>>> still wrapped in the ifdefs.  These sections mainly cover support for 
>>> MASTER and WDS modes.
>>>
>>> Anyway, please let me know what you think.  Hopefully I built the 
>>> patch right...
>>
>>
>>
>> James,
>> Can you post a patch that will build?  or did you just want
>> feedback on the current state of the patch?
> 
> 
> Ah; I see my tree that I did the diff on was missing the 
> wireless/Makefile and the ieee80211/ieee80211_module.c to create the 
> patch against... sigh.  Attached is ieee80211_module.c; you have the 
> change for the Makefile to include ieee80211.
> Later {hopefully today} I'll send a full patch that includes several of 
> the corrections you called out in your prior patch.

Now missing ieee80211_crypt.h (#included in the new
ieee80211.h).  Apparently still needing a complete diff.


+	/* Add the ESSID */
+        iwe.cmd = SIOCGIWESSID;
+        iwe.u.data.flags = 1;
+	if (network->flags & NETWORK_EMPTY_ESSID) {

Lines 2-3 above use spaces (e.g.) -- please use tabs.


-- 
~Randy

  reply	other threads:[~2005-02-10  4:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 18:47 [PATCH] ieee80211 subsystem James Ketrenos
2005-02-04 22:48 ` Jeff Garzik
2005-02-05  6:07 ` Randy.Dunlap
2005-02-08  3:57   ` Jouni Malinen
2005-02-08  9:41     ` James Ketrenos
2005-02-05  8:13 ` Christoph Hellwig
2005-02-08  2:49 ` Randy.Dunlap
2005-02-08  8:24   ` James Ketrenos
2005-02-10  4:36     ` Randy.Dunlap [this message]
2005-02-08  4:29 ` Jouni Malinen
2005-02-08  9:26   ` James Ketrenos
2005-02-08 23:25     ` Jeff Garzik
2005-02-08 23:33       ` James Ketrenos
2005-02-11  0:49       ` James Ketrenos
2005-02-11 21:44         ` Jeff Garzik
2005-02-08  4:45 ` Randy.Dunlap
2005-02-08 19:13   ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2005-02-08 21:45 Jean Tourrilhes

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=420AE4E1.7070204@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=jketreno@linux.intel.com \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.