On Sat, 08 Mar 2008 02:03:02 +0100 Wolfgang Denk wd@denx.de wrote:
In message 20080307142832.7d317b31.kim.phillips@freescale.com you wrote:
but these are the filenames in linux' device tree directory - arch/powerpc/boot/dts, and I'm assuming people do something sane like dtc -I $file.dts -O $file.dtb.
Argh... what a mess.
indeed.
are you suggesting we rename u-boot's config files too?
Well, my personal preference is to have the official board name and the related file names match as closely as possible, probabl;y just using lowercase letters for the files.
I don't think it's exactly intuitive to have a board named "mpc832xemds" and the related files use "mpc832x_mds".
That looks awfully broken to me.
afaik, you can supposedly buy an mds board with an mpc8321, mpc8321e, mpc8323, or an mpc8323e (the trailing 'e' denotes whether the crypto engine has its fuse intact). It's just the mpc8323e that is (probably by far) the most common.
At the momnt, the U-Boot code looks OK, so if you do it differently in Linux, you should fix it there.
Just my $ 0.02 (well, I think I should say $ 0.03 given current exchange rates ;-).
bah, what can you buy with a cent these days? ;)
linux board support files are consistent /within/ linux, and u-boot board support files are intra-u-boot consistent; it's just this particular file (the device tree) needs to be inter-linux and u-boot consistent (for interoperability purposes). Since linux does currently host the device tree files, we should probably follow their naming scheme, unless you want to discuss hosting device tree files in u-boot ;).
fyi, the board file was changed in the linux git tree commit be156bed9ebfe365c6d95f715eae3529cf694fcb
Kim