From: Zhu Yi <yi.zhu@intel.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
Valentin Manea <linux-wireless@mrs.ro>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Intel 4965 HT rates
Date: Thu, 21 Jan 2010 15:18:04 +0800 [thread overview]
Message-ID: <1264058284.5089.13.camel@debian> (raw)
In-Reply-To: <69e28c910912210552p1f63a47dw9fbabf2c26ce02e9@mail.gmail.com>
On Mon, 2009-12-21 at 05:52 -0800, Gábor Stefanik wrote:
> On Mon, Dec 21, 2009 at 3:44 AM, Zhu Yi <yi.zhu@intel.com> wrote:
> > On Mon, 2009-12-21 at 10:33 +0800, Guy, Wey-Yi W wrote:
> >> For 4965, 40MHz only supported in g band
> >
> > We don't support 40MHz channels in 2.4G band. See comments in
> > iwl-eeprom.h:
> >
> > *
> > * NOTE: 4965 does not support HT40 channels on 2.4 GHz.
> > */
> But why does the Windows driver for 4965 support it then?
Can you dump your 4965 eeprom and see if the channels in band 6 (2.4GHz
40MHz channel band) are valid? You can use modparam "debug=1" and grep
'HT40' in dmesg. If the flag is 0x0, the channel is marked as invalid by
EEPROM. The Linux driver simply excludes the HT40 channel in this case.
Thanks,
-yi
> >> -----Original Message-----
> >> From: Valentin Manea [mailto:linux-wireless@mrs.ro]
> >> Sent: Sunday, December 20, 2009 05:38 AM Pacific Standard Time
> >> To: linux-wireless@vger.kernel.org
> >> Subject: Intel 4965 HT rates
> >>
> >> Hi,
> >>
> >> I'm running compat-wireless-2.6.33-rc1 and iw list shows some confusing HT
> >> capabilities:
> >> Band 1:
> >> HT capabilities: 0x082c
> >> * 20 MHz operation
> >> * SM PS disabled
> >> * 20 MHz short GI
> >> * max A-MSDU len 7935
> >>
> >> but for 802.11a channels:
> >> Band 2:
> >> HT capabilities: 0x086e
> >> * 20/40 MHz operation
> >> * SM PS disabled
> >> * 20 MHz short GI
> >> * 40 MHz short GI
> >> * max A-MSDU len 7935
> >>
> >> While I can't tell when this happened, I remember older 2.6.29 releases
> >> supported HT40 for both bands.
> >> The wireless card is an Intel 4965 on a Thinkpad T61.
> >>
> >>
> >> Regards,
> >> Valentin
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >> N�����r��y���b�X��ǧv�^�){.n�+����{��*ޕ�,�{ay� ʇڙ�,j ��f���h���z� �w��� ���j:+v���w�j�m���� ����zZ+�����ݢj"��!�i
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
>
>
next prev parent reply other threads:[~2010-01-21 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 2:33 Intel 4965 HT rates Guy, Wey-Yi W
2009-12-21 2:44 ` Zhu Yi
2009-12-21 13:52 ` Gábor Stefanik
2009-12-28 3:45 ` Zhu Yi
2009-12-28 20:33 ` Gábor Stefanik
2009-12-29 0:46 ` Zhu Yi
2010-01-21 7:18 ` Zhu Yi [this message]
2010-01-21 21:09 ` Gábor Stefanik
2010-01-22 1:37 ` Zhu Yi
-- strict thread matches above, loose matches on Subject: below --
2009-12-20 13:10 Valentin Manea
2009-12-20 21:42 ` Luis R. Rodriguez
2009-12-20 21:48 ` Luis R. Rodriguez
2009-12-20 21:51 ` Luis R. Rodriguez
2009-12-20 21:52 ` Gábor Stefanik
2009-12-20 22:36 ` Valentin Manea
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=1264058284.5089.13.camel@debian \
--to=yi.zhu@intel.com \
--cc=linux-wireless@mrs.ro \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=wey-yi.w.guy@intel.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).