conf/machine: use xz over gz for images
PATCH 1/3 conf/machine: use xz over gz for images
The current meta-arago later assumes there will be a .tar.gz for the machines build into tisdk-rootfs-images. This compresses better anyway so lets switch these remaining machines over.
--- conf/machine/am3517-evm.conf | 2 +- conf/machine/am37x-evm.conf | 2 +- conf/machine/beagleboard.conf | 2 +- conf/machine/omap3evm.conf | 2 +- conf/machine/omap5-evm.conf | 2 +- conf/machine/pandaboard.conf | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-)
conf/machine/am3517-evm.conf +1 -1
@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS2"
conf/machine/am37x-evm.conf +1 -1
@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" KERNEL_DEVICETREE = "omap3-evm-37xx.dtb"
conf/machine/beagleboard.conf +1 -1
@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc # Only has DVI connector for external screen MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz ubi" +IMAGE_FSTYPES += "tar.xz ubi" EXTRA_IMAGECMD_jffs2 = "-lnp" KERNEL_DEVICETREE = "omap3-beagle.dtb omap3-beagle-xm.dtb omap3-beagle-xm-ab.dtb"
conf/machine/omap3evm.conf +1 -1
@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "jffs2 tar.gz" +IMAGE_FSTYPES += "jffs2 tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS0"
conf/machine/omap5-evm.conf +1 -1
@@ -4,7 +4,7 @@ require conf/machine/include/omap-a15.inc -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" KERNEL_DEVICETREE = "omap5-uevm.dtb"
conf/machine/pandaboard.conf +1 -1
@@ -6,7 +6,7 @@ require conf/machine/include/omap4.inc MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz" +IMAGE_FSTYPES += "tar.xz" KERNEL_DEVICETREE = "omap4-panda.dtb omap4-panda-a4.dtb omap4-panda-es.dtb"
Signature · 1 line
2.17.1
PATCH 2/3 Move Graphics and Multimedia drivers and apps out of recipes-bsp
recipes-bsp is looking a bit random at the moment, lets move graphics recipies into recipes-graphics and some multimedia related ones into recipes-multimedia.
---
.../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb | 0
.../ti-img-rogue-driver/0001-km-support-general-toolchain.patch | 0
.../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb | 0
.../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0
...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0
.../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb | 0
.../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb | 0
.../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb | 0
.../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb | 0
.../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb | 0
.../ti-img-encode-decode/viddec-test-app_1.0.0.bb | 0
.../ti-img-encode-decode/videnc-test-app_1.0.0.bb | 0
12 files changed, 0 insertions(+), 0 deletions(-)
rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%)
rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%)
rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%)
rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%)
rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%)
rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%)
rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%)
rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%)
rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%)
rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%)
rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%)
rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb renamed from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb +0 -0
recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch +0 -0
recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb +0 -0
recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb renamed from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb +0 -0
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch +0 -0
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb +0 -0
recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb renamed from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +0 -0
recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb renamed from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb +0 -0
recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb renamed from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb +0 -0
recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb +0 -0
recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb +0 -0
recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb +0 -0
Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp
Quoted 3 lines · Andrew F. Davis
recipes-bsp is looking a bit random at the moment, lets move graphics recipies into recipes-graphics and some multimedia related ones into recipes-multimedia.
Yeah, let me sit on this one for a bit - I'm slightly torn here, as I like some of the new names/locations, but not all them...
Quoted 79 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb | 0 .../ti-img-rogue-driver/0001-km-support-general-toolchain.patch | 0 .../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb | 0 .../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0 ...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0 .../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb | 0 .../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb | 0 .../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb | 0 .../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb | 0 .../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb | 0 .../ti-img-encode-decode/viddec-test-app_1.0.0.bb | 0 .../ti-img-encode-decode/videnc-test-app_1.0.0.bb | 0 12 files changed, 0 insertions(+), 0 deletions(-) rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%) rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%) rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%) rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%) rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb renamed from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb renamed from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb renamed from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb renamed from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb renamed from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb +0
-0recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb +0
-0Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp
Quoted 8 lines · Denys Dmytriyenko
Quoted 3 lines · Andrew F. Davis
recipes-bsp is looking a bit random at the moment, lets move graphics recipies into recipes-graphics and some multimedia related ones into recipes-multimedia.
Yeah, let me sit on this one for a bit - I'm slightly torn here, as I like some of the new names/locations, but not all them...
Same, I wasn't sure if I even wanted to post this one, but some later work I did depended on the new locations and I didn't feel like un-doing it.
Anyway here is another thing I was thinking:
recipes-bsp -> firmwares
recipes-kernel -> all kernel stuff including kernel modules recipes-graphics -> just the UM side drivers and apps
Right now we have kernel module recipes in several places, usually bundled either their assosiated firmware or UM drivers. If we split things out like above we can keep everything in more consistent locations.
Let me know if you have a prefrence either way.
Andrew
Quoted 80 lines
Quoted 80 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb | 0 .../ti-img-rogue-driver/0001-km-support-general-toolchain.patch | 0 .../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb | 0 .../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0 ...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0 .../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb | 0 .../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb | 0 .../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb | 0 .../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb | 0 .../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb | 0 .../ti-img-encode-decode/viddec-test-app_1.0.0.bb | 0 .../ti-img-encode-decode/videnc-test-app_1.0.0.bb | 0 12 files changed, 0 insertions(+), 0 deletions(-) rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%) rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%) rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%) rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%) rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb renamed from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb renamed from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb renamed from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb renamed from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb renamed from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb +0
-0recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb +0
-0Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp
Quoted 20 lines · Andrew F. Davis
Quoted 8 lines · Denys Dmytriyenko
Quoted 3 lines · Andrew F. Davis
recipes-bsp is looking a bit random at the moment, lets move graphics recipies into recipes-graphics and some multimedia related ones into recipes-multimedia.
Yeah, let me sit on this one for a bit - I'm slightly torn here, as I like some of the new names/locations, but not all them...
Same, I wasn't sure if I even wanted to post this one, but some later work I did depended on the new locations and I didn't feel like un-doing it.
Anyway here is another thing I was thinking:
recipes-bsp -> firmwares
recipes-kernel -> all kernel stuff including kernel modules recipes-graphics -> just the UM side drivers and apps
Quoted 5 lines
Right now we have kernel module recipes in several places, usually bundled either their assosiated firmware or UM drivers. If we split things out like above we can keep everything in more consistent locations.
Let me know if you have a prefrence either way.
I've been noticing that recipes-bsp has been growing out of proportion.
Some old names are historic, but maybe even more correct, e.g.:
https://en.wikipedia.org/wiki/PowerVR
I like "vivante" rename. Still thinking about "img" vs. powervr due to above.
Historically, out-of-tree kernel modules lived in recipes-bsp, while user-space apps and libs in recipes-graphics/recipes-multimedia. But I might agree to moving drivers away from recipes-bsp to leave that only for firmwares and maybe LLDs...
Denys
Quoted 84 lines
Andrew
Quoted 80 lines
Quoted 80 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb | 0 .../ti-img-rogue-driver/0001-km-support-general-toolchain.patch | 0 .../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb | 0 .../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0 ...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0 .../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb | 0 .../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb | 0 .../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb | 0 .../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb | 0 .../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb | 0 .../ti-img-encode-decode/viddec-test-app_1.0.0.bb | 0 .../ti-img-encode-decode/videnc-test-app_1.0.0.bb | 0 12 files changed, 0 insertions(+), 0 deletions(-) rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%) rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%) rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%) rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%) rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb renamed from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb renamed from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb renamed from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb renamed from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb renamed from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb +0
-0recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb +0
-0Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 2/3] Move Graphics and Multimedia drivers and apps out of recipes-bsp
Quoted 25 lines · Denys Dmytriyenko
Quoted 24 lines · Andrew F. Davis
Quoted 8 lines · Denys Dmytriyenko
Quoted 3 lines · Andrew F. Davis
recipes-bsp is looking a bit random at the moment, lets move graphics recipies into recipes-graphics and some multimedia related ones into recipes-multimedia.
Yeah, let me sit on this one for a bit - I'm slightly torn here, as I like some of the new names/locations, but not all them...
Same, I wasn't sure if I even wanted to post this one, but some later work I did depended on the new locations and I didn't feel like un-doing it.
Anyway here is another thing I was thinking:
recipes-bsp -> firmwares
recipes-kernel -> all kernel stuff including kernel modules recipes-graphics -> just the UM side drivers and appsRight now we have kernel module recipes in several places, usually bundled either their assosiated firmware or UM drivers. If we split things out like above we can keep everything in more consistent locations.
Quoted 9 lines
Quoted 1 line
Let me know if you have a prefrence either way.
I've been noticing that recipes-bsp has been growing out of proportion.
Some old names are historic, but maybe even more correct, e.g.:
https://en.wikipedia.org/wiki/PowerVRI like "vivante" rename. Still thinking about "img" vs. powervr due to above.
Personally, keeping the discrete solution's name they offered way back when by VideoLogic, even after becoming IMG, was a confusing thing to do on their part.
Now they are completely moving away from it at least, so "ti-img-sgx" seems to be the most consistent name for the line of "Imagination Technologies PowerVR Series5 SGX" GPUs in our chips.
Next after "SGX" they have "Rogue", "Furian", and "Albiorix" (according to wikipedia) so we could probably stay consistent going forward as ti-img-<family_name>. Which is what I do in this patch.
Quoted 5 lines
Historically, out-of-tree kernel modules lived in recipes-bsp, while user-space apps and libs in recipes-graphics/recipes-multimedia. But I might agree to moving drivers away from recipes-bsp to leave that only for firmwares and maybe LLDs...
I was looking for how others handled the kernel modules and took a hint from our friends over at NXP[0].
[0]
https://github.com/Freescale/meta-freescale/tree/master/recipes-kernel/kernel-modules
Andrew
Quoted 87 lines
Denys
Quoted 84 lines
Andrew
Quoted 80 lines
Quoted 80 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb | 0 .../ti-img-rogue-driver/0001-km-support-general-toolchain.patch | 0 .../ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb | 0 .../{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb | 0 ...001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 0 .../ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb | 0 .../{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb | 0 .../ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb | 0 .../{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb | 0 .../ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb | 0 .../ti-img-encode-decode/viddec-test-app_1.0.0.bb | 0 .../ti-img-encode-decode/videnc-test-app_1.0.0.bb | 0 12 files changed, 0 insertions(+), 0 deletions(-) rename recipes-bsp/{ti-img-encode-decode => vxd-dec-fw}/vxd-dec-fw_git.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver/0001-km-support-general-toolchain.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-rogue}/ti-img-rogue-driver_1.10.5371573.bb (100%) rename recipes-graphics/{libgles => ti-img-rogue}/ti-img-rogue-umlibs_1.10.5371573.bb (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch (100%) rename {recipes-bsp/powervr-drivers => recipes-graphics/ti-img-sgx}/ti-sgx-ddk-km_1.17.4948957.bb (100%) rename recipes-graphics/{libgles => ti-img-sgx}/ti-sgx-ddk-um_1.17.4948957.bb (100%) rename {recipes-bsp/gc320-drivers => recipes-graphics/ti-vivante-gc320}/ti-gc320-driver_5.0.11.p7.bb (100%) rename recipes-graphics/{libgal => ti-vivante-gc320}/ti-gc320-libs_5.0.11.p7.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/viddec-test-app_1.0.0.bb (100%) rename {recipes-bsp => recipes-multimedia}/ti-img-encode-decode/videnc-test-app_1.0.0.bb (100%)recipes-bsp/vxd-dec-fw/vxd-dec-fw_git.bb renamed from recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver/0001-km-support-general-toolchain.patch renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb renamed from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb +0
-0recipes-graphics/ti-img-rogue/ti-img-rogue-umlibs_1.10.5371573.bb renamed from recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb renamed from recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb +0
-0recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb renamed from recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-driver_5.0.11.p7.bb renamed from recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb +0
-0recipes-graphics/ti-vivante-gc320/ti-gc320-libs_5.0.11.p7.bb renamed from recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb +0
-0recipes-multimedia/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/viddec-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb +0
-0recipes-multimedia/ti-img-encode-decode/videnc-test-app_1.0.0.bb renamed from recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb +0
-0Signature · 1 line
2.17.1
PATCH 3/3 recipes-graphics: Use M for kernel build subdirectory over SUBDIRS
In reply to Andrew F. DavisSUBDIRS has been deprecated for a while and as of k5.4 no longer works. Use M= instead.
--- .../ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb | 2 +- recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb +1 -1
@@ -32,5 +32,5 @@ PVR_WS = "wayland" EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${PVR_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${PVR_SOC} WINDOW_SYSTEM=${PVR_WS}' do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +2 -2
@@ -38,9 +38,9 @@ do_compile_prepend() { } do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install } do_install_k3() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }
Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 3/3] recipes-graphics: Use M for kernel build subdirectory over SUBDIRS
Quoted 2 lines · Andrew F. Davis
SUBDIRS has been deprecated for a while and as of k5.4 no longer works. Use M= instead.
Thanks! Sorry, can you please swap this with patch #2, so I can merge it w/o moving things around yet. Thanks.
Quoted 36 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb | 2 +- recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb +1
-1@@ -32,5 +32,5 @@ PVR_WS = "wayland" EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${PVR_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${PVR_SOC} WINDOW_SYSTEM=${PVR_WS}' do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +2
-2@@ -38,9 +38,9 @@ do_compile_prepend() { } do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install } do_install_k3() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }Signature · 1 line
2.17.1
Re: [meta-ti][master][PATCH 3/3] recipes-graphics: Use M for kernel build subdirectory over SUBDIRS
Quoted 7 lines · Denys Dmytriyenko
Quoted 2 lines · Andrew F. Davis
SUBDIRS has been deprecated for a while and as of k5.4 no longer works. Use M= instead.
Thanks! Sorry, can you please swap this with patch #2, so I can merge it w/o moving things around yet. Thanks.
Sent as standalone patch.
Andrew
Quoted 37 lines
Quoted 37 lines
Signed-off-by Andrew F. Davis <[email protected]>--- .../ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb | 2 +- recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)recipes-graphics/ti-img-rogue/ti-img-rogue-driver_1.10.5371573.bb +1
-1@@ -32,5 +32,5 @@ PVR_WS = "wayland" EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${PVR_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${PVR_SOC} WINDOW_SYSTEM=${PVR_WS}' do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +2
-2@@ -38,9 +38,9 @@ do_compile_prepend() { } do_install() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_armhf/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install } do_install_k3() { - make -C ${STAGING_KERNEL_DIR} SUBDIRS=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install + make -C ${STAGING_KERNEL_DIR} M=${B}/eurasia_km/eurasiacon/binary_omap_linux_nulldrmws_release/target_aarch64/kbuild INSTALL_MOD_PATH=${D} PREFIX=${STAGING_DIR_HOST} modules_install }Signature · 1 line
2.17.1
Quoted 3 lines · Andrew F. Davis
The current meta-arago later assumes there will be a .tar.gz for the machines build into tisdk-rootfs-images. This compresses better anyway so lets switch these remaining machines over.
I'm fine with the code change, but I'm not fine with the message above. Need to come up with a more generic/neutral message - meta-ti should not refer to meta-arago or any specific Distro, as it's meant to be distro-agnostic. Moreover, meta-ti is being used in other distros and environment. So, just mentioning better compression ratio should be fine here. Thanks.
Denys
Quoted 91 lines
Signed-off-by Andrew F. Davis <[email protected]>--- conf/machine/am3517-evm.conf | 2 +- conf/machine/am37x-evm.conf | 2 +- conf/machine/beagleboard.conf | 2 +- conf/machine/omap3evm.conf | 2 +- conf/machine/omap5-evm.conf | 2 +- conf/machine/pandaboard.conf | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-)conf/machine/am3517-evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS2"conf/machine/am37x-evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" KERNEL_DEVICETREE = "omap3-evm-37xx.dtb"conf/machine/beagleboard.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc # Only has DVI connector for external screen MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz ubi" +IMAGE_FSTYPES += "tar.xz ubi" EXTRA_IMAGECMD_jffs2 = "-lnp" KERNEL_DEVICETREE = "omap3-beagle.dtb omap3-beagle-xm.dtb omap3-beagle-xm-ab.dtb"conf/machine/omap3evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "jffs2 tar.gz" +IMAGE_FSTYPES += "jffs2 tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS0"conf/machine/omap5-evm.conf +1
-1@@ -4,7 +4,7 @@ require conf/machine/include/omap-a15.inc -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" KERNEL_DEVICETREE = "omap5-uevm.dtb"conf/machine/pandaboard.conf +1
-1@@ -6,7 +6,7 @@ require conf/machine/include/omap4.inc MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz" +IMAGE_FSTYPES += "tar.xz" KERNEL_DEVICETREE = "omap4-panda.dtb omap4-panda-a4.dtb omap4-panda-es.dtb"Signature · 1 line
2.17.1
Quoted 11 lines · Denys Dmytriyenko
Quoted 3 lines · Andrew F. Davis
The current meta-arago later assumes there will be a .tar.gz for the machines build into tisdk-rootfs-images. This compresses better anyway so lets switch these remaining machines over.
I'm fine with the code change, but I'm not fine with the message above. Need to come up with a more generic/neutral message - meta-ti should not refer to meta-arago or any specific Distro, as it's meant to be distro-agnostic. Moreover, meta-ti is being used in other distros and environment. So, just mentioning better compression ratio should be fine here. Thanks.
I was worried about that also, but the only thing that seems to break is when building these with meta-arago on top. Something to do with packaging in that layer only works with .tar.zx so these machines that do .tar.gz break.
I'll re-word this as suggested.
Andrew
Quoted 94 lines
Denys
Quoted 91 lines
Signed-off-by Andrew F. Davis <[email protected]>--- conf/machine/am3517-evm.conf | 2 +- conf/machine/am37x-evm.conf | 2 +- conf/machine/beagleboard.conf | 2 +- conf/machine/omap3evm.conf | 2 +- conf/machine/omap5-evm.conf | 2 +- conf/machine/pandaboard.conf | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-)conf/machine/am3517-evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS2"conf/machine/am37x-evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" KERNEL_DEVICETREE = "omap3-evm-37xx.dtb"conf/machine/beagleboard.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc # Only has DVI connector for external screen MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz ubi" +IMAGE_FSTYPES += "tar.xz ubi" EXTRA_IMAGECMD_jffs2 = "-lnp" KERNEL_DEVICETREE = "omap3-beagle.dtb omap3-beagle-xm.dtb omap3-beagle-xm-ab.dtb"conf/machine/omap3evm.conf +1
-1@@ -7,7 +7,7 @@ require conf/machine/include/omap3.inc MACHINE_GUI_CLASS = "smallscreen" MACHINE_FEATURES += "touchscreen ethernet" -IMAGE_FSTYPES += "jffs2 tar.gz" +IMAGE_FSTYPES += "jffs2 tar.xz" EXTRA_IMAGECMD_jffs2 = "-lnp -e 0x20000 -s 2048" SERIAL_CONSOLES = "115200;ttyS0"conf/machine/omap5-evm.conf +1
-1@@ -4,7 +4,7 @@ require conf/machine/include/omap-a15.inc -IMAGE_FSTYPES += "ubi tar.gz" +IMAGE_FSTYPES += "ubi tar.xz" KERNEL_DEVICETREE = "omap5-uevm.dtb"conf/machine/pandaboard.conf +1
-1@@ -6,7 +6,7 @@ require conf/machine/include/omap4.inc MACHINE_GUI_CLASS = "bigscreen" -IMAGE_FSTYPES += "tar.gz" +IMAGE_FSTYPES += "tar.xz" KERNEL_DEVICETREE = "omap4-panda.dtb omap4-panda-a4.dtb omap4-panda-es.dtb"Signature · 1 line
2.17.1