[U-Boot] [ANN] U-Boot v2018.09-rc2 released

Jagan Teki jagan at amarulasolutions.com
Wed Aug 15 05:55:21 UTC 2018


On Wed, Aug 15, 2018 at 2:35 AM, Peter Robinson <pbrobinson at gmail.com> wrote:
> On Tue, Aug 14, 2018 at 2:22 AM, Tom Rini <trini at 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
[2] for discussion.

[2] http://u-boot.10912.n7.nabble.com/U-Boot-2018-07-Still-Broken-for-Allwinner-H3-SoCs-td334464.html#a334570


More information about the U-Boot mailing list