That PCI MMIO config space is for a virtual host controller that
> Jailhouse provides. If has to be placed into a free range in the
> physical address space of that target. If you relocate that range in the
> system config, also update the non-root cell device tree. The root cell
> will get that information automatically.
>
> Could you share /proc/iomem (without reservations) from your larger RPi?
>
I know, I was just wondering where that address comes from. So it's just a
randomly chosen address from free space? Or are there any special
requirements that do not apply for the other memory regions and I might be
not aware of them? I'll have to check it over again to share the error I
was getting when I was trying to move it.
/proc/iomem from 8G RPi4 with linux-raspberrypi 4.19 and (almost) default
config.txt:
enable_uart=1
dtoverlay=vc4-fkms-v3d
arm_64bit=1
00000000-3b3fffff : System RAM
00000000-00000fff : reserved
00080000-00c5ffff : Kernel code
00c60000-00d5ffff : reserved
00d60000-00f8ffff : Kernel data
1ec00000-2ebfffff : reserved
2eff5000-2effffff : reserved
373f7000-3b3fefff : reserved
3b3ff000-3b3fffff : reserved
40000000-fbffffff : System RAM
fd500000-fd50930f : pcie@7d500000
fd580000-fd58ffff : genet@7d580000
fd580e14-fd580e1c : unimac-mdio.-19
fd5d2200-fd5d222b : thermal@7d5d2200
fe007000-fe007aff : dma@7e007000
fe007b00-fe007eff : dma@7e007b00
fe00a000-fe00a023 : watchdog@7e100000
fe00b840-fe00b87b : mailbox@7e00b840
fe00b880-fe00b8bf : mailbox@7e00b880
fe100000-fe100113 : watchdog@7e100000
fe101000-fe102fff : cprman@7e101000
fe104000-fe10400f : rng@7e104000
fe200000-fe2000b3 : gpio@7e200000
fe201000-fe2011ff : serial@7e201000
fe201000-fe2011ff : serial@7e201000
fe215000-fe215007 : aux@7e215000
fe215040-fe21507f : serial@7e215040
fe300000-fe3000ff : mmcnr@7e300000
fe340000-fe3400ff : emmc2@7e340000
fec00000-fec03fff : hub
fec04000-fec07fff : core0
fec11000-fec1101f : watchdog@7e100000
100000000-1ffffffff : System RAM
1f7000000-1f7dfffff : reserved
1f7fc2000-1ffdfffff : reserved
1fff00000-1fff5ffff : reserved
1fff60000-1fff60fff : reserved
1fff61000-1fffc0fff : reserved
1fffc3000-1fffc3fff : reserved
1fffc4000-1fffc6fff : reserved
1fffc7000-1ffffefff : reserved
1fffff000-1ffffffff : reserved
600000000-603ffffff : pcie@7d500000
600000000-6000fffff : PCI Bus 0000:01
600000000-600000fff : 0000:01:00.0
600000000-600000fff : xhci-hcd
> Hmm, do not recall the background for that anymore. Why does the overlay
> not work with that currently used DT?
>
> RPi is an (out-of-tree) mess...
>
It's about where the DTBs are taken from. There are two sources, although
the result should be the same:
1) raspberrypi/firmware GitHub repository, where the prebuilt *dtb and
*.dtbos are. That's what is used in jailhouse-images.
2) arch/arm/boot/dts/[overlays] in linux-raspberrypi. That where I can
easily add them with a patch, but they won't make it to the boot partition.
So the thing is that I can make jailhouse-images to use the dtbs built with
kernel instead of the prebuilt ones. Doesn't seem like a big deal. I'm just
aware of the chicken-egg dependency between jailhouse and jailhouse-images,
so I started with this patch first.
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/CAGdCPwsyLjLLaPEsnhr6bwO9ioXQRvSz2Vg%2B48ym-R5kV_V1nA%40mail.gmail.com.
