On 4/12/19 9:56 PM, Michael Scott wrote:
Support RISC-V kernel image, using the "Image" target.
This change allows RISC-V support for fitImage via the following
flow: OpenSBI -> u-boot (as payload) -> Linux kernel (as fitImage
with ramdisk and dtb).
This was tested using QEMU RISC-V 64-bit.
Signed-off-by: Michael Scott <m...@foundries.io>
---
meta/classes/kernel-fitimage.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/kernel-fitimage.bbclass
b/meta/classes/kernel-fitimage.bbclass
index 2517d75746..09abedff8e 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -8,7 +8,7 @@ python __anonymous () {
d.setVar("DEPENDS", depends)
uarch = d.getVar("UBOOT_ARCH")
- if uarch == "arm64":
+ if uarch == "arm64" or uarch == "riscv":
I didn't see any response to this v2 patch. Is this approach
acceptible? RISC-V should not attempt to use zImage for fitImage as it
now stands.
replacementtype = "Image"
elif uarch == "mips":
replacementtype = "vmlinuz.bin"
--
Michael Scott
Embedded Software Engineer at Foundries.io
"microPlatforms™ for Connected Products"
E: m...@foundries.io
W: https://www.foundries.io
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
