From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: using SD card on Broadcom 4709 eval board
Date: Sun, 23 Nov 2014 12:09:15 +0100 [thread overview]
Message-ID: <1416740955.1991.37.camel@x220> (raw)
In-Reply-To: <CACYKDtgi73FzgX2RCS0MPJYS7YsndBWbpKKrRjO0TwGY1FvFsA@mail.gmail.com>
On Sat, 2014-11-22 at 17:05 -0800, Abu Rasheda wrote:
> > depends on B43 && SSB_SDIOHOST_POSSIBLE && EXPERIMENTAL,
>
> EXPERIMENTAL was removed in v3.9. So this concerns a pre-v3.9
> tree?
>
> Yes, it is 2.6 kernel.
Which v2.6 release? There were 40, the first was released in December
2003, the last in May 2011. Quite a few things changed in that period.
> I know this is extremely old.I just want to have SD card working, any
> suggestions ?
The "depends on" line you quoted was added in v2.6.32, which is still
supported, so the tree you're using might not be seen as "extremely old"
by everyone.
> > off the above B43 is only shows up in arch/ppc,
>
> You mean you can only set B43 if configuring for ARCH=ppc?
>
> I did a grep and only found B43 under arch/ppc, so I guess when
> ARCH=ppc is selected.
What did you actually grep for, and in what tree?
> > which does not make sense, as this CPU is arm based.
> >
> > Any guidance will be appreciated.
>
> So what I am missing ?
Useful answers?
See, you original question was:
> I have been trying to use SD card on Broadcom's 4709 eval board. Linux
> kernel tree provided with SDK seems to have few SDIO drivers, but non
> of them seems to be working or more accurately, loading them does not
> list device in /proc/devices, so I can create block file to mount it.
>
> After googling and searching through Linux kernel tree, it seems like
> B43_SDIO is correct option to turn on, since the controller seems to
> be on the Broadcom CPU (4709) process itself (am I correct ?).
It seems B43_SDIO supports wireless cards, of the Broadcom 43xx family,
that have a SDIO interface. I'm _guessing_ that these are (fairly
obscure) WLAN cards which can be plugged into a SD slot. Probably not
what you're looking for.
Which, actually, might be SD card support. Currently apparently
available through MMC, one of the options found in
drivers/mmc/host/Kconfig (perhaps MMC_SDHCI_BCM_KONA or
MMC_SDHCI_BCM2835?) and MMC_BLOCK.
Anyhow, grepping the mainline tree for 4709 did reveal "config
ARCH_BCM_5301X", which supports the BCM4709 SoC. But that Kconfig symbol
was only added in v3.15, see commit 5b293ebe7572 ("ARM: BCM5301X:
initial support for the BCM5301X/BCM470X SoCs with ARM CPU"). And that
still doesn't tell you what driver to use here.
The above is a verbose way to admit that I don't really know how to
determine what you need to get SD cards working. MAINTAINERS mentions
the bcm-kernel-feedback-list at broadcom.com list. Perhaps that can be of
help.
Paul Bolle
next prev parent reply other threads:[~2014-11-23 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 22:46 using SD card on Broadcom 4709 eval board Abu Rasheda
2014-11-22 23:07 ` Paul Bolle
2014-11-23 1:05 ` Abu Rasheda
2014-11-23 11:09 ` Paul Bolle [this message]
2014-11-23 20:05 ` Abu Rasheda
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=1416740955.1991.37.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.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).