I just wanted to add that I realize that it's just remapping the same IRQ.
I've tried changing the values to accommodate SPI (+16) vs PPI (+32) which
has only resulted in failure.
On Wed, Jul 13, 2022, 8:32 AM Brad Churchwell wrote:
> Hi Bertrand,
>
> I did this yesterday
W", but I can't get any further. I made sure that there
was nothing in the device tree that is obviously using IRQ 43 as well.
Any thoughts on this?
Cheers,
Brad
On Wed, Jul 13, 2022, 8:00 AM Bertrand Marquis
wrote:
> Hi Brad
>
> > On 12 Jul 2022, at 17:24, Brad Churchwell
020watchdog@ff848000
pwm@ff420030xin24m
qos@ffa58000
On Tue, Jul 12, 2022 at 11:24 AM Brad Churchwell wrote:
> Hi Bertrand,
>
> I believe I understand, but just to clarify, should I leave the
> ppi-partitions block in rk3399.dtsi as is and disa
22, at 16:59, Brad Churchwell wrote:
> >
> > Hi Bertrand,
> >
> > Thanks so much for the quick response!
> >
> > I should have mentioned previously that this device tree and kernel
> Image (5.15.16) does boot properly with the rootfs without XEN. The
> i
attached the device tree and include files just in case you'd like to
take a look at those.
Thanks so much for your help! I've been at this for weeks with very little
progress.
Cheers,
Brad
On Tue, Jul 12, 2022 at 10:05 AM Bertrand Marquis
wrote:
> Hi Brad,
>
> > On 11 Jul 2022
Hello,
I've been trying to get Xen to boot dom0 with my kernel for weeks on an
rk3399 based board and thought I'd reach out for help. It looks like either
Xen is not properly recreating the device tree or the interrupt controller
is just failing. The hypervisor boots but falls to initramfs because
