linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Franky Lin" <frankyl@broadcom.com>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "Thomas Langås" <thomas.langas@fxitech.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcm80211 (with bcm4329-chip)
Date: Mon, 21 Nov 2011 10:30:51 -0800	[thread overview]
Message-ID: <4ECA98DB.4030608@broadcom.com> (raw)
In-Reply-To: <4ECA8908.7070304@broadcom.com>

On 11/21/2011 09:23 AM, Arend van Spriel wrote:
> On 11/21/2011 02:56 PM, Thomas Langås wrote:
>> Hi!
>>
>> I'm trying to make our board use this driver instead of an old,
>> proprietary bcm4329-driver, but I can't seem
>> to find much detail on how to tell the driver where my chip is located
>> (on what SDIO-bus).  I suppose there
>> is some specifics I need to include in my machine-file?  Or is
>> everything magic?  Because, currently
>> the platform crashes when enabling the driver. I suspect that this is
>> because we boot from an uSD-card,
>> and that the brcm80211 tries to access the same port for connecting to the chip.
>>
>
> The MMC core should be able to come up with the correct device. It
> sounds strange that the driver would be activated for an SD card.
>
> Could you provide some information on the board you are using. Type of
> processor, kernel version, and anything else you can/want to share. In
> /sys/bus/sdio/devices/ you may find the location of the bcm4329.

Current MMC stack in Linux would not confuse a MMC/SD card and a SDIO 
device. Basically the intialization and command sets they used are 
different.

Just for curiosity, do you know the version of your proprietary driver? 
You should be able to find it in epivers.h.

A crash log would be helpful to locate the issue.

Regards,
Franky



  reply	other threads:[~2011-11-21 18:31 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 [this message]
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
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=4ECA98DB.4030608@broadcom.com \
    --to=frankyl@broadcom.com \
    --cc=arend@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 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).