From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Andreas Bräu" <ab@andi95.de>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Bastian Bittorf" <bittorf@bluebottle.com>,
openwrt-devel@lists.openwrt.org, linux-wireless@vger.kernel.org,
feint@lists.subsignal.org
Subject: Re: WRT54g / b43 / mac802.11 BREAKTHROUGH
Date: Thu, 19 Jul 2012 09:59:43 -0500 [thread overview]
Message-ID: <500820DF.1030008@lwfinger.net> (raw)
In-Reply-To: <982FBF04-5969-436D-9D3A-A6388C077667@andi95.de>
On 07/19/2012 02:18 AM, Andreas Bräu wrote:
>>>
>>> 1) why does a band change (can be seen through minstrel) is a problem?
>>
>> Because IIRC b43 doesn't support anything other than 2.4GHz at all.
>
> It's not a change between 2.4 and 5 GHz.
> Wifi stops working if the bitrate changes between 11b (1, 2, 5.5, 11) and 11g (6, 9, 12, 18, 24, 36, 48, 54) rates
>
> So if we tell the system to only use 11g rates, wifi doesn't stop.
Andi,
Rates for 11g include 1, 2, 5.5, and 11, as well as 6, 9, ... What you really
want to say is that it fails when it switches between CCCK and OFDM rates.
What chip is in your WRT54G?
Larry
next prev parent reply other threads:[~2012-07-19 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 11:56 WRT54g / b43 / mac802.11 BREAKTHROUGH Bastian Bittorf
2012-07-19 1:40 ` Gábor Stefanik
2012-07-19 7:18 ` Andreas Bräu
2012-07-19 10:03 ` [maschinenraum] " npl
2012-07-19 14:59 ` Larry Finger [this message]
2012-07-20 9:50 ` Bastian Bittorf
2012-07-20 9:06 ` Bastian Bittorf
2012-08-22 16:21 ` Hauke Mehrtens
2012-08-22 17:00 ` G.W. Haywood
2012-08-22 17:49 ` Rafał Miłecki
2012-08-22 18:17 ` Hauke Mehrtens
2012-08-22 18:45 ` Larry Finger
2012-08-22 21:05 ` Hauke Mehrtens
2012-08-22 21:19 ` Larry Finger
2012-08-25 14:50 ` Hauke Mehrtens
2012-08-24 17:18 ` Bastian Bittorf
2012-08-24 17:13 ` Bastian Bittorf
2013-02-14 20:35 ` Bastian Bittorf
2013-02-15 19:47 ` Larry Finger
2013-02-18 1:49 ` Larry Finger
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=500820DF.1030008@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ab@andi95.de \
--cc=bittorf@bluebottle.com \
--cc=feint@lists.subsignal.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=openwrt-devel@lists.openwrt.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).