Le 11/04/2018 à 18:06, Fabio Estevam a écrit :
On Wed, Apr 11, 2018 at 12:52 PM, Guillaume Gardet guillaume.gardet@free.fr wrote:
So, how to handle dtb filenames? Update with wrong soc definition ? Or drop this patch and define a FDTFILE for each flavor?
You can take a look at how we handle this for wandboard, cuboxi, sabresd, for example.
Taking mx6sabresd as an example you can look at board_late_init() in board/freescale/mx6sabresd/mx6sabresd.c
Then inside include/configs/mx6sabre_common.h check for the findfdt script that picks the correct dtb.
Ok. So, how would you like to proceed? Remove the generic mx6 'soc' definition and use a board sepcific 'board_rev' (or maybe a static definition if one configuration match a single dtb) to define the right dtb?
Could you tell me which DTB should work with the various nitrogen6x boards config?
Here are the one I could get from upstream kernel dts folder and possible config match: * imx6q-nitrogen6x.dts => nitrogen6q2g_defconfig nitrogen6q_defconfig * imx6q-nitrogen6_max.dts => none? * imx6q-nitrogen6_som2.dts => none? * imx6qp-nitrogen6_max.dts => none? * imx6qp-nitrogen6_som2.dts => none? * imx6dl-nitrogen6x.dts => nitrogen6dl2g_defconfig nitrogen6dl_defconfig * imx6sx-nitrogen6sx.dts => nitrogen6s1g_defconfig nitrogen6s_defconfig * imx6q-sabrelite.dts => mx6qsabrelite_defconfig * imx6dl-sabrelite.dts => none?
Guillaume