On Sat, Mar 7, 2009 at 8:14 AM, Eddie Dawydiuk <ed...@embeddedarm.com> wrote: > Hello, > >> But the question remains: Why do you need simpleboot support for >> Yosemite when you can use a uImage or cuImage with u-boot? > > We are developing a new board based upon the Yosemite board. Seeing as > though the Yosemite board was supported in the mainline kernel I decided > to start with that code base. After looking at what different > options/images were available for device trees vs open firmware I decided > the simpleImage would be the ideal format for our new board. I then read > how to build a simpleImage for the Yosemite board, which build without any > compiler errors. Although I found the image didn't work, so I figured it > might be helpful for others if the image just worked without > modifications. Although shortly I will be submitting support for our > custom board using this same approach. So if you have any suggestions on > this approach using the simpleImage please let me know.
Before I answer this, what bootloader are you using? > On another note, can you tell me/point me to some documentation on how to > get a unique machine ID for a new board? What do you mean? Are you referring to the top level compatible and model properties? g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
