On 17/04/18 17:49, Tony Lindgren wrote:
* Tero Kristo <t-kristo@xxxxxx> [180417 09:36]:
In typical setup, you can boot a large number of different configs via:
bootm 0x82000000#dra71-evm#nand#lcd-auo-g101evn01.0
... assuming the configs were named like that, and assuming they would be
compatible with each other. The am57xx-evm example provided is better, as
you can chain the different cameras to the available evm configs.
Why not just do it in the bootloader to put together the dtb?
Then for external devices, you could just pass info on the
kernel cmdline with lcd=foo camera=bar if they cannot be
detected over I2C.
(Added Linux ARM list to CC, this was not part of the original delivery.)
Ok trying to resurrect this thread a bit. Is there any kind of consensus
how things like this should be handled? Should we add the DT overlay
files to kernel tree or not?
Should we add any kind of build infra to kernel tree, and at what level
would this be? Just DT overlay file building support, and drop the FIT
build support as was proposed in this RFC series or...?
U-boot can obviously parse the base DTB + overlay DTB:s into a single
DTB, but this is somewhat clumsy approach and is relatively error prone
to get it right.
Building the FIT image post kernel build would also be possible, but who
would be doing this, is there any need to get this done in generic
manner or shall we just add SoC vendor specific tools for this?
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
