> > > > > This breakes my RPI4.
> > > > >
> > > > > After replacing the DTBs on the dos partition
> > > > > with those from the new dtb port, the rpi4
> > > > > does not emit anything on the console,
> > > > > and is not reachable over the network.
> > >
> > > Replacing the DTBs with those from the dtb package is not supposed to
> > > work.
> >
> > Ah, in that case I misunderstood the whole effort.
> > The entire content of the dtb package is /usr/local/share/dtb/.../*.dtb
> > - what is supposed to happen with them, i.e. how does one "use" the package?
>
> The raspberry pi is an exception, as the dtb for the raspberry pi come
> from a different firmware package.
To be clear: this applies to all RPIs?
(In particular, both RPI3 and RPI4?)
What is this the other firmware package
where OpenBSD gets the RPI dtbs?
> So the ones from this dtb port
> should not be tested on the raspberry pi.
OK, I'll stick to the BeagleBone Black with this.
> > > Replacing the DTBs with those from the dtb package is not supposed to
> > > work.
Is this specific to the Raspberry, or is that true in general?
The content of the dtb package is a bunch of DTBs unde /usr/local/share
- I am still not sure whether there is anything else to be done
with them besides copying them over to the msdos partition
(as created at install time).
Jan
