Hi Bin,
On Fri, 4 Oct 2019 at 03:45, Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Wed, Sep 25, 2019 at 10:58 PM Simon Glass sjg@chromium.org wrote:
When device-tree compilation fails it is sometimes tricky to see which line is broken, since the input file to dtc is a pre-processed version of the device tree.
Add a line that points to the file that needs to be checked:
Output is something like this:
Error: arch/x86/dts/.chromebook_coral.dtb.pre.tmp:170.15-16 syntax error
This line already provides information that you need.
FATAL ERROR: Unable to parse input tree Check /tmp/b/chromebook_coral/arch/x86/dts/.chromebook_coral.dtb.pre.tmp
I don't understand why we need another line that provides the same information.
Yes that is a bad example, I will update it. If a .dtsi has a CONFIG it is not possible from the source file to work one what when wrong.
for errors
Signed-off-by: Simon Glass sjg@chromium.org
scripts/Makefile.lib | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Regards, Simon