From: Michael Wu <flamingice@sourmilk.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Mohamed Abbas <mabbas@linux.intel.com>, netdev@vger.kernel.org
Subject: Re: 3945 driver using d80211
Date: Wed, 9 Aug 2006 09:47:15 -0700 [thread overview]
Message-ID: <200608090947.20291.flamingice@sourmilk.net> (raw)
In-Reply-To: <44D99558.1000507@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
On Wednesday 09 August 2006 00:57, Johannes Berg wrote:
> Please not, for now. We need someone pushing for fullmac features in
> d80211, we need those anyway for embedded systems that can't afford
> running all of it on the main CPU. While obviously Intel would benefit
> from doing this since a lot more d80211 features would come available,
> the greater good would be having a main-stream card that someone cares
> about and helps making d80211 full-mac capable.
>
It's not that hard to generate probe, authentication, and association frames,
and it isn't done frequently enough to stress any embedded system that can
run linux. Doing this would let 3945 take advantage of all the d80211
features, so why not?
What level of fullmac support are we talking about? True fullmac cards (as I
define them) do not need to use d80211. WE19 is all they need, to add
WPA/WPA2 support. The IPW cards have a particularly unique split between
firmware and host 802.11 duties which I haven't seen in any other cards. They
aren't quite fullmac enough to interface with WE directly, yet they only need
probe response handling to complete the picture. What other half-fullmac,
half-softmac card besides the other IPW cards splits card/host 802.11 duties
along those lines? What other splits between card and host are out there? I
would be very reluctant to make changes to the 802.11 stack to support
"fullmac" without evidence that other drivers need the change.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-09 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 21:27 3945 driver using d80211 Mohamed Abbas
2006-08-08 21:40 ` Michael Wu
2006-08-09 7:57 ` Johannes Berg
2006-08-09 14:50 ` John W. Linville
2006-08-09 16:47 ` Michael Wu [this message]
2006-08-09 17:26 ` Christoph Hellwig
2006-08-09 19:22 ` Dan Williams
2006-08-09 21:07 ` Mohamed Abbas
2006-08-09 21:32 ` Simon Barber
2006-08-09 21:41 ` Simon Barber
2006-08-09 22:42 ` Michael Wu
2006-08-09 0:06 ` Jouni Malinen
2006-08-09 15:49 ` 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=200608090947.20291.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=mabbas@linux.intel.com \
--cc=netdev@vger.kernel.org \
/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).