Re: [U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init found

2017-04-05 Thread Nathan Rossi
On 4 April 2017 at 17:20, Michal Simek wrote: > On 3.4.2017 13:38, Jean-Francois Dagenais wrote: >> >>> On Apr 3, 2017, at 02:55, Michal Simek wrote: >>> >>> This is not only one way how to configure system. You can use >>> psu_init*.tcl and configure chip through jtag and then you don't need >>>

Re: [U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init found

2017-04-04 Thread Jean-Francois Dagenais
> On Apr 3, 2017, at 02:55, Michal Simek wrote: > > This is not only one way how to configure system. You can use > psu_init*.tcl and configure chip through jtag and then you don't need > this .c/.h files. > You should be able to see warning already about it if you miss that files. Mmh. I had t

[U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init found

2017-04-04 Thread Jean-Francois Dagenais
When doing the SPL build, not finding the psu_init files yields an unuseable spl binary. Time is wasted as the build is carried through dev ops all the way to trying to boot the DUD build. A failure immediately alerts developers that something is wrong in the configuration of the u-boot tree, thus

Re: [U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init found

2017-04-04 Thread Michal Simek
On 3.4.2017 13:38, Jean-Francois Dagenais wrote: > >> On Apr 3, 2017, at 02:55, Michal Simek wrote: >> >> This is not only one way how to configure system. You can use >> psu_init*.tcl and configure chip through jtag and then you don't need >> this .c/.h files. >> You should be able to see warnin

Re: [U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init found

2017-04-02 Thread Michal Simek
Hi, On 3.4.2017 02:51, Jean-Francois Dagenais wrote: > When doing the SPL build, not finding the psu_init files yields an > unuseable spl binary. Time is wasted as the build is carried through dev > ops all the way to trying to boot the DUD build. > > A failure immediately alerts developers that