From: Michael Wu <flamingice@sourmilk.net>
To: netdev@oss.sgi.com
Subject: Re: Where Linux 802.11x support needs work
Date: Thu, 27 Jan 2005 11:24:13 -0500 [thread overview]
Message-ID: <200501271124.19740.flamingice@sourmilk.net> (raw)
In-Reply-To: <41F74757.3090104@tihlde.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Wednesday 26 January 2005 2:31 am, Roar Bjørgum Rotvik wrote:
> Michael Wu wrote:
> > On Tuesday 25 January 2005 11:03 pm, Dan Williams wrote:
> >>> One of the big item not mentionned by you is the in-kernel
> >>>802.11 stack (native frames and management). If done right, I guess it
> >>>would mostly be transparent to you...
> >>
> >>You know, I was thinking of it and I just forgot to put it on the list.
> >>If you're including madwifi and ipw2x00, we have a grand total of what, 3
> >>or 4 802.11 stacks in the kernel at the same time? (madwifi,
> >>orinoco/hermes, ipw2x00, linux-wlan-ng)
> >
> > Only orinoco/hermes is in the kernel, and that doesn't really have much
> > of an 802.11 stack, since most things are done in hardware. Madwifi has a
> > fairly complete 802.11 stack (ported from netbsd), and so does adm8211.
> > Dunno about ipw2x00.
>
> Do any of these 80.11 stacks (or the upstream linux network stack) have
> a solution for WLAN cards with 802.11e (QoS extension) with more than
> one HW/firmware transmit queues?
>
I'm not aware of any. The latest revision of the adm8211 chip supports more
than one tx queue, but only one is used.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-27 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 2:40 Where Linux 802.11x support needs work Jean Tourrilhes
2005-01-26 4:03 ` Dan Williams
2005-01-26 4:41 ` Michael Wu
2005-01-26 7:31 ` Roar Bjørgum Rotvik
2005-01-27 16:24 ` Michael Wu [this message]
2005-01-27 18:09 ` Michael Renzmann
2005-01-26 7:17 ` Michael Renzmann
2005-01-26 18:03 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 21:47 Dan Williams
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=200501271124.19740.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--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 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).