RPi4 Status and sysutils/rpi-firmware
Emmanuel Vadot
manu at bidouilliste.com
Wed Mar 3 08:12:42 UTC 2021
On Tue, 2 Mar 2021 19:55:54 +0100
Klaus Küchemann <maciphone2 at googlemail.com> wrote:
>
> On 2021-Mar-2, at 03:20, Emmanuel Vadot <manu at bidouilliste.com> wrote:
> >
> >
> >> ____________________
> > freebsd-arm at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org?
>
>
> I could write a WIKI-article(!, lol ) about how to fix these firmware-problems and get rid of them forever.
That's not true.
Even if we find a version of the firmware files that works for every
RPI boards that all of our users have right now, we will need to update
them when a new RPI boards is out. And with the Compute Module 4 being
out and a lot more carrier board being made than for the CM3 I expect a
lot more firmware updates than before.
> I could also offer a dtb-patch
Your earlier proposal was to commit into base a modified DTS based on
(I think) a decompiled version of the rpi-firmware DTB and put that in
place of the Linux mainline DTS (which is different) in the contrib
device-tree import tree.
This cannot work in the long time, if you don't see a problem I'm
soryr for you.
> u-boot-updates, netboot-tools
You can still do that.
> perhaps write a driver etc. :-) Ha Ha
Same thing, you can still do that.
> There's no reason to think the RPI4 does perform bad with FreeBSD
That's not what this thread is about.
> I know boards with more problems.
> But this topic is old stuff.
>
> K.
>
--
Emmanuel Vadot <manu at bidouilliste.com> <manu at FreeBSD.org>
More information about the freebsd-arm
mailing list