mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: why would beagle and panda boards not have CONFIG_MCI_STARTUP set?
Date: Tue, 7 Feb 2012 15:33:32 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1202071525420.28853@oneiric> (raw)


  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?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-02-07 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 20:33 Robert P. J. Day [this message]
2012-02-07 22:06 ` Sascha Hauer

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=alpine.DEB.2.02.1202071525420.28853@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.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