> Am Sonntag 13 November 2011, 01:32:03 schrieb Marek Vasut: > > > - every supported board in u-boot has to be supported in mainline > > > linux, > > > > > > too. because that is the basic requirement for an entry to stay in > > > this file. > > > > No, you can define CONFIG_MACH_TYPE MACH_TYPE_SOMETHING and > > MACH_TYPE_SOMETHING nnn in your config file. > > well, according to this argumentation, there would be no need for > mach-types.h at all. because if you rely on a mach-types.h definition and > it is removed from linux, you have to switch to define it yourself anyway.
Not really, if you don't use it to boot linux, you don't need the mach id. Or if you use dtree. > > > > IMHO u-boot should have its own mach-types.h (maybe autogenerated, like > > > the linux kernel do), just with entries for boards which are supported > > > by u-boot. This way, there won't be any problems with new board support > > > patches. > > > > That would be insane due to colisions in the number assignment. See above > > how to handle such trouble. > > of course with the same ids... (same source as the kernel mach-types, which > is http://www.arm.linux.org.uk/developer/machines/download.php) _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
