public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Report on bcma with 14e4:4353 (BCM43224)
Date: Sat, 30 Jul 2011 10:19:05 -0500	[thread overview]
Message-ID: <4E3420E9.6080603@lwfinger.net> (raw)

Rafa?,

I'm using a recent pull from wireless-testing - 'git describe' results in 
master-2011-07-26-150-g4ea94a9.

The driver is working well with reasonable performance. Using tcpperf, I get 
8-10 Mb/s upload on an 802.11g connection. The connection has been up for 17 
hours with no disconnects.

A minor annoyance is that the driver does not autoload on boot and had to be 
manually modprobed. AFAIK, I don't have any blacklisting or other configuration 
parameters that would cause this. Furthermore, I don't see anything in the 
driver code that would cause this. Does autoload work on your system?

A more serious problem is that the driver does not work on my 802.11n AP that is 
set for "up to 270 Mbps at 2.4 GHz". It will authenticate and associate, but the 
throughput is minimal. It also gets the "PHY transmission error" messages. None 
occur with 802.11g. I would guess some kind of error in the HT40 settings.

Thanks for your hard work on this device.

Larry

             reply	other threads:[~2011-07-30 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 15:19 Larry Finger [this message]
2011-08-17 18:27 ` Report on bcma with 14e4:4353 (BCM43224) Rafał Miłecki
2011-08-17 21:43   ` [PATCH] Add uevent to bcma bus, to autoload drivers David Woodhouse
2011-08-18  6:46     ` Rafał Miłecki
2011-08-18  7:51       ` David Woodhouse
2011-08-19 20:13         ` Rafał Miłecki
2011-08-19 20:52           ` David Woodhouse
2011-08-19 21:17             ` Rafał Miłecki

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=4E3420E9.6080603@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@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