On Sun, Feb 26, 2017 at 11:52:21PM -0600, Robert Nelson wrote: > On Sun, Feb 26, 2017 at 11:29 PM, Heiko Schocher <h...@denx.de> wrote: > > Hello Robert, > > > > Am 27.02.2017 um 05:34 schrieb Robert Nelson: > >> > >> On Sun, Feb 26, 2017 at 7:37 PM, Tom Rini <tr...@konsulko.com> 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 <tr...@konsulko.com> > >>> > >>> > >>> 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&m=148817429929267&w=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..
Coalescing things back in to one thread, yes, for the next release, we should switch over to key'ing the warning based on KBUILD_ENABLE_EXTRA_GCC_CHECKS and only once the patch to conditionally pass the flag in question is possible as well. Thanks all! -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/listinfo/u-boot
