Am Sonntag 13 November 2011, 17:18:27 schrieb Marek Vasut:
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.
so why should i use the mach-type.h anyway? instead i could just define the id in the config.
either there is a database, where the ids come from (and this database must not follow the linux policies) or there is no database and every board defines the numerical id (of couse they must match the linux mach ids.)
what about boards which switch from mach-ids to DT in linux? Just don't support mach-ids for these anymore and not being able to boot older kernels?