On 7/20/19 12:22 PM, Peter Robinson wrote: >> On 7/19/19 9:06 PM, Peter Robinson wrote: >>> On Fri, Jul 19, 2019 at 7:28 PM Heinrich Schuchardt <[email protected]> >>> wrote: >>>> >>>> In GRUB before 2.04 a bug existed which did not allow booting some ARM32 >>>> boards if U-Boot did not disable caches, cf. >>>> https://lists.linaro.org/pipermail/cross-distro/2019-July/000933.html >>>> >>>> In ExitBootServices() we were disabling the caches by calling >>>> cleanup_before_linux(). This workaround is not needed anymore. >>> >>> Do we want to remove this straight away? A lot of distributions will >>> take time to move to grub 2.04 because it's been a long time between >>> grub releases so they'll have quite a patch delta to re-align to the >>> new release. Fedora for example will rebase to grub 2.04 in Fedora 32 >>> which will start development end of August but won't be released until >>> next year. >> >> As described below this code does not remove any functionality that was >> active in U-Boot v2019.04 or v2019.07. >> >> I can see nothing in https://fedoraproject.org/wiki/Updates_Policy >> stopping GRUB 2.04 from being made available for stable Fedora releases. > > The maintainers believe that it's too intrusive to land now and they > want maximum testing time before it gets to stable users, funnily > enough people don't like it when their machines cease to boot.
Why should anybody's machines cease to boot? If Fedora does not role out a new U-Boot they are fine. If Fedora roles out a new U-Boot they should role out a matching GRUB and they are fine too. The venturous who build their own U-Boot should know how to role back their system if needed. Best regards Heinrich _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
