Dear Tom,
In message <20130805160747.GP5164@bill-the-cat> you wrote:
>
> > U-Boot is perfectly able to import such settings from text files (or
> > text blobs stored somewhere, even attached to the U-Boot image, if you
> > want), so just use the text files separately, instead of hard
> > compiling them into the code.
>
> But we have to start _somewhere_ with a compiled-in set of defaults.
Agreed, nbut that should be a very minimal set of setting that is
common to most use cases.
> Yes, some boards are easily updatable (it's just an SD card), but on
> others it's not. And there's a strong desire on the generic distro side
> (and on a lot of kernel hackers sides) to treat U-Boot as never-touch
> binaries. What ships is what's used. So a default that tries to load
I perfectly understand this argument, and this is exactly why I think
that a hard-coded, compiled in set of complex settings (as needed for
a standard distro, from what I've seen so far), would be a seriously
wrong approach. You _will_ need to make changes to such settings over
time, so plan for it, and provide an easy "never-touch U-Boot itself"
way for it.
> a controlable file is what started all of the boot.scr or uEnv.txt
> stuff.
Yes, I am aware of this.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
Anything that is worth doing at all is worth doing well.
-- Philip Earl of Chesterfield
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
