Hi Fabio,
On Sun, Sep 4, 2016 at 7:57 AM, Fabio Estevam festevam@gmail.com wrote:
Hi Jagan,
On Sat, Sep 3, 2016 at 5:22 AM, Jagan Teki jagannadh.teki@gmail.com wrote:
Since most of the board along with the config code used for mx6ul boards are common and for improving code reusability refactor or group code as mx6ul notation. Hence for new board its simply add new defconfig with existing board or related configs.
include/configs/mx6ul_14x14_evk.h -> include/configs/mx6ul.h board/freescale/mx6ul_14x14_evk -> board/freescale/mx6ul board/freescale/mx6ul/mx6ul_14x14_evk.c -> board/freescale/mx6ul/board.c
I think this will be hard to maintain. I still prefer each board to be added on its own board file/dts.
Initially I started of doing this, but I find most of the redundant code board as well in configs, its better follow this kind of notation because most of the remaining soc board files are so mature like this sunxi, zynq.
thanks!