From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Walle Date: Sun, 13 Nov 2011 00:58:42 +0100 Subject: [U-Boot] arm mach-types.h Message-ID: <201111130058.43026.michael@walle.cc> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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? -- Michael