summaryrefslogtreecommitdiffstats
path: root/meta-agl-bsp/meta-rcar-gen3/recipes-kernel/linux/files/r8a7796-m3ulcb-xen.dts
AgeCommit message (Collapse)AuthorFilesLines
2021-10-29[RCAR] Update RCAR BSP recipes to 5.5.0 versionRonan Le Martret1-91/+0
* rename the dts/dtsi file, the new BSP 5.5.0 change the file name of the dts file. * update the driver files hash * Add "meta-yocto-bsp" to BBLAYERS, it's new dependency of meta-renesas. Bug-AGL: SPEC-4081 Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Change-Id: I53b71906e7174d7b1153a6912f7181171730147c Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26703 Tested-by: Jenkins Job builder account ci-image-build: Jenkins Job builder account ci-image-boot-test: Jenkins Job builder account Reviewed-by: Scott Murray <scott.murray@konsulko.com> Reviewed-by: Stephane Desneux <stephane.desneux@iot.bzh> Reviewed-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
2020-03-12meta-rcar-gen3: Add Xen specific device tree for m3ulcbJérémy Fanguède1-0/+91
Provide a specific version of the device tree (appended with -xen) to run with Xen. Only the R-Car m3ulcb board is supported and tested so far. Add also the Xen block device backend support in the kernel, to be able to run block device based DomU. From U-Boot, Xen and Linux Dom0 can be run as follows (assuming binaries are in sdcard first partition): > setenv bootargs > fatload mmc 0:1 0x48080000 xen-m3ulcb.uImage > fatload mmc 0:1 0x48000000 r8a7796-m3ulcb-xen.dtb > fatload mmc 0:1 0x7a000000 Image-m3ulcb.bin > bootm 0x48080000 - 0x48000000 The Linux Dom0 bootargs are hardcoded in the device tree, the rootfs is expected to be on /dev/mmcblk1p2 Bug-AGL: SPEC-2912 Change-Id: Ia86e0789650eaf79d13691cf4f53755c8cb8f06c Signed-off-by: Jérémy Fanguède <j.fanguede@virtualopensystems.com>