Dear Tom,
In message <[email protected]> you
wrote:
>
> If you flash u-boot-dtb-tegra.bin, you'll get a fully functioning
> U-Boot. There's an intermediate file (u-boot-dtb.bin) that I assume
> is u-boot.bin+dtb - I'm not sure why it's left around - Allen could
> comment here.
I _dislike_ the idea of having image names which include architecture
or even board parts. I would really like to have generic names, that
can be used in a consistent way across platforms, architectures and
boards.
> So in my eyes, all you really need is u-boot-dtb-tegra.bin - an
> unwieldy name, to be sure, but it seems to satisfy your request for a
> Soc identifier in the name. I voted for just having u-boot.bin be the
Please reconsider. I definitely do NOT want to have SoC names or that
in any such images!
IIRC, the original idea was to provide image names (common for all
architectures, SoCs, boards) that only depend on where you install
U-Boot to. in this way, we would have:
- u-boot.bin for the generic case (say, for installation into NOR
flash, no SPL or similar needed).
- u-boot-nand.bin
for installation in NAND (with all needed headers,
padding etc. included)
- u-boot-onenand.bin
for installation in OneNAND
- u-boot.sd for installation on a SDCard
[actually we have an inconsistency in names here; this
should have been "u-boot-sd.bin" or maybe even better
"u-boot-sdcard.bin"]
etc.
It is very important to me that we do NOT include any architectures,
SoCs, or board specifc parts in the names because this will cause
major PITA for all kind of automatic test suites etc.
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: [email protected]
"He was so narrow minded he could see through a keyhole with both
eyes ..."
_______________________________________________
U-Boot mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/u-boot
