From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: why would beagle and panda boards not have CONFIG_MCI_STARTUP set?
Date: Tue, 7 Feb 2012 23:06:48 +0100 [thread overview]
Message-ID: <20120207220648.GF3852@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1202071525420.28853@oneiric>
On Tue, Feb 07, 2012 at 03:33:32PM -0500, Robert P. J. Day wrote:
>
> slowly working my way thru how to create an appropriate environment
> for my beagle xM and when i boot with the default beagle-configured
> MLO and barebox.bin, there are no disk devices defined as described
> here:
>
> http://wiki.barebox.org/doku.php?id=user:mmc-sd
>
> that's obviously a problem since the xM and pandaboards have no
> NAND and must boot off of SD card.
>
> now, as i understand it, the MLO loader needs access to the MMC/SD
> card just to read barebox.bin, so i'm not at all surprised to see, in
> omap3530_beagle_xload_defconfig, the settings:
>
> CONFIG_MCI=y
> CONFIG_MCI_STARTUP=y
> # CONFIG_MCI_WRITE is not set
> CONFIG_MCI_OMAP_HSMMC=y
>
> but in omap3530_beagle_defconfig, you have only:
>
> CONFIG_MCI=y
> CONFIG_MCI_OMAP_HSMMC=y
>
> if i read it correctly, you can add the line:
>
> mci0.probe=1
>
> to your environment. but with boards like beagles and pandas, why
> would you *not* configure with:
>
> CONFIG_MCI_STARTUP=y
>
> it would seem to make no sense to not have that. wouldn't that config
> setting be a no-brainer on any board that boots *only* off of SD?
>
Yes, this option should be set in the defconfig for such a case. Not
probing SD cards is only useful when the normal usecase is to boot from
nand where probing of SD cards would delay the boot time.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-02-07 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 20:33 Robert P. J. Day
2012-02-07 22:06 ` Sascha Hauer [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=20120207220648.GF3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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