> >> Actually I suspect that's because it's a different config and hence
> >> the issue, I suspect once the detection bit is fixed that issue may
> >> just go away.
> >
> > Could be. I'm working with a U-Boot dev right now who sent me two patches
> > to u-boot to try to fix the detection. So now I get to figure out how to
> > build u-boot to test it out.
> >
> > Pulling down 2020.04 from F32-beta was easy. Building it.... We'll see!
> > Can I build it on my x86_64? ;)
>
> He saved me hours and sent me files to test and they worked. So he's
> preparing a patch to send to the u-boot list. Hopefully that patch can
> get pulled into Fedora 32?
We don't tend to build U-Boot once a release goes GA, primarily just
due to lack of resources. That said U-Boot is firmware and completely
independent of the OS, we only build it due to convenience so using a
f33/rawhide build with F-32 OS is completely stable and works just
fine.
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
No comments:
Post a Comment