From: Vladimir Kondratiev <vkondra@mail.ru>
To: netdev@oss.sgi.com
Cc: Pedro Ramalhais <ramalhais@serrado.net>,
"Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Jeff Garzik <jgarzik@pobox.com>,
jt@hpl.hp.com, Jouni Malinen <jkmaline@cc.hut.fi>,
hostap@shmoo.com
Subject: Re: Updated WE-18 (WPA) proposal
Date: Tue, 31 Aug 2004 18:48:48 +0300 [thread overview]
Message-ID: <200408311848.55628.vkondra@mail.ru> (raw)
In-Reply-To: <1093966225.1464.9.camel@rootix>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Tuesday 31 August 2004 18:33, Pedro Ramalhais wrote:
PR> > > Intel Centrino driver is re-using chunks of HostAP, and I'm looking
at PR> > > doing so for the RealTek 8180 driver I am about to publish.
PR> >
PR> > Can someone elaborate on what "chunks" the centrino driver is using
PR> > from hostap?
PR> >
PR> > Jeff what aspects are you looking to re-use from hostap?
PR> >
PR> > I guess we at prism54 should also see what we can re-use too then.
PR> > Our next driver (a softmac driver) will have a lot more code since the
PR> > MAC will need to be implemented on the driver side -- I'm not yet sure
PR> > of the exact details as I haven't grep'd through the available code yet
PR> > I'm wondering though -- are there any other softmac drivers out there,
PR> > or to come soon?
PR> >
PR> > Luis
PR>
PR> The ipw2100 driver and ipw2200 driver both use these parts of hostap
PR> code:
PR> RX code (i think now it's in file hostap_80211_rx.c)
PR> little parts of the TX code (hostap_80211_tx.c)
PR> the hostap_crypt* code for WEP.
PR> Some IEEE802.11 related parts of header files.
PR> The ipw2100 is beggining to use hostap_crypt_tkip and hostap_crypt_ccmp
PR> for WPA and WPA2.
PR>
PR> I think that's it. Better ask James Ketrenos, he is one of the
PR> developers at intel.
Luis,
please correct me if I'm wrong. It seems to me that softmac drivers will need
significant changes relative to the model that HostAP employ. Also, many
changes dictated by QoS (TGe), if one want to really implement it. Will your
product support TGe?
May be, we need to do design for generic "softmac" that will be then used with
different PHY's. Question is, whether we can formally describe boundary
between softmac and PHY.
I am interesting in joining this "softmac" development, as I will do some
other .11 card which is "softmac". Can't reveal details yet, but we may
discuss softmac issues without disclosing private info (I don't want to lose
my job).
Vladimir.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-31 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 4:54 Updated WE-18 (WPA) proposal Jouni Malinen
2004-08-30 16:50 ` Jean Tourrilhes
2004-08-30 17:28 ` Jeff Garzik
2004-08-30 17:42 ` Jean Tourrilhes
2004-08-30 17:55 ` Jeff Garzik
2004-08-30 22:01 ` Luis R. Rodriguez
2004-08-30 22:20 ` Jeff Garzik
2004-08-31 8:54 ` Luis R. Rodriguez
2004-08-31 15:33 ` Pedro Ramalhais
2004-08-31 15:48 ` Vladimir Kondratiev [this message]
2004-08-31 21:04 ` Luis R. Rodriguez
2004-08-31 0:49 ` Pedro Ramalhais
2004-08-31 1:30 ` Jouni Malinen
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=200408311848.55628.vkondra@mail.ru \
--to=vkondra@mail.ru \
--cc=hostap@shmoo.com \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=ramalhais@serrado.net \
/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).