On Tue, Nov 22, 2022 at 04:18:55PM +0100, Jan Stary wrote: > On Nov 22 15:42:20, mark.kette...@xs4all.nl wrote: > > > Date: Tue, 22 Nov 2022 14:40:06 +0100 > > > From: Jan Stary <h...@stare.cz> > > > > > > On Nov 22 13:52:52, h...@stare.cz wrote: > > > > On Nov 14 23:37:05, patr...@blueri.se wrote: > > > > > the u-boot and dtb ports haven't been updated in a while, mostly > > > > > because > > > > > updating those regularly breaks working machines. I think it's time > > > > > for > > > > > another update, so here's a diff for both. > > > > > > > > > > Before this heads into the tree it would be nice to get some testing > > > > > from people with Pinebook Pro, RockPro64, and/or especially a > > > > > BeagleBone > > > > > Black. > > > > > > > > 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. > > > > > > > > I will take the SD card out and remove the com0 boot.conf > > > > to see what's happening once I am near the machine. > > > > > > My bad, it goes to com0 by default, so I did set tty fb0 > > > (as per INSTALL.arm64). Then I see this (jpeg attached, > > > as I have no cereal, and no ddb ps etc, as the usb keyboard > > > does not attach either); in short, > > > > > > panic: bcm_dwctwo_attach: intr_established failed! > > > > 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. So the ones from this dtb port should not be tested on the raspberry pi. Sorry, didn't think about this when I sent out the diff, otherwise I would have mentioned it.
