Dear Ronen Shitrit,
In message 309002C0DA137042828828FC53D7A9347E13538016@IL-MB01.marvell.com you wrote:
Dear Ronen Shitrit,
In message 309002C0DA137042828828FC53D7A9347E13537FE0@IL-MB01.marvell.com= you wrote:
I'm not sure we are on the same page here, the Kirkwood has an internal bootROM which can only boot an image if this image is wrapped by a specific header.
There are tons of standards for image formats, and even more commonly used formats I would not dare to call standard; but this processor has to invent yet another one?
Could you please use standard quoting rules? See http://www.netmeister.org/news/learn2quote.html
Aplso, please restrict your line lengh to some 70 characters or so.
Thanks.
[Ronen Shitrit] I still think we are not on the same page here. This isn't another image format...
But yes, it is.
Why do we need the bootrom? For example the KW doesn't have HW NAND ECC support :( But we still want to support boot from NAND and ve protected from upto 4 bi t ECC. So the CPU wakes up and start running code from the bootROM (embedded ROM i n the Kirkwood) this code read the NAND and verify its ECC, then according to the binary image header in the NAND it initialize the DRAM for this spec
You see? "binary image header" Here you say yourself that this is a binary image header, i. e. a prorpietary image format.
Fix the hardware design? [Ronen Shitrit] probably won't happen...
Though so.
Best regards,
Wolfgang Denk