From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: should all SD-bootable boards have CONFIG_MCI_WRITE enabled?
Date: Wed, 8 Feb 2012 08:43:27 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202080838460.4323@oneiric> (raw)
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@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
environment?
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?
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-08 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1202080838460.4323@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