linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Newton <nevion@gmail.com>
To: Rami Rosen <roszenrami@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 802.11n status (iwlagn)
Date: Tue, 13 Jan 2009 04:01:22 -0800	[thread overview]
Message-ID: <496C8292.8060001@gmail.com> (raw)
In-Reply-To: <b25312890901130241l635ffe78na10d2aa468365e7e@mail.gmail.com>

> In http://www.linuxwireless.org/en/users/Drivers, there
> is a table of drivers; some of them do support 802.11n,
> as you can see form the PHY modes column
> (there might be more such drivers, take into account that this table
> might not be always up to date).
> 
>  Intel iwl4965 is among them;  I did not perform any tests with
> 4965-based iwlagn devices with 80211.n though.

So if n (or n-draft) support really is in the 4965 driver already - how
do I access it?  It doesn't seem to be happening automatically -
filetransfers/iptraf let me know that much.  Very confused about what's
going on here and if I need any iwconfig magic or something like
replacing pfifo with multiq for device qdisc.  I haven't a clue.

> - I believe that you are aware that the 80211.n spec is expected
> only at the end of 2009 (December 2009) or later.

Ah, true, but I guess I was also wondering about n draft support since
these devices are available now and have been for quite a while.  I can
get 100 mbit/s or so with my 4965 card in windows with intel's drivers
and my asus wl500w router.  But only a lousy 54 or so in linux.  That
just ain't right.

  reply	other threads:[~2009-01-13 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  7:13 802.11n status (iwlagn) Jason Newton
2009-01-13 10:41 ` Rami Rosen
2009-01-13 12:01   ` Jason Newton [this message]
2009-01-13 16:39 ` reinette chatre
2009-01-19 12:37   ` David Shwatrz
2009-01-19 13:46     ` Tomas Winkler

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=496C8292.8060001@gmail.com \
    --to=nevion@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=roszenrami@gmail.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).