From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com
Subject: Re: brcmsmac: Data bus error in reading tsf_random
Date: Mon, 3 Dec 2012 21:40:21 +0100 [thread overview]
Message-ID: <50BD0E35.8030807@broadcom.com> (raw)
In-Reply-To: <50BAB095.2070103@hauke-m.de>
On 12/02/2012 02:36 AM, Hauke Mehrtens wrote:
> Hi Arend,
>
> I am getting a Data bus error when brcmsmac tries to read tsf_random in
> brcms_c_wme_setparams. This does not happen when I add a printk
> somewhere near that read of tsf_random or when I replace the read with a
> constant. In b43 this code works, without this error for me, see
> b43_qos_params_upload(). With the BCM4716 I do not have this problem. It
> could be that this is caused by the broken PCIe controller in the BCM4716.
I can look for known workarounds but I am afraid you know way more about
the BCM4716 than I do.
> I am using brcmsmac from compat-wireless 2012-09-07, but I have also
> tried the most recent brcmsmac code from wireless-testing. brcmsmac uses
> the normal firmware from linux-firmware and I have also tried the new
> firmware posted some days ago with the same result.
>
> I am using a BCM43224 connected to the PCIe controller of the BCM4716.
>
> Are there any special requirements for reading tsf_random under mips?
Not that I recall.
> To make my BCM43224 work I use this patch [0], the "printk("dummy\n");"
> is a hack to workaround the problem I am describing here.
That kind of hacks always make me suspicious about the compiler. I guess
you checked that both brcmsmac and b43 read the same register offset to
get tsf_random, right?
Regards,
Arend
prev parent reply other threads:[~2012-12-03 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 1:36 brcmsmac: Data bus error in reading tsf_random Hauke Mehrtens
2012-12-03 4:47 ` Nathan Hintz
2012-12-03 16:19 ` Larry Finger
2012-12-03 20:40 ` Arend van Spriel [this message]
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=50BD0E35.8030807@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.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).