Re: [yocto] [PATCH 1/1] Support for .dtbo files for dtb overlays
That patch is ok, however you should have not changed the formatting. So please
send a v2 with original formatting
preserved.
> On May 13, 2016, at 11:47 PM, Herve Jourdain wrote:
>
> Signed-off-by: Herve Jourdain
> ---
> meta/recipes-kernel/linux/linux-dtb.inc | 66 +
> 1 file changed, 35 insertions(+), 31 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc
> b/meta/recipes-kernel/linux/linux-dtb.inc
> index 651a19e..44782d8 100644
> --- a/meta/recipes-kernel/linux/linux-dtb.inc
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -31,44 +31,48 @@ do_compile_append() {
> }
>
> do_install_append() {
> - for DTB in ${KERNEL_DEVICETREE}; do
> - DTB=`normalize_dtb "${DTB}"`
> - DTB_BASE_NAME=`basename ${DTB} .dtb`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> - install -m 0644 ${DTB_PATH}
> ${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
> - done
> +for DTB in ${KERNEL_DEVICETREE}; do
> +DTB=`normalize_dtb "${DTB}"`
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> +install -m 0644 ${DTB_PATH}
> ${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT}
> +done
> }
>
> do_deploy_append() {
> - for DTB in ${KERNEL_DEVICETREE}; do
> - DTB=`normalize_dtb "${DTB}"`
> - DTB_BASE_NAME=`basename ${DTB} .dtb`
> - DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> - install -d ${DEPLOYDIR}
> - install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
> - ln -sf ${DTB_NAME}.dtb ${DEPLOYDIR}/${DTB_SYMLINK_NAME}.dtb
> - done
> +for DTB in ${KERNEL_DEVICETREE}; do
> +DTB=`normalize_dtb "${DTB}"`
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
> +DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> +install -d ${DEPLOYDIR}
> +install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.${DTB_EXT}
> +ln -sf ${DTB_NAME}.${DTB_EXT}
> ${DEPLOYDIR}/${DTB_SYMLINK_NAME}.${DTB_EXT}
> +done
> }
>
> pkg_postinst_kernel-devicetree () {
> - cd /${KERNEL_IMAGEDEST}
> - for DTB in ${KERNEL_DEVICETREE}
> - do
> - DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - update-alternatives --install
> /${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.dtb ${DTB_BASE_NAME}.dtb
> /boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
> - done
> +cd /${KERNEL_IMAGEDEST}
> +for DTB in ${KERNEL_DEVICETREE}
> +do
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +update-alternatives --install
> /${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT}
> /boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
> +done
> }
>
> pkg_postrm_kernel-devicetree () {
> - cd /${KERNEL_IMAGEDEST}
> - for DTB in ${KERNEL_DEVICETREE}
> - do
> - DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - update-alternatives --remove ${DTB_BASE_NAME}.dtb
> /boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
> - done
> +cd /${KERNEL_IMAGEDEST}
> +for DTB in ${KERNEL_DEVICETREE}
> +do
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
> "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +update-alternatives --remove ${DTB_BASE_NAME}.${DTB_EXT}
> /boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
> +done
> }
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
signature.asc
Description: Message signed with OpenPGP using G
Re: [yocto] [PATCH 1/1] Support for .dtbo files for dtb overlays
Hi Khem,
OK, sorry for that.
V2 is coming.
Cheers,
Herve
-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: samedi 14 mai 2016 09:15
To: Herve Jourdain
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [PATCH 1/1] Support for .dtbo files for dtb overlays
That patch is ok, however you should have not changed the formatting. So
please send a v2 with original formatting preserved.
> On May 13, 2016, at 11:47 PM, Herve Jourdain
wrote:
>
> Signed-off-by: Herve Jourdain
> ---
> meta/recipes-kernel/linux/linux-dtb.inc | 66
> +
> 1 file changed, 35 insertions(+), 31 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc
> b/meta/recipes-kernel/linux/linux-dtb.inc
> index 651a19e..44782d8 100644
> --- a/meta/recipes-kernel/linux/linux-dtb.inc
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -31,44 +31,48 @@ do_compile_append() { }
>
> do_install_append() {
> - for DTB in ${KERNEL_DEVICETREE}; do
> - DTB=`normalize_dtb "${DTB}"`
> - DTB_BASE_NAME=`basename ${DTB} .dtb`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> - install -m 0644 ${DTB_PATH}
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
> - done
> +for DTB in ${KERNEL_DEVICETREE}; do
> +DTB=`normalize_dtb "${DTB}"`
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> +install -m 0644 ${DTB_PATH}
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT}
> +done
> }
>
> do_deploy_append() {
> - for DTB in ${KERNEL_DEVICETREE}; do
> - DTB=`normalize_dtb "${DTB}"`
> - DTB_BASE_NAME=`basename ${DTB} .dtb`
> - DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> - install -d ${DEPLOYDIR}
> - install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
> - ln -sf ${DTB_NAME}.dtb ${DEPLOYDIR}/${DTB_SYMLINK_NAME}.dtb
> - done
> +for DTB in ${KERNEL_DEVICETREE}; do
> +DTB=`normalize_dtb "${DTB}"`
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} ".${DTB_EXT}"`
> +DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
> +install -d ${DEPLOYDIR}
> +install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.${DTB_EXT}
> +ln -sf ${DTB_NAME}.${DTB_EXT}
${DEPLOYDIR}/${DTB_SYMLINK_NAME}.${DTB_EXT}
> +done
> }
>
> pkg_postinst_kernel-devicetree () {
> - cd /${KERNEL_IMAGEDEST}
> - for DTB in ${KERNEL_DEVICETREE}
> - do
> - DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - update-alternatives --install
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.dtb ${DTB_BASE_NAME}.dtb
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
> - done
> +cd /${KERNEL_IMAGEDEST}
> +for DTB in ${KERNEL_DEVICETREE}
> +do
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +update-alternatives --install
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT}
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
> +done
> }
>
> pkg_postrm_kernel-devicetree () {
> - cd /${KERNEL_IMAGEDEST}
> - for DTB in ${KERNEL_DEVICETREE}
> - do
> - DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> - DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> - update-alternatives --remove ${DTB_BASE_NAME}.dtb
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
> - done
> +cd /${KERNEL_IMAGEDEST}
> +for DTB in ${KERNEL_DEVICETREE}
> +do
> +DTB_EXT=${DTB##*.}
> +DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
> +DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
> +update-alternatives --remove ${DTB_BASE_NAME}.${DTB_EXT}
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
> +done
> }
>
[yocto] [PATCH v2 0/1] Support for .dtbo files for dtb overlays
Recent kernels tend to use .dtbo files for device tree overlays, instead of .dtb before. .dtb are still used, but only for the "real" device trees (not the overlays). On some platforms (meta-raspberrypi for instance), recent firmware only loads .dtbo files for overlays. This patch tries to address this issue, while not breaking support for .dtb overlays. It allows the installation/deployment of both .dtb and .dtbo files, for device trees and overlays. This is in line with the behavior of kernels 4.4.6+ Herve Jourdain (1): Support for .dtbo files for dtb overlays meta/recipes-kernel/linux/linux-dtb.inc | 66 + 1 file changed, 35 insertions(+), 31 deletions(-) -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 1/1] Support for .dtbo files for dtb overlays
Signed-off-by: Herve Jourdain
---
meta/recipes-kernel/linux/linux-dtb.inc | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-dtb.inc
b/meta/recipes-kernel/linux/linux-dtb.inc
index 651a19e..ee60b6d 100644
--- a/meta/recipes-kernel/linux/linux-dtb.inc
+++ b/meta/recipes-kernel/linux/linux-dtb.inc
@@ -33,23 +33,25 @@ do_compile_append() {
do_install_append() {
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
- DTB_BASE_NAME=`basename ${DTB} .dtb`
+ DTB_EXT=${DTB##*.}
+ DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
- install -m 0644 ${DTB_PATH}
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
+ install -m 0644 ${DTB_PATH}
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT}
done
}
do_deploy_append() {
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
- DTB_BASE_NAME=`basename ${DTB} .dtb`
+ DTB_EXT=${DTB##*.}
+ DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
install -d ${DEPLOYDIR}
- install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
- ln -sf ${DTB_NAME}.dtb ${DEPLOYDIR}/${DTB_SYMLINK_NAME}.dtb
+ install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.${DTB_EXT}
+ ln -sf ${DTB_NAME}.${DTB_EXT}
${DEPLOYDIR}/${DTB_SYMLINK_NAME}.${DTB_EXT}
done
}
@@ -57,9 +59,10 @@ pkg_postinst_kernel-devicetree () {
cd /${KERNEL_IMAGEDEST}
for DTB in ${KERNEL_DEVICETREE}
do
+ DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
- update-alternatives --install
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.dtb ${DTB_BASE_NAME}.dtb
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
+ update-alternatives --install
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT}
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
done
}
@@ -67,8 +70,9 @@ pkg_postrm_kernel-devicetree () {
cd /${KERNEL_IMAGEDEST}
for DTB in ${KERNEL_DEVICETREE}
do
+ DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print $1}'`
DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
- update-alternatives --remove ${DTB_BASE_NAME}.dtb
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
+ update-alternatives --remove ${DTB_BASE_NAME}.${DTB_EXT}
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
done
}
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH v2 0/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12
Please disregard v1, there was 1 patch missing for 4.4 kernel... The firmware after 2016/04/12 () seems to have altered the behavior of device tree loading on RaspberryPi: for overlays, it loads only .dtbo files, not .dtb anymore. Also, it does not check for -overlay extension, so the name of the overlay that is placed in the "overlays" directory must be .dtbo, instead of -overlay.dtb. This patch tries to address this issue for 4.4 and 4.1 kernels. It must be used in conjunction with another patch to meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo files, instead of only .dtb. .dtb are still used, but only for the "real" device trees (not the overlays). This is in line with the behavior of kernels 4.4.6+ Herve Jourdain (1): Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12 classes/linux-raspberrypi-base.bbclass | 4 +-- classes/sdcard_image-rpi.bbclass | 6 ++-- conf/machine/include/rpi-base.inc | 30 +-- .../0002-fix-dtbo-rules.patch | 35 ++ .../0001-fix-dtbo-rules.patch | 13 recipes-kernel/linux/linux-raspberrypi_4.1.bb | 1 + recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 + 7 files changed, 70 insertions(+), 20 deletions(-) create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch create mode 100644 recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH v2 1/1] Support for .dtbo files for dtb overlays, required by firmware after 2016/04/12
Signed-off-by: Herve Jourdain
---
classes/linux-raspberrypi-base.bbclass | 4 +--
classes/sdcard_image-rpi.bbclass | 6 ++--
conf/machine/include/rpi-base.inc | 30 +--
.../0002-fix-dtbo-rules.patch | 35 ++
.../0001-fix-dtbo-rules.patch | 27 +
recipes-kernel/linux/linux-raspberrypi_4.1.bb | 1 +
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
7 files changed, 84 insertions(+), 20 deletions(-)
create mode 100644
recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
create mode 100644
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
diff --git a/classes/linux-raspberrypi-base.bbclass
b/classes/linux-raspberrypi-base.bbclass
index 40beef1..f2f0a5a 100644
--- a/classes/linux-raspberrypi-base.bbclass
+++ b/classes/linux-raspberrypi-base.bbclass
@@ -32,8 +32,8 @@ def get_dts(d, ver):
def split_overlays(d, out):
dts = get_dts(d, None)
if out:
-overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter_out('\S+\.dtbo$', dts, d)
else:
-overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter('\S+\.dtbo$', dts, d)
return overlays
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 4dfd7a3..e510ce0 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -110,7 +110,7 @@ IMAGE_CMD_rpi-sdimg () {
;;
*)
if test -n "${DTS}"; then
- # Device Tree Overlays are assumed to be suffixed by
'-overlay.dtb' string and will be put in a dedicated folder
+ # Device Tree Overlays are assumed to be suffixed by
'.dtbo' string and will be put in a dedicated folder
DT_OVERLAYS="${@split_overlays(d, 0)}"
DT_ROOT="${@split_overlays(d, 1)}"
@@ -124,9 +124,9 @@ IMAGE_CMD_rpi-sdimg () {
# Copy device tree overlays to dedicated folder
mmd -i ${WORKDIR}/boot.img overlays
for DTB in ${DT_OVERLAYS}; do
- DTB_BASE_NAME=`basename ${DTB} .dtb`
+ DTB_BASE_NAME=`basename ${DTB} ".dtbo"`
- mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb
::overlays/${DTB_BASE_NAME}.dtb
+ mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtbo
::overlays/${DTB_BASE_NAME}.dtbo
done
fi
mcopy -i ${WORKDIR}/boot.img -s
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin
::${SDIMG_KERNELIMAGE}
diff --git a/conf/machine/include/rpi-base.inc
b/conf/machine/include/rpi-base.inc
index 56ca83e..47eb23b 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -22,21 +22,21 @@ KERNEL_DEVICETREE ?= " \
bcm2709-rpi-2-b.dtb \
bcm2710-rpi-3-b.dtb \
\
-overlays/hifiberry-amp-overlay.dtb \
-overlays/hifiberry-dac-overlay.dtb \
-overlays/hifiberry-dacplus-overlay.dtb \
-overlays/hifiberry-digi-overlay.dtb \
-overlays/i2c-rtc-overlay.dtb \
-overlays/iqaudio-dac-overlay.dtb \
-overlays/iqaudio-dacplus-overlay.dtb \
-overlays/lirc-rpi-overlay.dtb \
-overlays/pitft22-overlay.dtb \
-overlays/pitft28-resistive-overlay.dtb \
-overlays/pps-gpio-overlay.dtb \
-overlays/rpi-ft5406-overlay.dtb \
-overlays/w1-gpio-overlay.dtb \
-overlays/w1-gpio-pullup-overlay.dtb \
-overlays/pi3-miniuart-bt-overlay.dtb \
+overlays/hifiberry-amp.dtbo \
+overlays/hifiberry-dac.dtbo \
+overlays/hifiberry-dacplus.dtbo \
+overlays/hifiberry-digi.dtbo \
+overlays/i2c-rtc.dtbo \
+overlays/iqaudio-dac.dtbo \
+overlays/iqaudio-dacplus.dtbo \
+overlays/lirc-rpi.dtbo \
+overlays/pitft22.dtbo \
+overlays/pitft28-resistive.dtbo \
+overlays/pps-gpio.dtbo \
+overlays/rpi-ft5406.dtbo \
+overlays/w1-gpio.dtbo \
+overlays/w1-gpio-pullup.dtbo \
+overlays/pi3-miniuart-bt.dtbo \
"
KERNEL_IMAGETYPE ?= "Image"
diff --git
a/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
new file mode 100644
index 000..25564c2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.1/0002-fix-dtbo-rules.patch
@@ -0,0 +1,35 @@
+diff --git a/arch/arm/Makefile b/arch/arm/Makefile
+index afd559d..06819fd 100644
+--- a/arch/arm/Makefile
b/arch/arm/Makefile
+@@ -322,6 +322,8 @@ $(INSTALL_TARGETS):
+
+ %.dtb: | scripts
+ $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++%.dtbo:
[yocto] [meta-cgl][PATCH] CGL recipes compliance calculator first draft
From: Sanziana Voicu
Signed-off-by: Sanziana Voicu
---
meta-cgl-common/classes/cgl-calc.bbclass | 21
.../recipes-cgl/corosync/corosync_1.4.7.bb | 7 +-
.../recipes-cgl/pacemaker/pacemaker_1.1.13.bb | 7 +-
scripts/script.py | 117 +
4 files changed, 150 insertions(+), 2 deletions(-)
create mode 100644 meta-cgl-common/classes/cgl-calc.bbclass
create mode 100755 scripts/script.py
diff --git a/meta-cgl-common/classes/cgl-calc.bbclass
b/meta-cgl-common/classes/cgl-calc.bbclass
new file mode 100644
index 000..81660d6
--- /dev/null
+++ b/meta-cgl-common/classes/cgl-calc.bbclass
@@ -0,0 +1,21 @@
+
+do_cgl_calc() {
+ NO_COMPLY="NO"
+ if [ -z "${CGL_ID}" ]; then
+ echo "${NO_COMPLY}" > calculator.txt
+ else
+ echo "${CGL_ID}" > calculator.txt
+ fi
+ if [ -z "${PRIORITY}" ]; then
+ echo "${NO_COMPLY}" >> calculator.txt
+ else
+ echo "${PRIORITY}" >> calculator.txt
+ fi
+ if [ -z "${DISCLOSURE}" ]; then
+ echo "${NO_COMPLY}" >> calculator.txt
+ else
+ echo "${DISCLOSURE}" >> calculator.txt
+ fi
+}
+
+addtask cgl_calc after do_fetch before do_build
diff --git a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
index 019a2f4..98b75e6 100644
--- a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
+++ b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
@@ -4,7 +4,7 @@ several default APIs and libraries, default configuration
files, and an init \
script."
HOMEPAGE = "http://corosync.github.io/corosync/";
-inherit autotools pkgconfig update-rc.d useradd
+inherit autotools pkgconfig update-rc.d useradd cgl-calc
SRC_URI = "http://build.clusterlabs.org/corosync/releases/${BPN}-${PV}.tar.gz \
file://groff-desc-path.patch \
@@ -58,3 +58,8 @@ USERADD_PACKAGES = "${PN}"
GROUPADD_PARAM_${PN} = "haclient"
USERADD_PARAM_${PN} = "-M --home ${localstatedir}/lib/heartbeat -g haclient
hacluster"
+CGL_ID="CFH.2.0,CCM.2.2"
+PRIORITY="P1,P1"
+DISCLOSURE="${PN},${PN}"
+
+
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
index d2e2395..84c8c84 100755
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
@@ -26,7 +26,7 @@ SRC_URI =
"https://github.com/ClusterLabs/${PN}/archive/Pacemaker-${PV}.zip \
SRC_URI[md5sum] = "d84a5173306727a981a4f87e36007595"
SRC_URI[sha256sum] =
"e963bc59a5d98a3e3441ea5cccb42aa67f9d7934b80c8818e19ae91c5da48331"
-inherit autotools-brokensep pkgconfig systemd python-dir useradd
+inherit autotools-brokensep pkgconfig systemd python-dir useradd cgl-calc
S="${WORKDIR}/pacemaker-Pacemaker-${PV}"
@@ -90,3 +90,8 @@ SYSTEMD_SERVICE_${PN}-remote += "pacemaker_remote.service"
USERADD_PACKAGES = "${PN}"
USERADD_PARAM_${PN} = "-r -g haclient -s ${base_sbindir}/nologin hacluster"
GROUPADD_PARAM_${PN} = "-r haclient"
+
+CGL_ID="AVL.25.0,CAF.2.1,CAF.2.2"
+PRIORITY="P1,P1,P1"
+DISCLOSURE="${PN},${PN},${PN}"
+
diff --git a/scripts/script.py b/scripts/script.py
new file mode 100755
index 000..e033fa4
--- /dev/null
+++ b/scripts/script.py
@@ -0,0 +1,117 @@
+#!/usr/bin/python
+
+import os, sys
+
+# The value represents the total number of P! requirements available
+# inside the CGL 5.0 template
+p1_reqs = 113
+files_no = 0
+cnt = 0
+nr = 0
+
+def compliance_calc(reqs_len):
+ number_p1=0;
+ for i in range(0,reqs_len):
+ number_p1=number_p1+1
+ procent=float(number_p1)/p1_reqs*100.
+ print "CGL compliance: %.2f%%" % procent
+
+build_dir = os.environ.get('BUILDDIR')
+if not build_dir:
+ print "Source the build environment before executing this script!"
+ sys.exit(1)
+director = build_dir + "/tmp/work"
+
+def populate_compl(content, files):
+ temp = content.split('\n')
+ global cnt
+
+ for j in range(0, len(temp[0].split(",")) ):
+ ID[cnt] = temp[0].split(",")[j]
+ P[cnt] = temp[1].split(",")[j]
+ D[cnt] = temp[2].split(",")[j]
+
+ if ID[cnt].split('.')[0] == "AVL":
+ shadow[cnt]=1
+ if ID[cnt].split('.')[0] == "CFH":
+ shadow[cnt]=2
+ if ID[cnt].split('.')[0] == "CSM":
+ shadow[cnt]=3
+ if ID[cnt].split('.')[0] == "CCM":
+ shadow[cnt]=4
+ if ID[cnt].split('.')[0] == "CAF":
+ shadow[cnt]=5
+ if ID[cnt].split('.')[0] == "CDIAG":
+ shadow[cnt]=6
+ if ID[cnt].split('.')[0] == "SMM":
+ shadow[cnt]=7
+ if ID[cnt].split('.')[0] == "SPM":
+
[yocto] [meta-cgl][PATCH] CGL recipes compliance calculator first draft
From: Sanziana Voicu
Signed-off-by: Sanziana Voicu
---
meta-cgl-common/classes/cgl-calc.bbclass | 21
.../recipes-cgl/corosync/corosync_1.4.7.bb | 7 +-
.../recipes-cgl/pacemaker/pacemaker_1.1.13.bb | 7 +-
scripts/script.py | 117 +
4 files changed, 150 insertions(+), 2 deletions(-)
create mode 100644 meta-cgl-common/classes/cgl-calc.bbclass
create mode 100755 scripts/script.py
diff --git a/meta-cgl-common/classes/cgl-calc.bbclass
b/meta-cgl-common/classes/cgl-calc.bbclass
new file mode 100644
index 000..81660d6
--- /dev/null
+++ b/meta-cgl-common/classes/cgl-calc.bbclass
@@ -0,0 +1,21 @@
+
+do_cgl_calc() {
+ NO_COMPLY="NO"
+ if [ -z "${CGL_ID}" ]; then
+ echo "${NO_COMPLY}" > calculator.txt
+ else
+ echo "${CGL_ID}" > calculator.txt
+ fi
+ if [ -z "${PRIORITY}" ]; then
+ echo "${NO_COMPLY}" >> calculator.txt
+ else
+ echo "${PRIORITY}" >> calculator.txt
+ fi
+ if [ -z "${DISCLOSURE}" ]; then
+ echo "${NO_COMPLY}" >> calculator.txt
+ else
+ echo "${DISCLOSURE}" >> calculator.txt
+ fi
+}
+
+addtask cgl_calc after do_fetch before do_build
diff --git a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
index 019a2f4..98b75e6 100644
--- a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
+++ b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
@@ -4,7 +4,7 @@ several default APIs and libraries, default configuration
files, and an init \
script."
HOMEPAGE = "http://corosync.github.io/corosync/";
-inherit autotools pkgconfig update-rc.d useradd
+inherit autotools pkgconfig update-rc.d useradd cgl-calc
SRC_URI = "http://build.clusterlabs.org/corosync/releases/${BPN}-${PV}.tar.gz \
file://groff-desc-path.patch \
@@ -58,3 +58,8 @@ USERADD_PACKAGES = "${PN}"
GROUPADD_PARAM_${PN} = "haclient"
USERADD_PARAM_${PN} = "-M --home ${localstatedir}/lib/heartbeat -g haclient
hacluster"
+CGL_ID="CFH.2.0,CCM.2.2"
+PRIORITY="P1,P1"
+DISCLOSURE="${PN},${PN}"
+
+
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
index d2e2395..84c8c84 100755
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
@@ -26,7 +26,7 @@ SRC_URI =
"https://github.com/ClusterLabs/${PN}/archive/Pacemaker-${PV}.zip \
SRC_URI[md5sum] = "d84a5173306727a981a4f87e36007595"
SRC_URI[sha256sum] =
"e963bc59a5d98a3e3441ea5cccb42aa67f9d7934b80c8818e19ae91c5da48331"
-inherit autotools-brokensep pkgconfig systemd python-dir useradd
+inherit autotools-brokensep pkgconfig systemd python-dir useradd cgl-calc
S="${WORKDIR}/pacemaker-Pacemaker-${PV}"
@@ -90,3 +90,8 @@ SYSTEMD_SERVICE_${PN}-remote += "pacemaker_remote.service"
USERADD_PACKAGES = "${PN}"
USERADD_PARAM_${PN} = "-r -g haclient -s ${base_sbindir}/nologin hacluster"
GROUPADD_PARAM_${PN} = "-r haclient"
+
+CGL_ID="AVL.25.0,CAF.2.1,CAF.2.2"
+PRIORITY="P1,P1,P1"
+DISCLOSURE="${PN},${PN},${PN}"
+
diff --git a/scripts/script.py b/scripts/script.py
new file mode 100755
index 000..e033fa4
--- /dev/null
+++ b/scripts/script.py
@@ -0,0 +1,117 @@
+#!/usr/bin/python
+
+import os, sys
+
+# The value represents the total number of P! requirements available
+# inside the CGL 5.0 template
+p1_reqs = 113
+files_no = 0
+cnt = 0
+nr = 0
+
+def compliance_calc(reqs_len):
+ number_p1=0;
+ for i in range(0,reqs_len):
+ number_p1=number_p1+1
+ procent=float(number_p1)/p1_reqs*100.
+ print "CGL compliance: %.2f%%" % procent
+
+build_dir = os.environ.get('BUILDDIR')
+if not build_dir:
+ print "Source the build environment before executing this script!"
+ sys.exit(1)
+director = build_dir + "/tmp/work"
+
+def populate_compl(content, files):
+ temp = content.split('\n')
+ global cnt
+
+ for j in range(0, len(temp[0].split(",")) ):
+ ID[cnt] = temp[0].split(",")[j]
+ P[cnt] = temp[1].split(",")[j]
+ D[cnt] = temp[2].split(",")[j]
+
+ if ID[cnt].split('.')[0] == "AVL":
+ shadow[cnt]=1
+ if ID[cnt].split('.')[0] == "CFH":
+ shadow[cnt]=2
+ if ID[cnt].split('.')[0] == "CSM":
+ shadow[cnt]=3
+ if ID[cnt].split('.')[0] == "CCM":
+ shadow[cnt]=4
+ if ID[cnt].split('.')[0] == "CAF":
+ shadow[cnt]=5
+ if ID[cnt].split('.')[0] == "CDIAG":
+ shadow[cnt]=6
+ if ID[cnt].split('.')[0] == "SMM":
+ shadow[cnt]=7
+ if ID[cnt].split('.')[0] == "SPM":
+
[yocto] Error in spec file (bad %description of dev package)
Hello, I have a packaging problem with the new share lib recipe I try to make. When I bitbake the recipe I get the correct package split : # tree . |-- libtime64 | `-- usr | `-- lib | |-- libtime64.so.1 -> /home/ ... /libtime64/1.0.1-r0/image/usr/lib/libtime64.so.1.0.1 | `-- libtime64.so.1.0.1 |-- libtime64-dbg | `-- usr | |-- lib | `-- src | `-- debug | `-- libtime64 | `-- 1.0.1-r0 | `-- libtime64-1.0.1 | |-- inc | | `-- time64.h | `-- src | `-- time64.c |-- libtime64-dev | `-- usr | |-- include | | |-- axt_2038.h | | `-- time64.h | `-- lib | `-- libtime64.so -> /home/ ... /libtime64/1.0.1-r0/image/usr/lib/libtime64.so.1 |-- libtime64-doc |-- libtime64-locale |-- libtime64-staticdev `-- libtime64.shlibdeps I include "libtime64" in IMAGE_INSTALL but only the main package and the dbg package are produced and the main package contain the content of the dev package. - libtime64-1-1.0.1-r0.cortexa9hf_vfp_neon.rpm - libtime64-dbg-1.0.1-r0.cortexa9hf_vfp_neon.rpm I found an error in the spec file for the dev package, the %package and %description are misnamed. Below an extract of the spec file: ** %package -n libtime64-1 Summary: Time64 library (support 2038 patch) - Development files Group: devel Requires: libtime64-1 = 1.0.1-r0 Suggests: libc6-dev Provides: libtime64-dev %description -n libtime64-1 Time64 library (support 2038 patch). This package contains symbolic links, header files, and related items necessary for software development. ... %files -n libtime64-1 %defattr(-,-,-,-) %dir "/usr" %dir "/usr/lib" %dir "/usr/include" "/usr/lib/libtime64.so" "/usr/include/axt_2038.h" "/usr/include/time64.h" %files -n libtime64-1 %defattr(-,-,-,-) %dir "/usr" %dir "/usr/lib" "/usr/lib/libtime64.so.1.0.1" "/usr/lib/libtime64.so.1" ** I use Yocto Dizzy on a ubuntu 14.04. Someone already see this problem ? Any idea to solve it ? thanks Jonathan Poulin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error in spec file (bad %description of dev package)
On Sat, May 14, 2016 at 6:40 AM, Jonathan Poulin wrote: > Hello, > > I have a packaging problem with the new share lib recipe I try to make. When > I bitbake the recipe I get the correct package split : > > # tree > . > |-- libtime64 > | `-- usr > | `-- lib > | |-- libtime64.so.1 -> /home/ ... > /libtime64/1.0.1-r0/image/usr/lib/libtime64.so.1.0.1 > | `-- libtime64.so.1.0.1 > |-- libtime64-dbg > | `-- usr > | |-- lib > | `-- src > | `-- debug > | `-- libtime64 > | `-- 1.0.1-r0 > | `-- libtime64-1.0.1 > | |-- inc > | | `-- time64.h > | `-- src > | `-- time64.c > |-- libtime64-dev > | `-- usr > | |-- include > | | |-- axt_2038.h > | | `-- time64.h > | `-- lib > | `-- libtime64.so -> /home/ ... > /libtime64/1.0.1-r0/image/usr/lib/libtime64.so.1 > |-- libtime64-doc > |-- libtime64-locale > |-- libtime64-staticdev > `-- libtime64.shlibdeps > > > I include "libtime64" in IMAGE_INSTALL but only the main package and the dbg > package are produced and the main package contain the content of the dev > package. > - libtime64-1-1.0.1-r0.cortexa9hf_vfp_neon.rpm > - libtime64-dbg-1.0.1-r0.cortexa9hf_vfp_neon.rpm > > I found an error in the spec file for the dev package, the %package and > %description are misnamed. Below an extract of the spec file: > > ** > %package -n libtime64-1 > Summary: Time64 library (support 2038 patch) - Development files > Group: devel > Requires: libtime64-1 = 1.0.1-r0 > Suggests: libc6-dev > Provides: libtime64-dev > > %description -n libtime64-1 > Time64 library (support 2038 patch). This package contains symbolic links, > header files, and related items necessary for software development. > > ... > > %files -n libtime64-1 > %defattr(-,-,-,-) > %dir "/usr" > %dir "/usr/lib" > %dir "/usr/include" > "/usr/lib/libtime64.so" > "/usr/include/axt_2038.h" > "/usr/include/time64.h" > > %files -n libtime64-1 > %defattr(-,-,-,-) > %dir "/usr" > %dir "/usr/lib" > "/usr/lib/libtime64.so.1.0.1" > "/usr/lib/libtime64.so.1" > > ** > > I use Yocto Dizzy on a ubuntu 14.04. > > Someone already see this problem ? Any idea to solve it ? Can you share the recipe for this package ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
What configs do I need to include in my machine.conf to support this processor? http://www.nvidia.com/object/jetson-tx1-dev-kit.html "require conf/machine/include/arm/arch-*.inc" ? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
Look at kraj/meta-jetson-tk1 on github On May 14, 2016 2:17 PM, "Paul Knopf" wrote: > What configs do I need to include in my machine.conf to support this > processor? > > http://www.nvidia.com/object/jetson-tx1-dev-kit.html > > "require conf/machine/include/arm/arch-*.inc" ? > > Thanks, > Paul Knopf > Software Engineer > Med X Change, Inc > pkn...@medxchange.com > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
They are using "require conf/machine/include/tune-cortexa15.inc" for the TK1, but the TX1 uses a Cortex A57, not a A15. There is no "tune-cortexa57". Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:08 PM, Khem Raj wrote: > Look at kraj/meta-jetson-tk1 on github > On May 14, 2016 2:17 PM, "Paul Knopf" wrote: > >> What configs do I need to include in my machine.conf to support this >> processor? >> >> http://www.nvidia.com/object/jetson-tx1-dev-kit.html >> >> "require conf/machine/include/arm/arch-*.inc" ? >> >> Thanks, >> Paul Knopf >> Software Engineer >> Med X Change, Inc >> pkn...@medxchange.com >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
NVideo provides the following crosstools-ng config for building a cross-compile toolchain. https://gist.github.com/anonymous/95b2ec71aebf8df644b1789bc3ed958d Some parts I think that are relevant... - CT_ARCH="arm" CT_ARCH_SUPPORTS_BOTH_MMU=y CT_ARCH_SUPPORTS_BOTH_ENDIAN=y CT_ARCH_SUPPORTS_32=y CT_ARCH_SUPPORTS_WITH_ARCH=y CT_ARCH_SUPPORTS_WITH_CPU=y CT_ARCH_SUPPORTS_WITH_TUNE=y CT_ARCH_SUPPORTS_WITH_FLOAT=y CT_ARCH_SUPPORTS_WITH_FPU=y CT_ARCH_SUPPORTS_SOFTFP=y CT_ARCH_DEFAULT_HAS_MMU=y CT_ARCH_DEFAULT_LE=y CT_ARCH_DEFAULT_32=y CT_ARCH_ARCH="armv7-a" CT_ARCH_CPU="cortex-a9" CT_ARCH_TUNE="cortex-a9" CT_ARCH_FPU="" # CT_ARCH_BE is not set CT_ARCH_LE=y CT_ARCH_32=y CT_ARCH_BITNESS=32 CT_ARCH_FLOAT_HW=y # CT_ARCH_FLOAT_SW is not set CT_TARGET_CFLAGS="" CT_TARGET_LDFLAGS="" # CT_ARCH_alpha is not set CT_ARCH_arm=y # CT_ARCH_avr32 is not set # CT_ARCH_blackfin is not set # CT_ARCH_m68k is not set # CT_ARCH_mips is not set # CT_ARCH_powerpc is not set # CT_ARCH_s390 is not set # CT_ARCH_sh is not set # CT_ARCH_sparc is not set # CT_ARCH_x86 is not set CT_ARCH_alpha_AVAILABLE=y CT_ARCH_arm_AVAILABLE=y CT_ARCH_avr32_AVAILABLE=y CT_ARCH_blackfin_AVAILABLE=y CT_ARCH_m68k_AVAILABLE=y CT_ARCH_mips_AVAILABLE=y CT_ARCH_powerpc_AVAILABLE=y CT_ARCH_s390_AVAILABLE=y CT_ARCH_sh_AVAILABLE=y CT_ARCH_sparc_AVAILABLE=y CT_ARCH_x86_AVAILABLE=y - What files do I need to build with this cross-toolchain, inside of Yocto? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:14 PM, Paul Knopf wrote: > They are using "require conf/machine/include/tune-cortexa15.inc" for the > TK1, but the TX1 uses a Cortex A57, not a A15. There is no "tune-cortexa57". > > Thanks, > Paul Knopf > Software Engineer > Med X Change, Inc > pkn...@medxchange.com > > On Sat, May 14, 2016 at 6:08 PM, Khem Raj wrote: > >> Look at kraj/meta-jetson-tk1 on github >> On May 14, 2016 2:17 PM, "Paul Knopf" wrote: >> >>> What configs do I need to include in my machine.conf to support this >>> processor? >>> >>> http://www.nvidia.com/object/jetson-tx1-dev-kit.html >>> >>> "require conf/machine/include/arm/arch-*.inc" ? >>> >>> Thanks, >>> Paul Knopf >>> Software Engineer >>> Med X Change, Inc >>> pkn...@medxchange.com >>> >>> -- >>> ___ >>> yocto mailing list >>> yocto@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/yocto >>> >>> > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
On Sat, May 14, 2016 at 3:23 PM, Paul Knopf wrote: > NVideo provides the following crosstools-ng config for building a > cross-compile toolchain. > > https://gist.github.com/anonymous/95b2ec71aebf8df644b1789bc3ed958d > with OE it will build everything for you just clone https://github.com/kraj/meta-jetson-tk1 add it to bblayers.conf and then set MACHINE = "jetson-tk1" and bitbake core-image-minimal > Some parts I think that are relevant... > > - > CT_ARCH="arm" > CT_ARCH_SUPPORTS_BOTH_MMU=y > CT_ARCH_SUPPORTS_BOTH_ENDIAN=y > CT_ARCH_SUPPORTS_32=y > CT_ARCH_SUPPORTS_WITH_ARCH=y > CT_ARCH_SUPPORTS_WITH_CPU=y > CT_ARCH_SUPPORTS_WITH_TUNE=y > CT_ARCH_SUPPORTS_WITH_FLOAT=y > CT_ARCH_SUPPORTS_WITH_FPU=y > CT_ARCH_SUPPORTS_SOFTFP=y > CT_ARCH_DEFAULT_HAS_MMU=y > CT_ARCH_DEFAULT_LE=y > CT_ARCH_DEFAULT_32=y > CT_ARCH_ARCH="armv7-a" > CT_ARCH_CPU="cortex-a9" > CT_ARCH_TUNE="cortex-a9" > CT_ARCH_FPU="" > # CT_ARCH_BE is not set > CT_ARCH_LE=y > CT_ARCH_32=y > CT_ARCH_BITNESS=32 > CT_ARCH_FLOAT_HW=y > # CT_ARCH_FLOAT_SW is not set > CT_TARGET_CFLAGS="" > CT_TARGET_LDFLAGS="" > # CT_ARCH_alpha is not set > CT_ARCH_arm=y > # CT_ARCH_avr32 is not set > # CT_ARCH_blackfin is not set > # CT_ARCH_m68k is not set > # CT_ARCH_mips is not set > # CT_ARCH_powerpc is not set > # CT_ARCH_s390 is not set > # CT_ARCH_sh is not set > # CT_ARCH_sparc is not set > # CT_ARCH_x86 is not set > CT_ARCH_alpha_AVAILABLE=y > CT_ARCH_arm_AVAILABLE=y > CT_ARCH_avr32_AVAILABLE=y > CT_ARCH_blackfin_AVAILABLE=y > CT_ARCH_m68k_AVAILABLE=y > CT_ARCH_mips_AVAILABLE=y > CT_ARCH_powerpc_AVAILABLE=y > CT_ARCH_s390_AVAILABLE=y > CT_ARCH_sh_AVAILABLE=y > CT_ARCH_sparc_AVAILABLE=y > CT_ARCH_x86_AVAILABLE=y > - > > What files do I need to build with this cross-toolchain, inside of Yocto? > > > Thanks, > Paul Knopf > Software Engineer > Med X Change, Inc > pkn...@medxchange.com > > On Sat, May 14, 2016 at 6:14 PM, Paul Knopf wrote: >> >> They are using "require conf/machine/include/tune-cortexa15.inc" for the >> TK1, but the TX1 uses a Cortex A57, not a A15. There is no "tune-cortexa57". >> >> Thanks, >> Paul Knopf >> Software Engineer >> Med X Change, Inc >> pkn...@medxchange.com >> >> On Sat, May 14, 2016 at 6:08 PM, Khem Raj wrote: >>> >>> Look at kraj/meta-jetson-tk1 on github >>> >>> On May 14, 2016 2:17 PM, "Paul Knopf" wrote: What configs do I need to include in my machine.conf to support this processor? http://www.nvidia.com/object/jetson-tx1-dev-kit.html "require conf/machine/include/arm/arch-*.inc" ? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto >> > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
That layer is for the tk1, not the tx1. I am asking for the proper include files to build for the tx1. Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:27 PM, Khem Raj wrote: > On Sat, May 14, 2016 at 3:23 PM, Paul Knopf wrote: > > NVideo provides the following crosstools-ng config for building a > > cross-compile toolchain. > > > > https://gist.github.com/anonymous/95b2ec71aebf8df644b1789bc3ed958d > > > > with OE it will build everything for you > just clone > > https://github.com/kraj/meta-jetson-tk1 > > add it to bblayers.conf > and then set MACHINE = "jetson-tk1" > and bitbake core-image-minimal > > > > Some parts I think that are relevant... > > > > - > > CT_ARCH="arm" > > CT_ARCH_SUPPORTS_BOTH_MMU=y > > CT_ARCH_SUPPORTS_BOTH_ENDIAN=y > > CT_ARCH_SUPPORTS_32=y > > CT_ARCH_SUPPORTS_WITH_ARCH=y > > CT_ARCH_SUPPORTS_WITH_CPU=y > > CT_ARCH_SUPPORTS_WITH_TUNE=y > > CT_ARCH_SUPPORTS_WITH_FLOAT=y > > CT_ARCH_SUPPORTS_WITH_FPU=y > > CT_ARCH_SUPPORTS_SOFTFP=y > > CT_ARCH_DEFAULT_HAS_MMU=y > > CT_ARCH_DEFAULT_LE=y > > CT_ARCH_DEFAULT_32=y > > CT_ARCH_ARCH="armv7-a" > > CT_ARCH_CPU="cortex-a9" > > CT_ARCH_TUNE="cortex-a9" > > CT_ARCH_FPU="" > > # CT_ARCH_BE is not set > > CT_ARCH_LE=y > > CT_ARCH_32=y > > CT_ARCH_BITNESS=32 > > CT_ARCH_FLOAT_HW=y > > # CT_ARCH_FLOAT_SW is not set > > CT_TARGET_CFLAGS="" > > CT_TARGET_LDFLAGS="" > > # CT_ARCH_alpha is not set > > CT_ARCH_arm=y > > # CT_ARCH_avr32 is not set > > # CT_ARCH_blackfin is not set > > # CT_ARCH_m68k is not set > > # CT_ARCH_mips is not set > > # CT_ARCH_powerpc is not set > > # CT_ARCH_s390 is not set > > # CT_ARCH_sh is not set > > # CT_ARCH_sparc is not set > > # CT_ARCH_x86 is not set > > CT_ARCH_alpha_AVAILABLE=y > > CT_ARCH_arm_AVAILABLE=y > > CT_ARCH_avr32_AVAILABLE=y > > CT_ARCH_blackfin_AVAILABLE=y > > CT_ARCH_m68k_AVAILABLE=y > > CT_ARCH_mips_AVAILABLE=y > > CT_ARCH_powerpc_AVAILABLE=y > > CT_ARCH_s390_AVAILABLE=y > > CT_ARCH_sh_AVAILABLE=y > > CT_ARCH_sparc_AVAILABLE=y > > CT_ARCH_x86_AVAILABLE=y > > - > > > > What files do I need to build with this cross-toolchain, inside of Yocto? > > > > > > Thanks, > > Paul Knopf > > Software Engineer > > Med X Change, Inc > > pkn...@medxchange.com > > > > On Sat, May 14, 2016 at 6:14 PM, Paul Knopf > wrote: > >> > >> They are using "require conf/machine/include/tune-cortexa15.inc" for the > >> TK1, but the TX1 uses a Cortex A57, not a A15. There is no > "tune-cortexa57". > >> > >> Thanks, > >> Paul Knopf > >> Software Engineer > >> Med X Change, Inc > >> pkn...@medxchange.com > >> > >> On Sat, May 14, 2016 at 6:08 PM, Khem Raj wrote: > >>> > >>> Look at kraj/meta-jetson-tk1 on github > >>> > >>> On May 14, 2016 2:17 PM, "Paul Knopf" wrote: > > What configs do I need to include in my machine.conf to support this > processor? > > http://www.nvidia.com/object/jetson-tx1-dev-kit.html > > "require conf/machine/include/arm/arch-*.inc" ? > > Thanks, > Paul Knopf > Software Engineer > Med X Change, Inc > pkn...@medxchange.com > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > >> > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)
This is what I am thinking. DEFAULTTUNE = "cortexa9hf" require conf/machine/include/tune-cortexa9.inc Does this sound right? I am using "hf" because in the crosstools-ng has CT_ARCH_FLOAT="hard", and cortexa9 because of CT_ARCH_CPU="cortex-a9" and CT_ARCH_TUNE="cortex-a9". Sorry, I'm that familiar with embedded processors. Any guidance would be greatly appreciated. Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:32 PM, Paul Knopf wrote: > That layer is for the tk1, not the tx1. I am asking for the proper include > files to build for the tx1. > > Thanks, > Paul Knopf > Software Engineer > Med X Change, Inc > pkn...@medxchange.com > > On Sat, May 14, 2016 at 6:27 PM, Khem Raj wrote: > >> On Sat, May 14, 2016 at 3:23 PM, Paul Knopf >> wrote: >> > NVideo provides the following crosstools-ng config for building a >> > cross-compile toolchain. >> > >> > https://gist.github.com/anonymous/95b2ec71aebf8df644b1789bc3ed958d >> > >> >> with OE it will build everything for you >> just clone >> >> https://github.com/kraj/meta-jetson-tk1 >> >> add it to bblayers.conf >> and then set MACHINE = "jetson-tk1" >> and bitbake core-image-minimal >> >> >> > Some parts I think that are relevant... >> > >> > - >> > CT_ARCH="arm" >> > CT_ARCH_SUPPORTS_BOTH_MMU=y >> > CT_ARCH_SUPPORTS_BOTH_ENDIAN=y >> > CT_ARCH_SUPPORTS_32=y >> > CT_ARCH_SUPPORTS_WITH_ARCH=y >> > CT_ARCH_SUPPORTS_WITH_CPU=y >> > CT_ARCH_SUPPORTS_WITH_TUNE=y >> > CT_ARCH_SUPPORTS_WITH_FLOAT=y >> > CT_ARCH_SUPPORTS_WITH_FPU=y >> > CT_ARCH_SUPPORTS_SOFTFP=y >> > CT_ARCH_DEFAULT_HAS_MMU=y >> > CT_ARCH_DEFAULT_LE=y >> > CT_ARCH_DEFAULT_32=y >> > CT_ARCH_ARCH="armv7-a" >> > CT_ARCH_CPU="cortex-a9" >> > CT_ARCH_TUNE="cortex-a9" >> > CT_ARCH_FPU="" >> > # CT_ARCH_BE is not set >> > CT_ARCH_LE=y >> > CT_ARCH_32=y >> > CT_ARCH_BITNESS=32 >> > CT_ARCH_FLOAT_HW=y >> > # CT_ARCH_FLOAT_SW is not set >> > CT_TARGET_CFLAGS="" >> > CT_TARGET_LDFLAGS="" >> > # CT_ARCH_alpha is not set >> > CT_ARCH_arm=y >> > # CT_ARCH_avr32 is not set >> > # CT_ARCH_blackfin is not set >> > # CT_ARCH_m68k is not set >> > # CT_ARCH_mips is not set >> > # CT_ARCH_powerpc is not set >> > # CT_ARCH_s390 is not set >> > # CT_ARCH_sh is not set >> > # CT_ARCH_sparc is not set >> > # CT_ARCH_x86 is not set >> > CT_ARCH_alpha_AVAILABLE=y >> > CT_ARCH_arm_AVAILABLE=y >> > CT_ARCH_avr32_AVAILABLE=y >> > CT_ARCH_blackfin_AVAILABLE=y >> > CT_ARCH_m68k_AVAILABLE=y >> > CT_ARCH_mips_AVAILABLE=y >> > CT_ARCH_powerpc_AVAILABLE=y >> > CT_ARCH_s390_AVAILABLE=y >> > CT_ARCH_sh_AVAILABLE=y >> > CT_ARCH_sparc_AVAILABLE=y >> > CT_ARCH_x86_AVAILABLE=y >> > - >> > >> > What files do I need to build with this cross-toolchain, inside of >> Yocto? >> > >> > >> > Thanks, >> > Paul Knopf >> > Software Engineer >> > Med X Change, Inc >> > pkn...@medxchange.com >> > >> > On Sat, May 14, 2016 at 6:14 PM, Paul Knopf >> wrote: >> >> >> >> They are using "require conf/machine/include/tune-cortexa15.inc" for >> the >> >> TK1, but the TX1 uses a Cortex A57, not a A15. There is no >> "tune-cortexa57". >> >> >> >> Thanks, >> >> Paul Knopf >> >> Software Engineer >> >> Med X Change, Inc >> >> pkn...@medxchange.com >> >> >> >> On Sat, May 14, 2016 at 6:08 PM, Khem Raj wrote: >> >>> >> >>> Look at kraj/meta-jetson-tk1 on github >> >>> >> >>> On May 14, 2016 2:17 PM, "Paul Knopf" wrote: >> >> What configs do I need to include in my machine.conf to support this >> processor? >> >> http://www.nvidia.com/object/jetson-tx1-dev-kit.html >> >> "require conf/machine/include/arm/arch-*.inc" ? >> >> Thanks, >> Paul Knopf >> Software Engineer >> Med X Change, Inc >> pkn...@medxchange.com >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> >> >> > >> > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
