On 02/25/2016 01:06 AM, Lokesh Vutla wrote:
[..snip..]
[...]
"setenv fdtfile dra72-evm.dtb; fi;" \ "if test $board_name = beagle_x15; then " \ "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \
"if test $board_name = am57xx_evm; then " \"setenv fdtfile am57xx-beagle-x15.dtb; fi;" \Is it the same dtb file for am57xx_evm as well? or is this intentional and will be updated later?
Yes - it should be the same dtb file for 2 reasons: A) At this point in patch, we dont want to break am57xx-evm - mentioned in diffstat to remind ourselves. B) we are attempting to move all these "cape" like variants into device tree overlays -> in which case the same dtb is reused even for am57xx-evm, and overlay with panel and touchscreen for the "gpevm" panel board.
So, in almost with 80% certainty, we might not introduce a am57xx_evm.dtb in upstream - we really dont need to. In fact, upstream kernel and current master u-boot does bootup successfully, and would like to maintain it so (point A).