Hi,
Does u-boot always follow the mach-types.h from upstream linux? Is there any policy?
If thats true, it means, that - 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. - a device with device tree bindings, won't have any mach-type entry at all, which means, that a distribution is not able to backport a device support from DT form to an old-fashioned setup code (eg. support for a board on older linux kernels, which doesn't have ARM device tree support).
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.
Opinions?