On Tue, 1 Sep 2020 at 01:53, Jan Kiszka <jan.kis...@siemens.com> wrote:
> ...and that is because the RPi kernel is downstream, and it's > dt-bindings are moving targets. As we pull the dtbs from the firmware > repo and not from the kernel build, we need to keep both in sync. Sigh. > > We could more or less easily switch at least the main dtb to the kernel > build, but we would still risk to break the overlays. Maybe I will try > to align it all eventually, but for now the knowledge about the > dependency may already help on next update. > > I think it might be actually better to switch to the DTBs from the kernel repo. The overlays are there (see arch/arm/boot/dts/overlays) and it's the way how Yocto's meta-raspberrypi does it and it seems to work fine. > >> > >> By the way, for some reason the ivshmem-net is showing up as eth1 in the > >> -next build and thus is not being configured automatically. > > > > That was fine here. I specifically tested this path as it exposed the > > GICv2 bug in Jailhouse. Will double-check after updating the firmware. > > > > RPi dropped the linux,pci-domain property from the physical pci host, > and that made our vpci config incompatible, moving it to an unexpected > domain. Fixed, please have a look at the v2 series I just sent. > > Will take a look. Jakub -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to jailhouse-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/CAGdCPwsDoF-HSb_Lpx_mWw-DAqbwOWJ%2BW%3Dm%2B06Nac6DMRp%3D6NQ%40mail.gmail.com.
