date:20170226

[U-Boot] [RFC PATCH] kbuild: turn of dtc unit address warnings by default

2017-02-26 Thread Masahiro Yamada

DTC 1.4.2 or later checks DT unit-address without reg property and
vice-versa, and generates lots of warnings.  Fixing DT files will
take for a while.  Until then, let's turn off the check unless
building with W=*.

Introduce a new helper dtc-option to check if the option is supported
in order to suppress warnings on older versions.

Signed-off-by: Masahiro Yamada 
---

This is one possible answer to Tom's:
https://www.mail-archive.com/u-boot@lists.denx.de/msg240328.html

He fixed the problem on travis-ci by commit a0f3e3d, but it is still
annoying during the regular development.
Perhaps we may want to hide the warnings (at least hidden in Linux
Kernel by default).
Or, is it better to keep it noisy
to motivate people to fix their DT files?
I am not quite sure...

Now I am sending this as RFC patch in case people may want to start discussion.

BTW, this is a counter-part of the patch I sent to the Kbuild sub-system
(https://patchwork.kernel.org/patch/9592747/)
because I want the U-Boot build system with Linux as much as possible.
Let's see if I will get possible opinions in the Kbuild review.


 Makefile   | 2 +-
 scripts/Kbuild.include | 5 +
 scripts/Makefile.extrawarn | 6 ++
 3 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 38b42da..b258de8 100644
--- a/Makefile
+++ b/Makefile
@@ -371,7 +371,7 @@ export ARCH CPU BOARD VENDOR SOC CPUDIR BOARDDIR
 export CONFIG_SHELL HOSTCC HOSTCFLAGS HOSTLDFLAGS CROSS_COMPILE AS LD CC
 export CPP AR NM LDR STRIP OBJCOPY OBJDUMP
 export MAKE AWK PERL PYTHON
-export HOSTCXX HOSTCXXFLAGS DTC CHECK CHECKFLAGS
+export HOSTCXX HOSTCXXFLAGS CHECK CHECKFLAGS DTC DTC_FLAGS
 
 export KBUILD_CPPFLAGS NOSTDINC_FLAGS UBOOTINCLUDE OBJCOPYFLAGS LDFLAGS
 export KBUILD_CFLAGS KBUILD_AFLAGS
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index 30e6e31..1b62aed 100644
--- a/scripts/Kbuild.include
+++ b/scripts/Kbuild.include
@@ -172,6 +172,11 @@ ld-version = $(shell $(LD) --version | 
$(srctree)/scripts/ld-version.sh)
 # Usage:  $(call ld-ifversion, -ge, 22252, y)
 ld-ifversion = $(shell [ $(ld-version) $(1) $(2) ] && echo $(3) || echo $(4))
 
+# dtc-option
+# Usage:  DTC_FLAGS += $(call dtc-option,-Wno-unit_address_vs_reg)
+dtc-option = $(call try-run,\
+   echo '/dts-v1/; / {};' | $(DTC) $(1),$(1),$(2))
+
 ##
 
 ###
diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn
index 6547e57..7b2cffc 100644
--- a/scripts/Makefile.extrawarn
+++ b/scripts/Makefile.extrawarn
@@ -57,4 +57,10 @@ ifeq ("$(strip $(warning))","")
 endif
 
 KBUILD_CFLAGS += $(warning)
+
+else
+
+# Disable noisy checks by default
+DTC_FLAGS += $(call dtc-option,-Wno-unit_address_vs_reg)
+
 endif
-- 
2.7.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] [PATCH 2/2] ARM: dts: uniphier: fix no unit name warnings

2017-02-26 Thread Masahiro Yamada

Fix warnings reported when built by DTC 1.4.2 or later:
  Node /memory has a reg or ranges property, but no unit name

Signed-off-by: Masahiro Yamada 
---

 arch/arm/dts/uniphier-ld11-ref.dts  | 2 +-
 arch/arm/dts/uniphier-ld11.dtsi | 2 +-
 arch/arm/dts/uniphier-ld20-ref.dts  | 2 +-
 arch/arm/dts/uniphier-ld20.dtsi | 2 +-
 arch/arm/dts/uniphier-ld4-ref.dts   | 2 +-
 arch/arm/dts/uniphier-ld6b-ref.dts  | 2 +-
 arch/arm/dts/uniphier-pro4-ace.dts  | 2 +-
 arch/arm/dts/uniphier-pro4-ref.dts  | 2 +-
 arch/arm/dts/uniphier-pro4-sanji.dts| 2 +-
 arch/arm/dts/uniphier-pxs2-gentil.dts   | 2 +-
 arch/arm/dts/uniphier-pxs2-vodka.dts| 2 +-
 arch/arm/dts/uniphier-sld3-ref.dts  | 2 +-
 arch/arm/dts/uniphier-sld8-ref.dts  | 2 +-
 arch/arm/dts/uniphier-support-card.dtsi | 2 +-
 14 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/arch/arm/dts/uniphier-ld11-ref.dts 
b/arch/arm/dts/uniphier-ld11-ref.dts
index 7693bf2..b4ef804 100644
--- a/arch/arm/dts/uniphier-ld11-ref.dts
+++ b/arch/arm/dts/uniphier-ld11-ref.dts
@@ -29,7 +29,7 @@
i2c5 = 
};
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0 0x8000 0 0x4000>;
};
diff --git a/arch/arm/dts/uniphier-ld11.dtsi b/arch/arm/dts/uniphier-ld11.dtsi
index 38dc1ec..8488984 100644
--- a/arch/arm/dts/uniphier-ld11.dtsi
+++ b/arch/arm/dts/uniphier-ld11.dtsi
@@ -104,7 +104,7 @@
 <1 10 4>;
};
 
-   soc {
+   soc@0 {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
diff --git a/arch/arm/dts/uniphier-ld20-ref.dts 
b/arch/arm/dts/uniphier-ld20-ref.dts
index 41ee07e..61bce42 100644
--- a/arch/arm/dts/uniphier-ld20-ref.dts
+++ b/arch/arm/dts/uniphier-ld20-ref.dts
@@ -29,7 +29,7 @@
i2c5 = 
};
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0 0x8000 0 0xc000>;
};
diff --git a/arch/arm/dts/uniphier-ld20.dtsi b/arch/arm/dts/uniphier-ld20.dtsi
index 7176757..d853526 100644
--- a/arch/arm/dts/uniphier-ld20.dtsi
+++ b/arch/arm/dts/uniphier-ld20.dtsi
@@ -173,7 +173,7 @@
 <1 10 4>;
};
 
-   soc {
+   soc@0 {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
diff --git a/arch/arm/dts/uniphier-ld4-ref.dts 
b/arch/arm/dts/uniphier-ld4-ref.dts
index 0f4bd9b..95fe90c 100644
--- a/arch/arm/dts/uniphier-ld4-ref.dts
+++ b/arch/arm/dts/uniphier-ld4-ref.dts
@@ -16,7 +16,7 @@
model = "UniPhier LD4 Reference Board";
compatible = "socionext,uniphier-ld4-ref", "socionext,uniphier-ld4";
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0x8000 0x2000>;
};
diff --git a/arch/arm/dts/uniphier-ld6b-ref.dts 
b/arch/arm/dts/uniphier-ld6b-ref.dts
index 4da3c63..e9ab1e9 100644
--- a/arch/arm/dts/uniphier-ld6b-ref.dts
+++ b/arch/arm/dts/uniphier-ld6b-ref.dts
@@ -16,7 +16,7 @@
model = "UniPhier LD6b Reference Board";
compatible = "socionext,uniphier-ld6b-ref", "socionext,uniphier-ld6b";
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0x8000 0x8000>;
};
diff --git a/arch/arm/dts/uniphier-pro4-ace.dts 
b/arch/arm/dts/uniphier-pro4-ace.dts
index f70bc82..4f81d3c 100644
--- a/arch/arm/dts/uniphier-pro4-ace.dts
+++ b/arch/arm/dts/uniphier-pro4-ace.dts
@@ -14,7 +14,7 @@
model = "UniPhier Pro4 Ace Board";
compatible = "socionext,uniphier-pro4-ace", "socionext,uniphier-pro4";
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0x8000 0x4000>;
};
diff --git a/arch/arm/dts/uniphier-pro4-ref.dts 
b/arch/arm/dts/uniphier-pro4-ref.dts
index 9714fb0..6431912 100644
--- a/arch/arm/dts/uniphier-pro4-ref.dts
+++ b/arch/arm/dts/uniphier-pro4-ref.dts
@@ -16,7 +16,7 @@
model = "UniPhier Pro4 Reference Board";
compatible = "socionext,uniphier-pro4-ref", "socionext,uniphier-pro4";
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0x8000 0x4000>;
};
diff --git a/arch/arm/dts/uniphier-pro4-sanji.dts 
b/arch/arm/dts/uniphier-pro4-sanji.dts
index d43f725..33380a0 100644
--- a/arch/arm/dts/uniphier-pro4-sanji.dts
+++ b/arch/arm/dts/uniphier-pro4-sanji.dts
@@ -14,7 +14,7 @@
model = "UniPhier Pro4 Sanji Board";
compatible = "socionext,uniphier-pro4-sanji", "socionext,uniphier-pro4";
 
-   memory {
+   memory@8000 {
device_type = "memory";
reg = <0x8000 0x8000>;
};
diff --git a/arch/arm/dts/uniphier-pxs2-gentil.dts

[U-Boot] [PATCH 1/2] ARM: dts: uniphier: remove skeleton.dtsi inclusion

2017-02-26 Thread Masahiro Yamada

Linux Commit 9c0da3cc61f1 ("ARM: dts: explicitly mark skeleton.dtsi
as deprecated") declared that skeleton.dtsi was deprecated.

Signed-off-by: Masahiro Yamada 
---

 arch/arm/dts/uniphier-ld4.dtsi  | 4 ++--
 arch/arm/dts/uniphier-pro4.dtsi | 4 ++--
 arch/arm/dts/uniphier-pro5.dtsi | 4 ++--
 arch/arm/dts/uniphier-pxs2.dtsi | 4 ++--
 arch/arm/dts/uniphier-sld3.dtsi | 4 ++--
 arch/arm/dts/uniphier-sld8.dtsi | 4 ++--
 6 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/arch/arm/dts/uniphier-ld4.dtsi b/arch/arm/dts/uniphier-ld4.dtsi
index bbfa164..0d3d963 100644
--- a/arch/arm/dts/uniphier-ld4.dtsi
+++ b/arch/arm/dts/uniphier-ld4.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-ld4";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
diff --git a/arch/arm/dts/uniphier-pro4.dtsi b/arch/arm/dts/uniphier-pro4.dtsi
index 9b881f6..210ac27 100644
--- a/arch/arm/dts/uniphier-pro4.dtsi
+++ b/arch/arm/dts/uniphier-pro4.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-pro4";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
diff --git a/arch/arm/dts/uniphier-pro5.dtsi b/arch/arm/dts/uniphier-pro5.dtsi
index 68866e1..de98697 100644
--- a/arch/arm/dts/uniphier-pro5.dtsi
+++ b/arch/arm/dts/uniphier-pro5.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-pro5";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
diff --git a/arch/arm/dts/uniphier-pxs2.dtsi b/arch/arm/dts/uniphier-pxs2.dtsi
index da62070..904320c 100644
--- a/arch/arm/dts/uniphier-pxs2.dtsi
+++ b/arch/arm/dts/uniphier-pxs2.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-pxs2";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
diff --git a/arch/arm/dts/uniphier-sld3.dtsi b/arch/arm/dts/uniphier-sld3.dtsi
index 919cbff..7578920 100644
--- a/arch/arm/dts/uniphier-sld3.dtsi
+++ b/arch/arm/dts/uniphier-sld3.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-sld3";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
diff --git a/arch/arm/dts/uniphier-sld8.dtsi b/arch/arm/dts/uniphier-sld8.dtsi
index 5550bb8..4117132 100644
--- a/arch/arm/dts/uniphier-sld8.dtsi
+++ b/arch/arm/dts/uniphier-sld8.dtsi
@@ -7,10 +7,10 @@
  * SPDX-License-Identifier:GPL-2.0+X11
  */
 
-/include/ "skeleton.dtsi"
-
 / {
compatible = "socionext,uniphier-sld8";
+   #address-cells = <1>;
+   #size-cells = <1>;
 
cpus {
#address-cells = <1>;
-- 
2.7.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] travis-ci: Temporarily disable using a newer device tree compiler

2017-02-26 Thread Robert Nelson

On Sun, Feb 26, 2017 at 11:29 PM, Heiko Schocher  wrote:
> Hello Robert,
>
> Am 27.02.2017 um 05:34 schrieb Robert Nelson:
>>
>> On Sun, Feb 26, 2017 at 7:37 PM, Tom Rini  wrote:
>>>
>>> On Sun, Feb 26, 2017 at 08:01:19PM -0500, Tom Rini wrote:
>>>
 For a long while dtc has warned about various constructs.  This is now
 leading to log file size being exceeded in travis, and as the majority
 of these errors need to be fixed in the kernel, switch to using the
 stock device-tree-compiler package.

 Signed-off-by: Tom Rini 
>>>
>>>
>>> Applied to u-boot/master, thanks!
>>>
>>> But I'm not happy to have to apply it, either.  I do not wish to break
>>> travis-ci, but sun7i is now exceeding the allowed stdout size.  And
>>> these are problems that need to be fixed in the kernel first, rather
>>> than here first.  The patches to fix u-boot local issues (such as x86
>>> never got picked up either, but likely need to be respun.  I expect that
>>> once the new DTC version is tagged and populated upstream in the kernel
>>> as well, we will be able to re-enable the changes we had here.
>>
>>
>> This was fixed (aka a hidden bandaid) in the linux kernel via:
>>
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/scripts/Makefile.lib?id=bc553986a2f7c56d0de811485d5312ea29692d5d
>
>
> Heh... IIRC, I tried to fix a lot of this messages (in U-Boot), around
> a year ago, and we decided to not apply them in u-boot, instead they
> should go away via kernel resyncs, when the warnings are fixed in the
> kernel!
>
> Also I think, I tried a similiar approach as the commit you mentioned...
> Ah, yes, here:
> http://lists.denx.de/pipermail/u-boot/2016-April/252408.html
>
> We decided (for u-boot) it would be better to fix the problems and
> not supress the warning, but it seems, the problems get not really fixed
> in the kernel ...
>
> I wasn;t aware of the above patch in the kernel... thanks for pointing!

and i think by moving the kernel to disable that patch, it's slowed
down the number of register fix patches..

ps, this just came in on kbuild list just a few minutes ago:

https://marc.info/?l=linux-kbuild=148817429929267=2

one of the issues with bc553986a2f7c56d0de811485d5312ea29692d5d is
that it breaks the build with older version of dtc that don't know
what to do with the -Wno-unit_address_vs_reg flag..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH 14/20] arm: socfpga: add SPL support for Arria 10

2017-02-26 Thread Chee, Tien Fong

On Sab, 2017-02-25 at 22:43 +0100, Marek Vasut wrote:
> On 02/22/2017 10:47 AM, Ley Foon Tan wrote:
> > 
> > Add SPL support for Arria 10.
> > 
> > Signed-off-by: Tien Fong Chee 
> > Signed-off-by: Ley Foon Tan 
> > ---
> >  arch/arm/mach-socfpga/spl.c | 92
> > -
> >  1 file changed, 90 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/mach-socfpga/spl.c b/arch/arm/mach-
> > socfpga/spl.c
> > index fec4c7a..1299e67 100644
> > --- a/arch/arm/mach-socfpga/spl.c
> > +++ b/arch/arm/mach-socfpga/spl.c
> > @@ -19,37 +19,55 @@
> >  #include 
> >  #include 
> >  #include 
> > +#include 
> > +#include 
> > +#include 
> > +#if defined(CONFIG_TARGET_SOCFPGA_ARRIA10)
> > +#include 
> > +#endif
> >  
> >  DECLARE_GLOBAL_DATA_PTR;
> >  
> > +#if defined(CONFIG_TARGET_SOCFPGA_GEN5)
> > +#define BOOTINFO_BSEL_SHIFT0
> Wasn't this defined in the misc support patch already ?
> 
> > 
> >  static struct pl310_regs *const pl310 =
> >     (struct pl310_regs *)CONFIG_SYS_PL310_BASE;
> >  static struct scu_registers *scu_regs =
> >     (struct scu_registers *)SOCFPGA_MPUSCU_ADDRESS;
> >  static struct nic301_registers *nic301_regs =
> >     (struct nic301_registers *)SOCFPGA_L3REGS_ADDRESS;
> > -static struct socfpga_system_manager *sysmgr_regs =
> > +#elif defined(CONFIG_TARGET_SOCFPGA_ARRIA10)
> > +#define BOOTINFO_BSEL_SHIFT12
> > +#endif
> > +
> > +static const struct socfpga_system_manager *sysmgr_regs =
> >     (struct socfpga_system_manager *)SOCFPGA_SYSMGR_ADDRESS;
> >  
> >  u32 spl_boot_device(void)
> >  {
> >     const u32 bsel = readl(_regs->bootinfo);
> >  
> > -   switch (bsel & 0x7) {
> > +   switch ((bsel >> BOOTINFO_BSEL_SHIFT) & 0x7) {
> >     case 0x1:   /* FPGA (HPS2FPGA Bridge) */
> >     return BOOT_DEVICE_RAM;
> >     case 0x2:   /* NAND Flash (1.8V) */
> >     case 0x3:   /* NAND Flash (3.0V) */
> > +#if defined(CONFIG_TARGET_SOCFPGA_GEN5)
> >     socfpga_per_reset(SOCFPGA_RESET(NAND), 0);
> > +#endif
> >     return BOOT_DEVICE_NAND;
> >     case 0x4:   /* SD/MMC External Transceiver (1.8V) */
> >     case 0x5:   /* SD/MMC Internal Transceiver (3.0V) */
> > +#if defined(CONFIG_TARGET_SOCFPGA_GEN5)
> >     socfpga_per_reset(SOCFPGA_RESET(SDMMC), 0);
> >     socfpga_per_reset(SOCFPGA_RESET(DMA), 0);
> > +#endif
> >     return BOOT_DEVICE_MMC1;
> >     case 0x6:   /* QSPI Flash (1.8V) */
> >     case 0x7:   /* QSPI Flash (3.0V) */
> > +#if defined(CONFIG_TARGET_SOCFPGA_GEN5)
> >     socfpga_per_reset(SOCFPGA_RESET(QSPI), 0);
> > +#endif
> This looks awful, you might want to split this function into
> A10-specific and Gen5 specific one(s) .
> 
#if defined(CONFIG_TARGET_SOCFPGA_GEN5) can be removed, Arria10 would
use the same implementation as gen5.
> > 
> >     return BOOT_DEVICE_SPI;
> >     default:
> >     printf("Invalid boot device (bsel=%08x)!\n",
> > bsel);
> > @@ -68,6 +86,7 @@ u32 spl_boot_mode(const u32 boot_device)
> >  }
> >  #endif
> >  
> > +#if defined(CONFIG_TARGET_SOCFPGA_GEN5)
> >  static void socfpga_nic301_slave_ns(void)
> >  {
> >     writel(0x1, _regs->lwhps2fpgaregs);
> > @@ -182,3 +201,72 @@ void board_init_f(ulong dummy)
> >     /* Configure simple malloc base pointer into RAM. */
> >     gd->malloc_base = CONFIG_SYS_TEXT_BASE + (1024 * 1024);
> >  }
> > +#elif defined(CONFIG_TARGET_SOCFPGA_ARRIA10)
> > +#ifdef CONFIG_SPL_BOARD_INIT
> > +void spl_board_init(void)
> > +{
> > +   /* configuring the clock based on handoff */
> > +   cm_basic_init(gd->fdt_blob);
> > +   WATCHDOG_RESET();
> > +
> > +   config_dedicated_pins(gd->fdt_blob);
> > +   WATCHDOG_RESET();
> > +
> > +   /* Release UART from reset */
> > +   reset_deassert_uart();
> > +
> > +   /* enable console uart printing */
> > +   preloader_console_init();
> > +}
> > +#endif
> > +
> > +void board_init_f(ulong dummy)
> > +{
> > +   memset(__bss_start, 0, __bss_end - __bss_start);
> Is this really needed ? Should be done by common code already ...
> 
> > 
> > +   /*
> > +    * Configure Clock Manager to use intosc clock instead
> > external osc to
> > +    * ensure success watchdog operation. We do it as early as
> > possible.
> > +    */
> > +   cm_use_intosc();
> > +
> > +   watchdog_disable();
> > +
> > +   arch_early_init_r();
> > +
> > +#ifdef CONFIG_HW_WATCHDOG
> > +   /* release osc1 watchdog timer 0 from reset */
> > +   reset_deassert_osc1wd0();
> > +
> > +   /* reconfigure and enable the watchdog */
> > +   hw_watchdog_init();
> > +   WATCHDOG_RESET();
> > +#endif /* CONFIG_HW_WATCHDOG */
> > +
> > +#ifdef CONFIG_OF_CONTROL
> > +   /* We need to access to FDT as this stage */
> > +   /* FDT is at end of image */
> > +   gd->fdt_blob = (void *)(__bss_end);
> This looks like common code too ?
> 
> > 
> > +   /* Check whether we have a valid FDT or not. */
> > +   if (fdtdec_prepare_fdt()) {
> > +

Re: [U-Boot] [PATCH] travis-ci: Temporarily disable using a newer device tree compiler

2017-02-26 Thread Heiko Schocher

Hello Robert,

Am 27.02.2017 um 05:34 schrieb Robert Nelson:

On Sun, Feb 26, 2017 at 7:37 PM, Tom Rini wrote:

On Sun, Feb 26, 2017 at 08:01:19PM -0500, Tom Rini wrote:

For a long while dtc has warned about various constructs. This is now
leading to log file size being exceeded in travis, and as the majority
of these errors need to be fixed in the kernel, switch to using the
stock device-tree-compiler package.

Signed-off-by: Tom Rini

Applied to u-boot/master, thanks!

But I'm not happy to have to apply it, either. I do not wish to break
travis-ci, but sun7i is now exceeding the allowed stdout size. And
these are problems that need to be fixed in the kernel first, rather
than here first. The patches to fix u-boot local issues (such as x86
never got picked up either, but likely need to be respun. I expect that
once the new DTC version is tagged and populated upstream in the kernel
as well, we will be able to re-enable the changes we had here.

This was fixed (aka a hidden bandaid) in the linux kernel via:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/scripts/Makefile.lib?id=bc553986a2f7c56d0de811485d5312ea29692d5d

Heh... IIRC, I tried to fix a lot of this messages (in U-Boot), around
a year ago, and we decided to not apply them in u-boot, instead they
should go away via kernel resyncs, when the warnings are fixed in the
kernel!

Also I think, I tried a similiar approach as the commit you mentioned...
Ah, yes, here:
http://lists.denx.de/pipermail/u-boot/2016-April/252408.html

We decided (for u-boot) it would be better to fix the problems and
not supress the warning, but it seems, the problems get not really fixed
in the kernel ...

I wasn;t aware of the above patch in the kernel... thanks for pointing!

@Tom:
So, I feel, the problems get not fixed fast in the kernel (if ever),
may we want to cherry-pick this patch from the kernel (or make a
similiar patch for U-Boot)?

bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

69 matches

Mail list logo