arm-trusted-firmware: add upstream version 2.2
PATCH 1/1 arm-trusted-firmware: add upstream version 2.2
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55 -0
@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot"
Signature · 1 line
2.7.4
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
What's the delta between the two ?
Bruce
Quoted 77 lines
Signed-off-by Denys Dmytriyenko <[email protected]>Cc Joshua Watt <[email protected]>--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bbmeta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55
-1@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot" --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 9 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Quoted 4 lines
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Signature · 1 line
Denys
Quoted 84 lines
Quoted 76 lines
Signed-off-by Denys Dmytriyenko <[email protected]>Cc Joshua Watt <[email protected]>--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bbmeta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55
-1@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot" --2.7.4
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-coreSignature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 11 lines · Denys Dmytriyenko
Quoted 10 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
Quoted 6 lines
Quoted 1 line
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116
FWIW, variants of this recipe crop up in pretty much every ARM-based BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb); it seems common enough that a base recipe that each BSP layer can bbappend to suite their needs seems like it would be useful?
Quoted 6 lines
Quoted 3 lines
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Quoted 21 lines · Joshua Watt
Quoted 11 lines · Denys Dmytriyenko
Quoted 10 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
Quoted 6 lines
Quoted 1 line
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116
Quoted 5 lines
FWIW, variants of this recipe crop up in pretty much every ARM-based BSP layer (e.g.
https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
it seems common enough that a base recipe that each BSP layer can bbappend to suite their needs seems like it would be useful?
Jon had some ideas about that, but I admit to only being an interested party and since I was aware of what he was up to, that I'd draw him into the conversation.
Definitely a good thing to get some sort of centralized base recipe, that can be extended by layers.
Bruce
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 16 lines · Joshua Watt
Quoted 14 lines · Denys Dmytriyenko
Quoted 11 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
Quoted 8 lines
Quoted 3 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116FWIW, variants of this recipe crop up in pretty much every ARM-based
BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
it seems common enough that a base recipe that each BSP layer can
bbappend to suite their needs seems like it would be useful?
Yes, indeed, hence we agreed to submit it to oe-core...
And meta-arm sounds like a good idea and can be used by all those ARM-based BSPs as a base, but for some reason I cannot find any announcements for that new layer... Jon?
Signature · 1 line
Denys
Quoted 5 lines
Quoted 4 lines
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Quoted 27 lines · Denys Dmytriyenko
Quoted 16 lines · Joshua Watt
Quoted 14 lines · Denys Dmytriyenko
Quoted 11 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
Quoted 8 lines
Quoted 3 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116FWIW, variants of this recipe crop up in pretty much every ARM-based
BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
it seems common enough that a base recipe that each BSP layer can
bbappend to suite their needs seems like it would be useful?
Quoted 5 lines
Yes, indeed, hence we agreed to submit it to oe-core...
And meta-arm sounds like a good idea and can be used by all those ARM-based BSPs as a base, but for some reason I cannot find any announcements for that new layer... Jon?
Sorry, I was unaware that it was common practice to announce this kind of thing. Also, it was very barebones for the first few weeks. In fact, I still think it is minimal. That being said, I'll send email to OE-devel (and/or OE-Core) announcing it properly.
Thanks,
Jon
Quoted 15 lines
--
DenysQuoted 5 lines
Quoted 4 lines
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 30 lines · Jon Mason
Quoted 29 lines · Denys Dmytriyenko
Quoted 16 lines · Joshua Watt
Quoted 14 lines · Denys Dmytriyenko
Quoted 11 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
Quoted 8 lines
Quoted 3 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116FWIW, variants of this recipe crop up in pretty much every ARM-based
BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
it seems common enough that a base recipe that each BSP layer can
bbappend to suite their needs seems like it would be useful?Yes, indeed, hence we agreed to submit it to oe-core...
Quoted 8 lines
Quoted 3 lines
And meta-arm sounds like a good idea and can be used by all those ARM-based BSPs as a base, but for some reason I cannot find any announcements for that new layer... Jon?
Sorry, I was unaware that it was common practice to announce this kind of thing. Also, it was very barebones for the first few weeks. In fact, I still think it is minimal. That being said, I'll send email to OE-devel (and/or OE-Core) announcing it properly.
If you want it to be a base for other ARM-based BSP layers, it should be very well known, well maintained and Yocto-compliant. I see there are multiple sub-layers in meta-arm and there was a recent discussion how to properly separate things in those sub-layers - BSP, Distro and Apps w/o mixing them.
For example, our meta-ti BSP layer has no other dependency besides OE-Core, making it very clean. In order for me to make meta-ti also depend on meta-arm for ATF, OPTEE, etc., I would like it to be up to the quality standards of OE-Core! So, the bar is quite high, but I'm willing to help and work in that direction with you and others.
Signature · 1 line
Denys
Quoted 20 lines
Thanks,
JonQuoted 15 lines
--
DenysQuoted 5 lines
Quoted 4 lines
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 41 lines · Denys Dmytriyenko
Quoted 30 lines · Jon Mason
Quoted 29 lines · Denys Dmytriyenko
Quoted 16 lines · Joshua Watt
Quoted 14 lines · Denys Dmytriyenko
Quoted 11 lines · Bruce Ashfield
Quoted 6 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
Quoted 8 lines
Quoted 3 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116FWIW, variants of this recipe crop up in pretty much every ARM-based
BSP layer (e.g. https://github.com/alistair23/meta-pine64/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb);
it seems common enough that a base recipe that each BSP layer can
bbappend to suite their needs seems like it would be useful?Yes, indeed, hence we agreed to submit it to oe-core...
Quoted 8 lines
Quoted 3 lines
And meta-arm sounds like a good idea and can be used by all those ARM-based BSPs as a base, but for some reason I cannot find any announcements for that new layer... Jon?
Sorry, I was unaware that it was common practice to announce this kind of thing. Also, it was very barebones for the first few weeks. In fact, I still think it is minimal. That being said, I'll send email to OE-devel (and/or OE-Core) announcing it properly.
Quoted 4 lines
If you want it to be a base for other ARM-based BSP layers, it should be very well known, well maintained and Yocto-compliant. I see there are multiple sub-layers in meta-arm and there was a recent discussion how to properly separate things in those sub-layers - BSP, Distro and Apps w/o mixing them.
Yes, and per that discussion we removed the distro portion from our layer. We are currently working on CI. So this will be heavily tested and verified on Arm reference platforms (and hopefully others). Also, it's on my TODO list to get this layer Yocto-complaint for the 3.1 release. If anything is lacking, let me know and I'll add it to the list!
Quoted 5 lines
For example, our meta-ti BSP layer has no other dependency besides OE-Core, making it very clean. In order for me to make meta-ti also depend on meta-arm for ATF, OPTEE, etc., I would like it to be up to the quality standards of OE-Core! So, the bar is quite high, but I'm willing to help and work in that direction with you and others.
I appreciate this, and agree that this is only useful if it is of the highest quality. Otherwise, development will fragment and everyone will waste resources doing their own thing.
We are in the process of pulling in recipes from meta-linaro (per their suggestion) for OP-TEE and binary toolchains, and my hope is that this will be a "one stop shop" for all things Arm related.
Thanks,
Jon
Quoted 25 lines
--
DenysQuoted 20 lines
Thanks,
JonQuoted 15 lines
--
DenysQuoted 5 lines
Quoted 4 lines
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Quoted 7 lines
Quoted 4 lines
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
It hasn't been there that long, and I was talking to Jon about it at the various conferences late last year, otherwise, I wouldn't have known either.
Quoted 9 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Sounds like a good plan.
Cheers,
Bruce
Quoted 89 lines
--
DenysQuoted 84 lines
Quoted 71 lines
Signed-off-by Denys Dmytriyenko <[email protected]>Cc Joshua Watt <[email protected]>--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bbmeta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55
-1@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot" --2.7.4
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 16 lines · Bruce Ashfield
Quoted 14 lines · Denys Dmytriyenko
Quoted 12 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
It hasn't been there that long, and I was talking to Jon about it at the various conferences late last year, otherwise, I wouldn't have known either.
Getting this meta layer and recipe took longer than I was expecting. So, I've been talking about it for months in anticipation of it coming out, but it was only properly public at the beginning of this month. So, not that it is, I can start badgering people to start using it instead of recreating the wheel. :)
Thanks,
Jon
Quoted 118 lines
Quoted 10 lines
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
Sounds like a good plan.
Cheers,
Bruce
Quoted 89 lines
--
DenysQuoted 84 lines
Quoted 71 lines
Signed-off-by Denys Dmytriyenko <[email protected]>Cc Joshua Watt <[email protected]>--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bbmeta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55
-1@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot" --2.7.4
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
_______________________________________________
Openembedded-core mailing list [email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 23 lines · Denys Dmytriyenko
Quoted 9 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Quoted 4 lines
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Ah, interesting, somehow I totally missed that one! :)
What triggered this submission is that we have our own variant in meta-ti and Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116
Quoted 4 lines
Quoted 1 line
What's the delta between the two ?
Hmm, that one uses older 2.1 version. Other than that, I'll need to test to see if it's as adaptable and expandable as our more simplistic variants...
These work for the BSPs we have internally, but we are very open to patches to make the recipes better :)
I believe someone inside Arm is working on v2.2 recipes. I don't have anything queued for it. So I'll ask around to verify.
Thanks,
Jon
Quoted 94 lines
--
DenysQuoted 71 lines
Quoted 71 lines
Signed-off-by Denys Dmytriyenko <[email protected]>Cc Joshua Watt <[email protected]>--- .../arm-trusted-firmware_2.2.bb | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bbmeta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb new file +55
-1@@ -0,0 +1,55 @@ +SUMMARY = "ARM Trusted Firmware" +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \ +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \ +It provides implementations of various ARM interface standards such as the \ +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \ +(TBBR) and Secure monitor code." +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html" + +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89" + +inherit deploy + +DEPENDS = "dtc-native openssl-native" + +PACKAGE_ARCH = "${MACHINE_ARCH}" + +S = "${WORKDIR}/git" +B = "${WORKDIR}/build" + +BRANCH = "master" +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}" +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796" + +ATF_BINARY ??= "bl31" +ATF_SUFFIX ??= "bin" +ATF_TARGET ??= "all" + +CFLAGS[unexport] = "1" +LDFLAGS[unexport] = "1" +AS[unexport] = "1" +LD[unexport] = "1" + +do_configure[noexec] = "1" + +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \ + PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}' + +do_compile() { + oe_runmake ${ATF_TARGET} +} + +do_install() { + install -d ${D}/boot + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/ +} + +do_deploy() { + install -d ${DEPLOYDIR} + install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/ +} +addtask deploy before do_build after do_compile + +FILES_${PN} = "/boot" +SYSROOT_DIRS += "/boot" --2.7.4
Quoted 13 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 9 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Quoted 6 lines
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
What's the delta between the two ?
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
Ross
Quoted 13 lines · Ross Burton
Quoted 12 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
Quoted 8 lines
Quoted 3 lines
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
What's the delta between the two ?
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
Such as all the various cortex etc CPU tuning files?
Quoted 16 lines · Andre McCurdy
Quoted 15 lines · Ross Burton
Quoted 14 lines · Bruce Ashfield
Quoted 7 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A). To avoid duplicating efforts of adding very similar recipes to BSP layers, add an upstream reference implementation to openembedded-core, which can be customized by BSPs, if needed.
Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
What's the delta between the two ?
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we should move everything that is not needed by qemux86 to meta-intel... JK :)
Signature · 1 line
Denys
Quoted 4 lines · Denys Dmytriyenko
Quoted 1 line
Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we should move everything that is not needed by qemux86 to meta-intel... JK :)
I almost pre-empted this comment in my reply because I knew it was coming. :)
Personally, not a terrible idea. The slight difference is that meta-intel is *Intel's* BSP and we don't share stuff like firmware/drivers with AMD.
Ross
Quoted 11 lines · Ross Burton
Quoted 4 lines · Denys Dmytriyenko
Quoted 1 line
Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we should move everything that is not needed by qemux86 to meta-intel... JK :)
I almost pre-empted this comment in my reply because I knew it was coming. :)
Personally, not a terrible idea. The slight difference is that meta-intel is *Intel's* BSP and we don't share stuff like
firmware/driverswith AMD.Ross
it will be good to find what the overlap will be, is it something that BSPs can use with minimum changes, or are we providing a template that will be copied over and housed in form of bbappends or bbs. I am not familiar enough to assess that.
Perhaps it would be good to limit this to arm compatible machines, secondly, there is a point in having it in OE-Core if meta-arm is limiting itself to arm provided BSPs alone. I think it will be good to have a platform supported in core to be able to test it, between qemu and beaglebone, I guess it is not used. Or pehaps it is and we do not use it, so that change would be good to have as well.
Quoted 24 lines · Khem Raj
Quoted 8 lines · Ross Burton
Quoted 6 lines · Denys Dmytriyenko
Quoted 1 line
Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we
should move everything that is not needed by qemux86 to meta-intel... JK :)Quoted 8 lines
I almost pre-empted this comment in my reply because I knew it was coming. :)
Personally, not a terrible idea. The slight difference is that meta-intel is *Intel's* BSP and we don't share stuff like
firmware/driverswith AMD.Ross
it will be good to find what the overlap will be, is it something that BSPs can use with minimum changes, or are we providing a template that will be copied over and housed in form of bbappends or bbs. I am not familiar enough to assess that.
Quoted 6 lines
Perhaps it would be good to limit this to arm compatible machines, secondly, there is a point in having it in OE-Core if meta-arm is limiting itself to arm provided BSPs alone. I think it will be good to have a platform supported in core to be able to test it, between qemu and beaglebone, I guess it is not used. Or pehaps it is and we do not use it, so that change would be good to have as well.
To be clear, we do not want this limited to Arm BSPs. We want this used by everyone, to make this recipe as solid as possible. Also, we hope it encourages everyone to contribute their TF-A source code "up-stream" and use the generic recipe.
Thanks,
Jon
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 16 lines · Khem Raj
Quoted 15 lines · Ross Burton
Quoted 6 lines · Denys Dmytriyenko
Quoted 1 line
Such as all the various cortex etc CPU tuning files?
LOL! :) Of course, since ARM is such an inferior arch to x86. Otherwise we
should move everything that is not needed by qemux86 to meta-intel... JK :)I almost pre-empted this comment in my reply because I knew it was coming. :)
Personally, not a terrible idea. The slight difference is that meta-intel is *Intel's* BSP and we don't share stuff like
firmware/driverswith AMD.
Quoted 6 lines
Quoted 1 line
Ross
it will be good to find what the overlap will be, is it something that BSPs can use with minimum changes, or are we providing a template that will be copied over and housed in form of bbappends or bbs. I am not familiar enough to assess that.
It depends how much of a specific platform support was already upstreamed to ATF. For example, full TI platform support requires a more recent version that 2.2 release (plus some "linkage" to OPTEE). And based on meta-rockchip submission from Joshua, RK3399 requires a secondary Cortex-M toolchain to build some parts. So, it seems like it would require some bbappends in BSPs.
Quoted 6 lines
Perhaps it would be good to limit this to arm compatible machines, secondly, there is a point in having it in OE-Core if meta-arm is limiting itself to arm provided BSPs alone. I think it will be good to have a platform supported in core to be able to test it, between qemu and beaglebone, I guess it is not used. Or pehaps it is and we do not use it, so that change would be good to have as well.
Well, beaglebone is arm32. From the Yocto Project perspective, we don't have an arm64 reference platform (membership questions, etc.), which would require ATF.
Signature · 1 line
Denys
Quoted 16 lines · Ross Burton
Quoted 15 lines · Bruce Ashfield
Quoted 9 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A).
To avoid duplicating efforts of adding very similar recipes to BSP layers,
add an upstream reference implementation to openembedded-core, which can be
customized by BSPs, if needed.Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
Quoted 8 lines
Quoted 3 lines
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
What's the delta between the two ?
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
If its needed by many platforms, I'm not adverse to it being in core so I have an open mind on core vs. meta-arm. I'm waiting to see what Jon's thoughts are on that.
Cheers,
Richard
Quoted 22 lines · Richard Purdie
Quoted 20 lines · Ross Burton
Quoted 18 lines · Bruce Ashfield
Quoted 9 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A).
To avoid duplicating efforts of adding very similar recipes to BSP layers,
add an upstream reference implementation to openembedded-core, which can be
customized by BSPs, if needed.Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
What's the delta between the two ?
Quoted 8 lines
Quoted 4 lines
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
If its needed by many platforms, I'm not adverse to it being in core so I have an open mind on core vs. meta-arm. I'm waiting to see what Jon's thoughts are on that.
My thought was that unless it's needed by qemuarm, etc, it would remain in meta-arm. We're going to have other desirable recipes (e.g., edk2) in the near future. So, this layer would be useful for all Arm BSPs.
Thanks,
Jon
Quoted 10 lines
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 20 lines · Ross Burton
Quoted 19 lines · Bruce Ashfield
Quoted 10 lines · Denys Dmytriyenko
From: Denys Dmytriyenko <[email protected]>
Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A).
To avoid duplicating efforts of adding very similar recipes to BSP layers,
add an upstream reference implementation to openembedded-core, which can be
customized by BSPs, if needed.Isn't this one of the things that Jon Mason is trying to standardize/support in meta-arm ?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a
Quoted 6 lines
Quoted 1 line
What's the delta between the two ?
That was precisely my thought too. meta-arm isn't exactly well known right now, but ideally it should be a central place for common pieces that are specific to ARM hardware (unlike anything that is needed for qemuarm itself).
Per meta-arm's README:
|meta-arm:
This layer provides support for general recipes for the Arm architecture. Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.
So does that package belong in meta-arm based on what Arm is trying to do?
- armin
|
Quoted 1 line
Ross