From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michal Simek <michal.simek@xilinx.com>
Date: Tue, 4 Apr 2017 09:20:28 +0200
Subject: [U-Boot] [PATCH] arm64: zynqmp: fail SPL build if no psu_init
	found
In-Reply-To: <7177F7D8-CB8F-4205-AD7C-174704A7C600@gmail.com>
References: <1491180708-16121-1-git-send-email-jeff.dagenais@gmail.com>
 <efb67fec-c6b2-78a5-470e-6d11fd53c775@xilinx.com>
 <7177F7D8-CB8F-4205-AD7C-174704A7C600@gmail.com>
Message-ID: <9fc1c03a-a34c-74df-19f2-0fa333a62563@xilinx.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 3.4.2017 13:38, Jean-Francois Dagenais wrote:
> 
>> On Apr 3, 2017, at 02:55, Michal Simek <michal.simek@xilinx.com> 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 thought of that, but it seemed like this scenario might have been a
> minority issue. I guess this is a very yocto-centric problem. Warnings emitted
> inside builds that bitbake spawns are only visible in a log file for each steps
> (configure, compile, etc.) inside each recipe's work dir and so they are
> completely invisible to the operator that invokes bitbake.
> 
> Perhaps I should come up with a strategy to emerge this particular warning in
> the u-boot-xlnx_%.bb recipe?
> 
> Thoughts?

No idea but u-boot does it IMHO right.

M