All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Franky Lin" <frankyl@broadcom.com>
To: "Thomas Langås" <thomas.langas@fxitech.com>
Cc: "Arend Van Spriel" <arend@broadcom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Howard Harte" <hharte@broadcom.com>
Subject: Re: brcm80211 (with bcm4329-chip)
Date: Mon, 21 Nov 2011 14:48:10 -0800	[thread overview]
Message-ID: <4ECAD52A.6050509@broadcom.com> (raw)
In-Reply-To: <CADrAYBmhBWVDC=K+F-NU6WkUv-M=WddWvU1pe9AXABEinUBGvQ@mail.gmail.com>

On 11/21/2011 02:26 PM, Thomas Langås wrote:
> On Mon, Nov 21, 2011 at 10:58 PM, Franky Lin<frankyl@broadcom.com>  wrote:
>> It's possible that the firmware carshed. Are you using the firmware/nvram
>> from Linux repository? You should use the nvram that fits your platform.
>
> I'm using the one from repository now, yes.
>
> Using the firmware I had from before, the only difference I see is the
> time of when
> the IRQ handler is called, but that is probably just randomness, I guess?

I think both firmware is fine. I was referring to the 
brcm/bcm4329-fullmac-4.txt It's a nvram file contains critical 
information used by firmware. And it's hardware dependent. We have 
submitted a patch to remove the one in Linux firmware repository to 
avoid confusion as it's for a Broadcom internal development board. It 
may not work with your set up. I think there should be a similar file 
comes with the proprietary driver package if you are using a module 
instead of a 4329 chip. Please use that one.

>
> Attached is the log when modprobing with old firmware.
>

The issue you facing is more likely SDIO bus connection issue.
brcmf_sdioh_request_word: Failed to write word, Err: 0xffffffac
mmc1: Got data interrupt 0x00200000 even though no data operation was in 
progress.
These may be both caused by data CRC error/time out.
I don't have Exynos 4210 spec. But I guess for a such new chip the SDIO 
host should be able to run the bus at 50MHz. You could try to hack the 
MMC/SDIO host driver and reduce the max frequency to 25MHz or even 
further to 12MHz to see if any improvement.

Regards,
Franky


  reply	other threads:[~2011-11-21 22:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADrAYBnwWEaigcgQYYk6V3VEuEYyrmzJQXegKVk6TgOTPh5N8A@mail.gmail.com>
2011-11-21 17:23 ` brcm80211 (with bcm4329-chip) Arend van Spriel
2011-11-21 18:30   ` Franky Lin
2011-11-21 18:45     ` Thomas Langås
2011-11-21 19:58       ` Franky Lin
2011-11-21 21:13         ` Thomas Langås
2011-11-21 21:34           ` Thomas Langås
2011-11-21 21:58             ` Franky Lin
2011-11-21 22:26               ` Thomas Langås
2011-11-21 22:48                 ` Franky Lin [this message]
2011-11-21 23:40                   ` Thomas Langås
2011-11-21 23:42                     ` Howard Harte
2011-11-21 23:50                       ` Thomas Langås
2011-11-21 23:56                         ` Franky Lin
2011-11-22  0:00                           ` Thomas Langås
2011-11-22  0:13                             ` Franky Lin
2011-11-22  0:22                               ` Thomas Langås
2011-11-21 18:47   ` Thomas Langås

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=4ECAD52A.6050509@broadcom.com \
    --to=frankyl@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=hharte@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=thomas.langas@fxitech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.