why would beagle and panda boards not have CONFIG_MCI_STARTUP set?

why would beagle and panda boards not have CONFIG_MCI_STARTUP set?

[Robert P. J. Day]

  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

Re: why would beagle and panda boards not have CONFIG_MCI_STARTUP set?

[Sascha Hauer]

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