From: Hauke Mehrtens <hauke@hauke-m.de>
To: b43-dev@lists.infradead.org
Subject: Interesting 14e4:4321
Date: Fri, 06 May 2011 23:36:33 +0200 [thread overview]
Message-ID: <4DC469E1.2040101@hauke-m.de> (raw)
In-Reply-To: <BANLkTim0usjWr8DqJQk+GQiBHmfgTjey7g@mail.gmail.com>
On 05/06/2011 10:40 PM, Rafa? Mi?ecki wrote:
> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
> rare and interesting so I wanted to post all info about it :)
>
> I'm attaching lspci and dmesg.
>
> I find it interesting because it seems to be SSB SOC with standard
> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
> 14e4:4321 card connected, which is SSB-based one with (the most
> interesting) 80211.
>
> Unfortunately this is one another BCM4321 with DMA not working. I
> really need to focus on this after fixing LP-PHY and adding BCMA.
>
Hi Rafa?,
RealOpty reported the same DMA error in the OpenWrt channel and it is
nice that you are working on this. He was using a Netgear WNR834B V2.
Here is his dmesg output: http://paste.ubuntu.com/599979/
We already fixed some of the problems with these devices but have not
investigated into the DMA errors.
The cardbus attribute in the nvram seams to be set wrong for some
devices we added a workaround for it for the Netgear WNR834B V2. [0] It
would be nice to get the nvram content ( nvram show ) to also detect
this device and activate the workaround for it.
The SPROM is not stored on the pci card but in the nvram on the flash
chip of the device. This is now correctly read out in OpenWrt and we
will send some patches to mainline soon. [1] [2]
Hauke
[0]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/980-wnr834b_no_cardbus_invariant.patch
[1]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/031-ssb-add-callback-for-sprom.patch
[2]:
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/patches-2.6.37/033-bcm47xx-register-fallback-callback.patch
next prev parent reply other threads:[~2011-05-06 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 20:40 Interesting 14e4:4321 Rafał Miłecki
2011-05-06 21:28 ` Larry Finger
2011-05-06 21:48 ` Rafał Miłecki
2011-05-06 22:25 ` Larry Finger
2011-05-06 21:36 ` Hauke Mehrtens [this message]
2011-05-06 21:51 ` Rafał Miłecki
[not found] ` <479014597.20110507002540@googlemail.com>
[not found] ` <BANLkTi=n6gjDxGX0buUamNQAydPCMqEpjg@mail.gmail.com>
[not found] ` <274308290.20110507111432@googlemail.com>
2011-05-07 9:41 ` Rafał Miłecki
2011-05-06 21:56 ` Jonas Gorski
2011-05-06 22:14 ` Rafał Miłecki
2011-05-06 22:32 ` Jonas Gorski
2011-05-07 15:17 ` Michael Büsch
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=4DC469E1.2040101@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=b43-dev@lists.infradead.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