On Wed, Aug 15, 2018 at 07:14:16AM +0100, Peter Robinson wrote: > On Wed, Aug 15, 2018 at 7:13 AM, Jagan Teki <ja...@amarulasolutions.com> > wrote: > > On Wed, Aug 15, 2018 at 11:40 AM, Peter Robinson <pbrobin...@gmail.com> > > wrote: > >> On Wed, Aug 15, 2018 at 6:55 AM, Jagan Teki <ja...@amarulasolutions.com> > >> wrote: > >>> On Wed, Aug 15, 2018 at 2:35 AM, Peter Robinson <pbrobin...@gmail.com> > >>> wrote: > >>>> On Tue, Aug 14, 2018 at 2:22 AM, Tom Rini <tr...@konsulko.com> wrote: > >>>>> Hey all, > >>>>> > >>>>> It is release day and despite Travis-CI being really bad about network > >>>>> connections over the weekend, it's back to normal today at least. So > >>>>> I'm putting out v2018.09-rc2 now. I plan on looking at Kconfig > >>>>> migrations and similar things that I can size-test. I think there's > >>>>> still a code removal patch or two I can apply as well at this point. > >>>>> > >>>>> Things look on track for -rc3 on the 27th, -rc4 on September 3rd and > >>>>> then final release on September 10th. Thanks all! > >>>> > >>>> So the AllWinner H3 SoC still appears to be broken in rc2 from the > >>>> regression that happened just before 2018.07 GA, it was discussed in a > >>>> couple of threads but I had no answer from previous inquiry [1], does > >>>> anyone know if there was a conclusion as to the best fix for this? > >>>> > >>>> ## Flattened Device Tree blob at 43000000 > >>>> Booting using the fdt blob at 0x43000000 > >>>> EHCI failed to shut down host controller. > >>>> EHCI failed to shut down host controller. > >>>> EHCI failed to shut down host controller. > >>>> EHCI failed to shut down host controller. > >>>> Loading Ramdisk to 49350000, end 49fff4f9 ... OK > >>>> Loading Device Tree to 49348000, end 4934fa97 ... OK > >>>> > >>>> Starting kernel ... > >>>> > >>>> and it just hangs > >>>> > >>>> [1] https://lists.denx.de/pipermail/u-boot/2018-August/336837.html > >>> > >>> What is this board? Is it reproducing GCC 6.3-2017.02? See this thread > >> > >> It's a Orange Pi PC built using gcc 8.2 in Fedora 29. Fedora has a > >> policy of requiring the distro toolchain so I don't have an option of > >> using some random toolkit how some users "fixed" it. > > > > That may be fedora choice, we just need to understand whether it work > > with other toolchain or not? > > It also works with 2018.07-rc3
Yes, we cannot say "Oh, you must use $toolchain only" as that means there's some real bug that's being papered over by how things are optimized or some compiler bug being tickled by the code. But it's also a good data point to have. Can you please do a one-off manual build and see if it does work with that toolchain? Thanks! -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
