should all SD-bootable boards have CONFIG_MCI_WRITE enabled?

Robert P. J. Day rpjday at
Wed Feb 8 08:43:27 EST 2012

  with boards like the beagle and panda that can boot off of SD cards,
shouldn't all boards like that have CONFIG_MCI_WRITE enabled so that
one could write the environment back with "saveenv"?

  currently, omap3530_beagle_defconfig *doesn't* have that set, which
produces (on my xM):

barebox at Texas Instrument's Beagle:/ saveenv
saving environment
could not open /dev/env0: Read-only file system

  now, that *could* be because i have no /dev/env0 file given how my
environment was configured (i have only /dev/defaultenv), but even if
i did have a /dev/env0, wouldn't i still need MCI_WRITE to save my

  the obvious proposed patch is to add CONFIG_MCI_WRITE=y to both the
beagle and panda defconfig files.  does that sound right?  any other
boards for which that would be appropriate?



Robert P. J. Day                                 Ottawa, Ontario, CANADA


More information about the barebox mailing list