[meta-freescale] [3rdparty][PATCH 1/3] linux-boundary-rt: remove unmaintained version
Now that the kernel headers are fixed to 4.9 in meta-freescale, 3rd
party kernel better match that same version.
We currently do not have the bandwidth to maintain such RT version so
remove it to avoid confusion.
Signed-off-by: Gary Bisson
---
.../0001-fix-build.patch | 71 ---
.../0002-no-split-ptlocks.patch | 85
...nd-CPU-stalls-in-the-imx-sdma-driver.patch | 126 -
.../0004-export-swait-locked-functions.patch | 31 --
.../linux/linux-boundary-rt-4.1.15/defconfig | 451 --
.../linux/linux-boundary-rt_4.1.15.bb | 24 -
6 files changed, 788 deletions(-)
delete mode 100644
recipes-kernel/linux/linux-boundary-rt-4.1.15/0001-fix-build.patch
delete mode 100644
recipes-kernel/linux/linux-boundary-rt-4.1.15/0002-no-split-ptlocks.patch
delete mode 100644
recipes-kernel/linux/linux-boundary-rt-4.1.15/0003-Work-around-CPU-stalls-in-the-imx-sdma-driver.patch
delete mode 100644
recipes-kernel/linux/linux-boundary-rt-4.1.15/0004-export-swait-locked-functions.patch
delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/defconfig
delete mode 100644 recipes-kernel/linux/linux-boundary-rt_4.1.15.bb
diff --git a/recipes-kernel/linux/linux-boundary-rt-4.1.15/0001-fix-build.patch
b/recipes-kernel/linux/linux-boundary-rt-4.1.15/0001-fix-build.patch
deleted file mode 100644
index 4be4066..000
--- a/recipes-kernel/linux/linux-boundary-rt-4.1.15/0001-fix-build.patch
+++ /dev/null
@@ -1,71 +0,0 @@
-Fix build errors when RT patch is applied
-
-Upstream-Status: Inappropriate [other]
-Freescale does not support the RT patch
-
-Signed-off-by: Jacob Kroon
-Signed-off-by: Dominic Sacré [updated for 3.14.28]
-
-diff --git a/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c
b/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c
-index 2ec98dc..5d0b7df 100644
a/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c
-+++ b/drivers/mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_os.c
-@@ -7344,7 +7344,7 @@ gckOS_WaitSignal(
-
- might_sleep();
-
--spin_lock_irq(&signal->obj.wait.lock);
-+raw_spin_lock_irq(&signal->obj.wait.lock);
-
- if (signal->obj.done)
- {
-@@ -7366,9 +7366,8 @@ gckOS_WaitSignal(
- ? MAX_SCHEDULE_TIMEOUT
- : Wait * HZ / 1000;
-
--DECLARE_WAITQUEUE(wait, current);
--wait.flags |= WQ_FLAG_EXCLUSIVE;
--__add_wait_queue_tail(&signal->obj.wait, &wait);
-+DEFINE_SWAITER(wait);
-+swait_prepare_locked(&signal->obj.wait, &wait);
-
- while (gcvTRUE)
- {
-@@ -7380,9 +7379,9 @@ gckOS_WaitSignal(
- }
-
- __set_current_state(TASK_INTERRUPTIBLE);
--spin_unlock_irq(&signal->obj.wait.lock);
-+raw_spin_unlock_irq(&signal->obj.wait.lock);
- timeout = schedule_timeout(timeout);
--spin_lock_irq(&signal->obj.wait.lock);
-+raw_spin_lock_irq(&signal->obj.wait.lock);
-
- if (signal->obj.done)
- {
-@@ -7403,10 +7402,10 @@ gckOS_WaitSignal(
- }
- }
-
--__remove_wait_queue(&signal->obj.wait, &wait);
-+swait_finish_locked(&signal->obj.wait, &wait);
- }
-
--spin_unlock_irq(&signal->obj.wait.lock);
-+raw_spin_unlock_irq(&signal->obj.wait.lock);
-
- OnError:
- /* Return status. */
-diff --git a/include/linux/imx_sema4.h b/include/linux/imx_sema4.h
-index 9787980..3586199 100644
a/include/linux/imx_sema4.h
-+++ b/include/linux/imx_sema4.h
-@@ -9,6 +9,8 @@
- #ifndef __LINUX_IMX_SEMA4_H__
- #define __LINUX_IMX_SEMA4_H__
-
-+#include
-+
- #define SEMA4_NUM_DEVICES 1
- #define SEMA4_NUM_GATES 16
-
diff --git
a/recipes-kernel/linux/linux-boundary-rt-4.1.15/0002-no-split-ptlocks.patch
b/recipes-kernel/linux/linux-boundary-rt-4.1.15/0002-no-split-ptlocks.patch
deleted file mode 100644
index 40c012a..000
--- a/recipes-kernel/linux/linux-boundary-rt-4.1.15/0002-no-split-ptlocks.patch
+++ /dev/null
@@ -1,85 +0,0 @@
-Work around the oops below by disabling split ptlocks
-
-Upstream-Status: Inappropriate [disable feature]
-
-Signed-off-by: Jacob Kroon
-Signed-off-by: Dominic Sacré [updated for 3.14.28]
-
-Unable to handle kernel NULL pointer dereference at virtual address
-pgd = ac5a8000
-[] *pgd=3c8db831, *pte=, *ppte=
-Internal error: Oops: 17 [#1] PREEMPT SMP ARM
-Modules linked in:
-CPU: 1 PID: 277 Comm: test-qt5 Not tainted 3.10.17-rt12-monkey+gec1af9f #2
-task: ac65df80 ti: ac968000 task.ti: ac968000
-PC is at _raw_spin_lock+0x10/0x4c
-LR is at get_parent_ip+0x10/0x2c
-pc : [<80623fd4>]lr : [<8004ef18>]psr: 60010013
-sp : ac969c38 ip : 80c44404 fp :
-r10: ac65df80 r9 : ac969cd8 r8 :
-r7 : 0054 r6 : afffe000 r5 : r4 :
-r3 : ac
[meta-freescale] [3rdparty][PATCH 3/3] u-boot-boundary: bump revision to ca185fc7
Main changes are:
- Fix blkcache to match page size
- Add LCM JM430 display support
- Add LTK0680YTMDB display support
- Fix DDR initialization
- Fix M4 loading/booting
Signed-off-by: Gary Bisson
---
recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
b/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
index 9b9b363..59b17cc 100644
--- a/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
+++ b/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM =
"file://Licenses/README;md5=30503fd321432fc713238f582193b78e"
PV = "v2018.07+git${SRCPV}"
-SRCREV = "f35ba6cfbe5a0f039ec14e790e212564e98c84d6"
+SRCREV = "ca185fc7406207da613c728935f534a4054674f1"
SRCBRANCH = "boundary-v2018.07"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
--
2.19.1
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 2/3] linux-boundary: bump revision to a141bcc8
Main changes are: - Merge v4.9.128 stable release - Enable Cypress cyttsp5 touch controller - Fix i.MX8MQ HDMI audio bitrates - Add EETI EXC3000 touch support - Add LCM JM430 display support (MIPI to LCD) - Fix i.MX8MQ DCSS colors issue (REC.709) - Enable Sitronix st1633 touch controller Signed-off-by: Gary Bisson --- .../linux/linux-boundary-4.9.x/arm/defconfig | 21 +++ .../linux-boundary-4.9.x/arm64/defconfig | 10 - recipes-kernel/linux/linux-boundary_4.9.x.bb | 2 +- 3 files changed, 31 insertions(+), 2 deletions(-) diff --git a/recipes-kernel/linux/linux-boundary-4.9.x/arm/defconfig b/recipes-kernel/linux/linux-boundary-4.9.x/arm/defconfig index ecbd470..8df3b3d 100644 --- a/recipes-kernel/linux/linux-boundary-4.9.x/arm/defconfig +++ b/recipes-kernel/linux/linux-boundary-4.9.x/arm/defconfig @@ -1,13 +1,24 @@ CONFIG_KERNEL_LZO=y CONFIG_SYSVIPC=y +CONFIG_POSIX_MQUEUE=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_CGROUPS=y +CONFIG_MEMCG=y +CONFIG_MEMCG_SWAP=y +# CONFIG_MEMCG_SWAP_ENABLED is not set +CONFIG_BLK_CGROUP=y CONFIG_CGROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y +CONFIG_CGROUP_PIDS=y +CONFIG_CGROUP_FREEZER=y +CONFIG_CPUSETS=y +CONFIG_CGROUP_DEVICE=y +CONFIG_CGROUP_CPUACCT=y +CONFIG_CGROUP_PERF=y CONFIG_NAMESPACES=y CONFIG_BLK_DEV_INITRD=y CONFIG_EXPERT=y @@ -58,6 +69,7 @@ CONFIG_PM_TEST_SUSPEND=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=y +CONFIG_XFRM_USER=m CONFIG_INET=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y @@ -82,6 +94,10 @@ CONFIG_NFT_NAT=m CONFIG_NFT_REJECT=m CONFIG_NFT_COMPAT=m CONFIG_NFT_HASH=m +CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m +CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m +CONFIG_NETFILTER_XT_MATCH_IPVS=m +CONFIG_IP_VS=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NFT_CHAIN_NAT_IPV4=m CONFIG_NFT_MASQ_IPV4=m @@ -156,6 +172,7 @@ CONFIG_MD=y CONFIG_BLK_DEV_DM=y CONFIG_NETDEVICES=y CONFIG_TUN=m +CONFIG_VETH=m # CONFIG_NET_CADENCE is not set # CONFIG_NET_VENDOR_BROADCOM is not set # CONFIG_NET_VENDOR_CIRRUS is not set @@ -209,7 +226,11 @@ CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_AR1020_I2C=m CONFIG_TOUCHSCREEN_ATMEL_MXT=m CONFIG_TOUCHSCREEN_CR_MULTI=m +CONFIG_TOUCHSCREEN_CYPRESS_CYTTSP5=m +CONFIG_TOUCHSCREEN_CYPRESS_CYTTSP5_DEVICETREE_SUPPORT=y +CONFIG_TOUCHSCREEN_CYPRESS_CYTTSP5_I2C=m CONFIG_TOUCHSCREEN_EGALAX=m +CONFIG_TOUCHSCREEN_EXC3000=m CONFIG_TOUCHSCREEN_FT5X06=m CONFIG_TOUCHSCREEN_GOODIX=m CONFIG_TOUCHSCREEN_ILI210X=m diff --git a/recipes-kernel/linux/linux-boundary-4.9.x/arm64/defconfig b/recipes-kernel/linux/linux-boundary-4.9.x/arm64/defconfig index bfaeba0..4e74c69 100644 --- a/recipes-kernel/linux/linux-boundary-4.9.x/arm64/defconfig +++ b/recipes-kernel/linux/linux-boundary-4.9.x/arm64/defconfig @@ -70,6 +70,7 @@ CONFIG_ARM_SCPI_CPUFREQ=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=y +CONFIG_XFRM_USER=m CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_PNP=y @@ -87,6 +88,8 @@ CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m CONFIG_NETFILTER_XT_TARGET_LOG=m CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m +CONFIG_NETFILTER_XT_MATCH_IPVS=m +CONFIG_IP_VS=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_FILTER=m @@ -122,7 +125,6 @@ CONFIG_BT_LEDS=y CONFIG_BT_HCIUART=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_ATH3K=y -CONFIG_BT_HCIUART_3WIRE=y CONFIG_BT_HCIUART_BCM=y CONFIG_BT_HCIUART_QCA=y CONFIG_BT_HCIVHCI=y @@ -161,6 +163,7 @@ CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=65536 CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_VIRTIO_BLK=y +CONFIG_BLK_DEV_NVME=m CONFIG_SENSORS_FXOS8700=y CONFIG_SENSORS_FXAS2100X=y CONFIG_SRAM=y @@ -224,6 +227,7 @@ CONFIG_KEYBOARD_IMX_SC_PWRKEY=y CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_FT5X06=m CONFIG_TOUCHSCREEN_GOODIX=m +CONFIG_TOUCHSCREEN_SITRONIX_I2C_TOUCH=m CONFIG_INPUT_MISC=y CONFIG_INPUT_UINPUT=y CONFIG_INPUT_MPL3115=y @@ -254,6 +258,7 @@ CONFIG_I2C_IMX_LPI2C=y CONFIG_I2C_CROS_EC_TUNNEL=y CONFIG_I2C_SLAVE=y CONFIG_SPI=y +CONFIG_SPI_IMX=y CONFIG_SPI_FSL_LPSPI=y CONFIG_SPI_PL022=y CONFIG_SPI_SPIDEV=m @@ -269,6 +274,7 @@ CONFIG_GPIO_MAX732X=y CONFIG_GPIO_PCA953X=y CONFIG_GPIO_PCA953X_IRQ=y CONFIG_GPIO_MAX77620=y +CONFIG_POWER_RESET_SNVS=y CONFIG_POWER_RESET_VEXPRESS=y CONFIG_POWER_RESET_XGENE=y CONFIG_POWER_RESET_SYSCON=y @@ -414,6 +420,7 @@ CONFIG_GADGET_UAC1=y CONFIG_USB_ETH=m CONFIG_USB_ETH_EEM=y CONFIG_USB_G_NCM=m +CONFIG_USB_FUNCTIONFS=m CONFIG_USB_MASS_STORAGE=m CONFIG_USB_G_SERIAL=m CONFIG_USB_CDC_COMPOSITE=m @@ -515,6 +522,7 @@ CONFIG_ECRYPT_FS_MESSAGING=y CONFIG_JFFS2_FS=y CONFIG_UBIFS_FS=y CONFIG_SQUASHFS=y +CONFIG_SQUASHFS_XZ=y CONFIG_NFS_FS=y CONFIG_NFS_V4=y CONFIG_NFS_V4_1=y diff --git a/recipes-kernel/linux/linux-boundary_4.9.x.bb b/recipes-kernel/linux/linux-boundary_4.9.x.bb index 2c2e2a4..c659eb1 100644 --- a/recipes-kernel/linux/linux-boundary_4.9.x.bb +++ b/recipes-kernel/linux/linux-boundary_4.9.x.bb @@ -15,6 +15,6 @@ SRC_URI
[meta-freescale] [3rdparty][PATCH 0/3] boundary: update kernel and uboot revisions
Hi, As the Thud release should be approaching we want to offer the best support for our Nitrogen8M right away. This series remove the RT kernel as it isn't maintained and that kernel headers 4.9 are being used right now. Then the U-Boot/Kernel revision bumps bring their share of improvements that are detailed in each commit log. Let me know if you have any question. Regards, Gary Gary Bisson (3): linux-boundary-rt: remove unmaintained version linux-boundary: bump revision to a141bcc8 u-boot-boundary: bump revision to ca185fc7 .../u-boot/u-boot-boundary-common_2018.07.inc | 2 +- .../linux/linux-boundary-4.9.x/arm/defconfig | 21 + .../linux-boundary-4.9.x/arm64/defconfig | 10 +- .../0001-fix-build.patch | 71 --- .../0002-no-split-ptlocks.patch | 85 ...nd-CPU-stalls-in-the-imx-sdma-driver.patch | 126 - .../0004-export-swait-locked-functions.patch | 31 -- .../linux/linux-boundary-rt-4.1.15/defconfig | 451 -- .../linux/linux-boundary-rt_4.1.15.bb | 24 - recipes-kernel/linux/linux-boundary_4.9.x.bb | 2 +- 10 files changed, 32 insertions(+), 791 deletions(-) delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/0001-fix-build.patch delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/0002-no-split-ptlocks.patch delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/0003-Work-around-CPU-stalls-in-the-imx-sdma-driver.patch delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/0004-export-swait-locked-functions.patch delete mode 100644 recipes-kernel/linux/linux-boundary-rt-4.1.15/defconfig delete mode 100644 recipes-kernel/linux/linux-boundary-rt_4.1.15.bb -- 2.19.1 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH v2] u-boot-boundary-fw-utils: Build cross recipe
Hi,
On Tue, Oct 23, 2018 at 12:07 AM Khem Raj wrote:
>
> Signed-off-by: Khem Raj
> ---
> recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
> b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
> index 0a7697a..804a504 100644
> --- a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
> +++ b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
> @@ -44,4 +44,5 @@ RPROVIDES_${PN} += "u-boot-fw-utils"
> BBCLASSEXTEND = "cross"
>
> COMPATIBLE_MACHINE = "(imx)"
> -COMPATIBLE_MACHINE_class-cross = "(.*)"
> +COMPATIBLE_MACHINE_class-cross_arm = "(.*)"
> +COMPATIBLE_MACHINE_class-cross_aarch64 = "(.*)"
Sorry for the dumb question but why is class-cross needed in the first
place? Isn't MACHINE = (imx) sufficient to only target imx platforms
which can only be arm/arm64.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH] u-boot-boundary-fw-utils: Define a dummy fw_env.config
Hi, On Sun, Oct 21, 2018 at 5:28 PM Khem Raj wrote: > > When building the cross recipe it complains about missing file > especially on non arm/aarch64 targets > > Fixes > WARNING: > /mnt/a/yoe/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb: > Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry > fw_env.config: file could not be found We should then limit the package to ARM/ARM64 architectures only as it should only be built for Boundary Devices platforms anyway (all of which are ARM). Adding a dummy config file doesn't feel right. Also, this package should only be built when explicitly added to your packages list, not sure why someone would build it when using machines other than nitrogen*. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH] imx-vpu-hantro: Fix h1 encoder build issue
Hi Carol, On Tue, Oct 9, 2018 at 4:16 AM Carol Zhu wrote: > > Modify the environment setting of h1 encoder to > correct include header directory, make LINUX_VERSION_CODE > come from kernel build folder instead of toolchain headers. > > Signed-off-by: Yuqing Zhu > --- > .../0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch | 2 > +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git > a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch > > b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch > index e9bf925..9d54223 100644 > --- > a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch > +++ > b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch > @@ -34,7 +34,7 @@ index 56b4332..0be43ce 100755 > ENV += -I$(LINUX_KERNEL_ROOT)/drivers/staging/android/uapi > > +# LINUX_VERSION_CODE from kernel build folder instead of toolchain headers > -+INCLUDE_HEADERS += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi > ++ENV += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi > + > LIBENCNAME = libcodec_enc > LIBSENC = -L./ -lhantro_h1 -lpthread > -- > 1.9.1 I now see what was the issue, I copied the same fix on both Makefile although one is using INCLUDE_HEADERS and the other ENV. Thanks for the fix! Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 01/14] linux-libc-headers: Use linux-libc-headers v4.9 for L4.9.123-2.3.0_8mm_ga
Hi Carol,
On Mon, Oct 8, 2018 at 11:30 AM Carol Zhu wrote:
> Hi Gary,
>
>
>
> I updated my local build env to the latest master branch and try building
> the vpu hantro.
>
> But I got a small build issue:
>
> | ./ewl/ewl_x280_common.c: In function 'EWLMallocLinear':
>
> | ./ewl/ewl_x280_common.c:775:25: error: storage size of 'dma_phys' isn't
> known
>
> | struct dma_buf_phys dma_phys;
>
> | ^~~~
>
> | ./ewl/ewl_x280_common.c:799:17: warning: assignment to '__u64' {aka
> 'long long unsigned int'} from 'struct ion_heap_data
> (*)[(sizetype)(heap_cnt)]' makes integer from pointer without a cast
> [-Wint-conversion]
>
> | query.heaps = &ihd;
>
> | ^
>
> | ./ewl/ewl_x280_common.c:819:35: error: 'struct ion_allocation_data' has
> no member named 'fd'
>
> | info->ion_fd = allocation_data.fd;
>
> |^
>
> | ./ewl/ewl_x280_common.c:821:31: error: 'DMA_BUF_IOCTL_PHYS' undeclared
> (first use in this function); did you mean 'DMA_BUF_IOCTL_SYNC'?
>
> | ret = ioctl(info->ion_fd, DMA_BUF_IOCTL_PHYS, &dma_phys);
>
> |^~
>
> |DMA_BUF_IOCTL_SYNC
>
What platform are you building for?
I only tried 8M (Nitrogen8M) and this worked for me. But maybe the encoder
part needs to be modified for 8MM.
It goes into >k4.14 branch as the incorrect LINUX_VERSION_CODE, so I did a
> update about the include directory of version.h, plz take a check.
>
> ---
> a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
>
> +++
> b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
>
> @@ -34,7 +34,7 @@ index 56b4332..0be43ce 100755
>
> ENV += -I$(LINUX_KERNEL_ROOT)/drivers/staging/android/uapi
>
>
>
> +# LINUX_VERSION_CODE from kernel build folder instead of toolchain headers
>
> -+INCLUDE_HEADERS += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi
>
> ++ENV += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi
>
If you have a fix please submit it.
> Thanks for your fix. It looks flexible and do fix the build problem.
>
> But I am still a little bit confused.
>
> For my understanding, the version of libc-headers should match the one of
> kernel, or the compatibility couldn’t be guaranteed.
>
No the toolchain header doesn't have to match the kernel version exactly as
the ABI is backward compatible.
> And our current release maintain both libc-header and Linux-imx recipes to
> make them version match.
>
> eg:
> https://source.codeaurora.org/external/imx/meta-fsl-bsp-release/tree/imKernel
> headerx/meta-bsp/recipes-kernel/linux-libc-headers?h=rocko-4.9.123-2.3.0_8mm_ga
>
>
> For people using pre-built toolchains, they’re supposed to choose proper
> version, which would be better.
>
As ABI is backwards compatible, people shouldn't have to worry about kernel
headers:
https://elinux.org/images/1/15/Anatomy_of_Cross-Compilation_Toolchains.pdf
If libc-headers could be backwards compatible except this “
> LINUX_VERSION_CODE”, then it’s ok with version mismatch.
>
Exactly, if the issue is only LINUX_VERSION_CODE then it should be taken
from kernel directly.
Also, since some headers are NXP-specific (ion.h), then even if you use a
pre-built toolchain with same version headers it won't work anyway as those
headers will be missing.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 01/14] linux-libc-headers: Use linux-libc-headers v4.9 for L4.9.123-2.3.0_8mm_ga
Hi Carol, This is fixed already by pointing to the kernel header directly. https://github.com/Freescale/meta-freescale/commit/387b285adc25aa244bfe90f4083320304af237c5 https://github.com/Freescale/meta-freescale/commit/476c63185e6864f82e938247235e7ad8ad20af4b Changing the toolchain header is not flexible enough. First, this is Yocto, but you need to think about people using other build systems like Buildroot where such change will never be merged. Also there's the case of people using pre-built toolchains, you can't control their headers versions. All in all, you shouldn't rely on toolchains headers, especially for LINUX_VERSION_CODE. Also, in the future, NXP will provide 4.14 kernel version, but what if someone wants to stick to a 4.9 (GA) kernel? Do you plan on having libc-headers for all next kernel releases? Doesn't sound like a scalable approach. Regards, Gary Bisson Boundary Devices, LLC www.boundarydevices.com <http://www.BoundaryDevices.com> On Mon, Oct 8, 2018 at 5:15 AM Carol Zhu wrote: > Hi Otavio, > > Sorry for the late reply, I just come back from our National Day Holiday. > > The current poky master has linux-libc-headers v4.18 but our kernel > version is 4.9.123, the two version are mismatch. > And when compiling vpu hantro, I got build break. > It needs to do LINUX_VERSION_CODE check, which relies on the > Linux/version.h from Linux-libc-headers. > So I have to downgrade the Linux-libc-headers to 4.9 to match with our > kernel version. > > > B.R. > Carol > -Original Message- > From: Otavio Salvador > Sent: 2018年10月2日 1:49 > To: Carol Zhu ; Tom Hochstein > Cc: meta-freescale Mailing List > Subject: Re: [meta-freescale] [PATCH 01/14] linux-libc-headers: Use > linux-libc-headers v4.9 for L4.9.123-2.3.0_8mm_ga > > On Sun, Sep 30, 2018 at 5:55 AM Yuqing Zhu wrote: > > Hold linux-libc-headers v4.9 in meta-freescale layer, which matches > > the current linux-imx version in L4.9.123-2.3.0_8mm_ga. > > > > Signed-off-by: Yuqing Zhu > > I already reported multiple times that we cannot change this recipe. > > Both Max and Gary raised the same concerns about it making all packages > machine specific which is forbidden. Please align with Tom about the > incoming work of using a set of imx specific headers instead. > > -- > Otavio Salvador O.S. Systems > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ossystems.com.br&data=02%7C01%7Ccarol.zhu%40nxp.com%7Cb3d3ad002e774a24ae6808d627c633e2%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636740129563654748&sdata=7gWSdDOkNN4c0EZiO7oXayw5X5Hum9JTo4XHCOvtYYQ%3D&reserved=0 > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcode.ossystems.com.br&data=02%7C01%7Ccarol.zhu%40nxp.com%7Cb3d3ad002e774a24ae6808d627c633e2%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636740129563654748&sdata=T4EZfBHWgktjyz00XYdVi0rZCADIMj9CXIRjgFPECus%3D&reserved=0 > Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 > -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH] u-boot-boundary: Update to v2018.07
From: Ian Coolidge
From: Ian Coolidge
Compatible with nitrogem8m board
Blog post: https://boundarydevices.com/u-boot-v2018-07/
Signed-off-by: Ian Coolidge
Signed-off-by: Gary Bisson
---
.../u-boot-boundary-common_2017.03.imx8m.inc | 15 ---
...inc => u-boot-boundary-common_2018.07.inc} | 8 ++--
.../aarch64/fw_env.config | 1 +
.../{ => arm}/fw_env.config | 0
...bb => u-boot-boundary-fw-utils_2018.07.bb} | 8 +++-
.../u-boot/u-boot-boundary_2017.03.imx8m.bb | 6 ---
recipes-bsp/u-boot/u-boot-boundary_2017.07.bb | 6 ---
recipes-bsp/u-boot/u-boot-boundary_2018.07.bb | 17 +++
.../u-boot-script-boundary_2017.03.imx8m.bb | 45 ---
...7.bb => u-boot-script-boundary_2018.07.bb} | 2 +-
10 files changed, 29 insertions(+), 79 deletions(-)
delete mode 100644 recipes-bsp/u-boot/u-boot-boundary-common_2017.03.imx8m.inc
rename recipes-bsp/u-boot/{u-boot-boundary-common_2017.07.inc =>
u-boot-boundary-common_2018.07.inc} (51%)
create mode 100644
recipes-bsp/u-boot/u-boot-boundary-fw-utils/aarch64/fw_env.config
rename recipes-bsp/u-boot/u-boot-boundary-fw-utils/{ => arm}/fw_env.config
(100%)
rename recipes-bsp/u-boot/{u-boot-boundary-fw-utils_2017.07.bb =>
u-boot-boundary-fw-utils_2018.07.bb} (83%)
delete mode 100644 recipes-bsp/u-boot/u-boot-boundary_2017.03.imx8m.bb
delete mode 100644 recipes-bsp/u-boot/u-boot-boundary_2017.07.bb
create mode 100644 recipes-bsp/u-boot/u-boot-boundary_2018.07.bb
delete mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_2017.03.imx8m.bb
rename recipes-bsp/u-boot/{u-boot-script-boundary_2017.07.bb =>
u-boot-script-boundary_2018.07.bb} (94%)
diff --git a/recipes-bsp/u-boot/u-boot-boundary-common_2017.03.imx8m.inc
b/recipes-bsp/u-boot/u-boot-boundary-common_2017.03.imx8m.inc
deleted file mode 100644
index 63f2bac..000
--- a/recipes-bsp/u-boot/u-boot-boundary-common_2017.03.imx8m.inc
+++ /dev/null
@@ -1,15 +0,0 @@
-DESCRIPTION = "U-Boot for Boundary Devices boards"
-LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
-
-PV = "v2017.03.imx8m+git${SRCPV}"
-
-SRCREV = "962210405277c99520aa4c5185c5aa2d589fbd1d"
-SRCBRANCH = "boundary-imx_v2017.03_4.9.51_imx8m_ga"
-SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
-
-S = "${WORKDIR}/git"
-
-inherit dtc-145
-
-PACKAGE_ARCH = "${MACHINE_ARCH}"
diff --git a/recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
b/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
similarity index 51%
rename from recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
rename to recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
index 4263fa1..9b9b363 100644
--- a/recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
+++ b/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc
@@ -1,11 +1,11 @@
DESCRIPTION = "U-Boot for Boundary Devices boards"
LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
+LIC_FILES_CHKSUM =
"file://Licenses/README;md5=30503fd321432fc713238f582193b78e"
-PV = "v2017.07+git${SRCPV}"
+PV = "v2018.07+git${SRCPV}"
-SRCREV = "445823ef2abfff2fc1c63cc53c57c1e139f88b1b"
-SRCBRANCH = "boundary-v2017.07"
+SRCREV = "f35ba6cfbe5a0f039ec14e790e212564e98c84d6"
+SRCBRANCH = "boundary-v2018.07"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
S = "${WORKDIR}/git"
diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils/aarch64/fw_env.config
b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/aarch64/fw_env.config
new file mode 100644
index 000..eccfb0f
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/aarch64/fw_env.config
@@ -0,0 +1 @@
+/dev/mmcblk0boot0 0x1fe0000x2000 0x1000
diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config
b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/arm/fw_env.config
similarity index 100%
rename from recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config
rename to recipes-bsp/u-boot/u-boot-boundary-fw-utils/arm/fw_env.config
diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
similarity index 83%
rename from recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
rename to recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
index f5dd879..56ba151 100644
--- a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
+++ b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb
@@ -1,7 +1,11 @@
require u-boot-boundary-common_${PV}.inc
SUMMARY = "U-Boot bootloader fw_printenv/setenv utilities"
-DEPENDS = "mtd-utils"
+DEPENDS += "mtd-utils bison-native"
+
+FILE
Re: [meta-freescale] [PATCH 0/2] Fix Hantro/Gstreamer build issues
Hi Tom,
On Wed, Oct 3, 2018 at 3:50 PM Tom Hochstein wrote:
> Hi Gary,
>
> Thanks for this fix and for letting us know about the ownership mistake.
>
> Related to this, I am working on a dedicated linux-imx-headers recipe with
> Otavio. With such a recipe, do you see a problem with copying ion.h from
> drivers/staging/android to /usr/include/linux?
>
Where do you plan on installing those headers? They shouldn't be mixed with
the libc/toolchain headers.
Then I'm not sure to see the benefit of such linux-imx-headers recipe vs.
pointing to the kernel dir as you do it already for many packages:
$ grep -r STAGING_KERNEL_ recipes-{bsp,multimedia} | wc -l
20
$ grep -r STAGING_KERNEL_ recipes-{bsp,multimedia} | sed 's/:.*//' | uniq
recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
recipes-bsp/imx-test/imx-test_git.bb
recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
recipes-bsp/imx-lib/imx-lib_git.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_git.bb
recipes-multimedia/gstreamer/imx-gst1.0-plugin_4.4.2.bb
recipes-multimedia/alsa/imx-alsa-plugins_1.0.26.bb
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH 1/2] imx-vpu-hantro: fix build issue
The source code uses LINUX_VERSION_CODE at many places which constraints
the package to be built with a toolchain whose headers match the kernel.
This is a far from ideal solution, especially if one wants to use a
prebuilt toolchain (with unknown kernel header version).
So change the CFLAGS to consider the kernel build folder so that the
Linux version test actually matches the kernel built.
Signed-off-by: Gary Bisson
---
...clusion-to-be-from-kernel-build-fold.patch | 44 +++
.../imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb| 5 ++-
2 files changed, 48 insertions(+), 1 deletion(-)
create mode 100644
recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
diff --git
a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
new file mode 100644
index ..e9bf9257
--- /dev/null
+++
b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch
@@ -0,0 +1,44 @@
+From 1d7b7046c8f735e150e92aeace3fe6d0686b9bc9 Mon Sep 17 00:00:00 2001
+From: Gary Bisson
+Date: Wed, 3 Oct 2018 10:52:29 +0200
+Subject: [PATCH] Fix version.h inclusion to be from kernel build folder
+
+Instead of relying on Toolchain headers which can be from newer kernel.
+
+Signed-off-by: Gary Bisson
+---
+ Makefile_G1G2 | 3 +++
+ Makefile_H1 | 3 +++
+ 2 files changed, 6 insertions(+)
+
+diff --git a/Makefile_G1G2 b/Makefile_G1G2
+index 29866a4..c473bcb 100755
+--- a/Makefile_G1G2
b/Makefile_G1G2
+@@ -16,6 +16,9 @@ INCLUDE_HEADERS += -I$(LINUX_KERNEL_ROOT)/include/uapi
-I$(LINUX_KERNEL_ROOT)/in
+ # ION header location
+ INCLUDE_HEADERS += -I$(LINUX_KERNEL_ROOT)/drivers/staging/android/uapi
+
++# LINUX_VERSION_CODE from kernel build folder instead of toolchain headers
++INCLUDE_HEADERS += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi
++
+ CFLAGS += -DDEC_MODULE_PATH=\"/dev/mxc_hantro\" -DUSE_FAKE_RFC_TABLE
-DFIFO_DATATYPE=void* -DNDEBUG -DDOWN_SCALER \
+-DUSE_EXTERNAL_BUFFER -DUSE_FAST_EC -DUSE_VP9_EC
-DGET_FREE_BUFFER_NON_BLOCK \
+-DDEC_X170_OUTPUT_FORMAT=0 -DDEC_X170_TIMEOUT_LENGTH=-1
-DENABLE_HEVC_SUPPORT \
+diff --git a/Makefile_H1 b/Makefile_H1
+index 56b4332..0be43ce 100755
+--- a/Makefile_H1
b/Makefile_H1
+@@ -23,6 +23,9 @@ ENV += -I$(SDKTARGETSYSROOT)/usr/imx/include
+ # ION header location
+ ENV += -I$(LINUX_KERNEL_ROOT)/drivers/staging/android/uapi
+
++# LINUX_VERSION_CODE from kernel build folder instead of toolchain headers
++INCLUDE_HEADERS += -I$(LINUX_KERNEL_BUILD)/include/generated/uapi
++
+ LIBENCNAME = libcodec_enc
+ LIBSENC = -L./ -lhantro_h1 -lpthread
+
+--
+2.19.0
+
diff --git a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
index 243f1f35..b5fc8468 100644
--- a/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
+++ b/recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb
@@ -12,6 +12,7 @@ PROVIDES = "virtual/imxvpu"
SRC_URI = " \
${FSL_MIRROR}/${PN}-${PV}.bin;fsl-eula=true \
file://0001-Fix-ion.h-header-inclusion-to-be-standard.patch \
+file://0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch \
"
SRC_URI[md5sum] = "140796ddd6f1be47cffb7e5e2bfe0fb6"
SRC_URI[sha256sum] =
"c092a5b0f8897bae54154f58e47b6d2de033da01ee231a8cd779a51bbe962606"
@@ -24,7 +25,9 @@ PLATFORM_mx8mm = "IMX8MM"
PLATFORM_mx8mq = "IMX8MQ"
do_compile () {
-oe_runmake CROSS_COMPILE="${HOST_PREFIX}"
LINUX_KERNEL_ROOT="${STAGING_KERNEL_DIR}"
SDKTARGETSYSROOT="${STAGING_DIR_TARGET}" PLATFORM="${PLATFORM}" all
+oe_runmake CROSS_COMPILE="${HOST_PREFIX}"
LINUX_KERNEL_BUILD="${STAGING_KERNEL_BUILDDIR}" \
+LINUX_KERNEL_ROOT="${STAGING_KERNEL_DIR}"
SDKTARGETSYSROOT="${STAGING_DIR_TARGET}" \
+PLATFORM="${PLATFORM}" all
}
do_install () {
--
2.19.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH 2/2] gstreamer1.0-plugins-base: fix build issue
Just like imx-vpu-hantro, this package now depends on LINUX_VERSION_CODE
which should be retrieved from kernel build folder directly instead of
relying on the toolchain kernel headers.
Signed-off-by: Gary Bisson
---
.../gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
index 3d31d22f..a9259946 100644
--- a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.14.imx.bb
@@ -67,6 +67,7 @@ EXTRA_OECONF += " \
-I${STAGING_KERNEL_DIR}/include/uapi \
-I${STAGING_KERNEL_DIR}/include \
-I${STAGING_KERNEL_DIR}/drivers/staging/android/uapi \
+-I${STAGING_KERNEL_BUILDDIR}/include/generated/uapi \
" \
"
--
2.19.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH 0/2] Fix Hantro/Gstreamer build issues
Hi Otavio/Tom/Carol, Please consider this series to fix the build of the latest multimedia components without having to change the libc-headers version. The issue currently is that the code relies on LINUX_VERSION_CODE but it uses the toolchain headers by default. So use the kernel builddir verion.h instead. If you accept this approach, please leave the ownership of the imx-vpu-hantro patch as-is as it wasn't very "open-sourcy" of you to keep my previous patch/title/log but remove my SOB/ownership... This has been tested on Nitrogen8M: - Using a 720p MIPI display (eLCDIF output) - Decoding SKYFALL trailer [1] gives 16fps only - Seems that some conf is missing to achieve 30fps like before - Here is the command used to test it: # gst-launch-1.0 filesrc location=/home/root/SKYFALL-4K.mp4 ! \ parsebin ! vpudec ! glimagesink Regards, Gary [1] http://downloads.4ksamples.com/downloads/SKYFALL%204K%20(Ultra%20HD)%20(4ksamples.com).mp4 Gary Bisson (2): imx-vpu-hantro: fix build issue gstreamer1.0-plugins-base: fix build issue ...clusion-to-be-from-kernel-build-fold.patch | 44 +++ .../imx-vpu-hantro/imx-vpu-hantro_1.8.0.bb| 5 ++- .../gstreamer1.0-plugins-base_1.14.imx.bb | 1 + 3 files changed, 49 insertions(+), 1 deletion(-) create mode 100644 recipes-bsp/imx-vpu-hantro/imx-vpu-hantro/0002-Fix-version.h-inclusion-to-be-from-kernel-build-fold.patch -- 2.19.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [distro][PATCH] layer.conf: add thud to LAYERSERIES_COMPAT
Signed-off-by: Gary Bisson
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 2990fc8..b9f7bf8 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -9,4 +9,4 @@ BBFILE_COLLECTIONS += "fsl-demos"
BBFILE_PATTERN_fsl-demos := "^${LAYERDIR}/"
BBFILE_PRIORITY_fsl-demos = "4"
-LAYERSERIES_COMPAT_fsl-demos = "sumo"
+LAYERSERIES_COMPAT_fsl-demos = "sumo thud"
--
2.19.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [distro][PATCH] Revert "fsl-base.inc: Set linux-libc-headers version to v4.9 for L4.9.123-2.3.0_8mm_ga"
This reverts commit 19c44783151e5a387c65ae837e34544b4667b9be. Since we don't plan on using the linux-libc-headers_4.9.bb recipe from NXP [1], this patch should be reverted. [1] https://lists.yoctoproject.org/pipermail/meta-freescale/2018-October/023402.html Signed-off-by: Gary Bisson --- conf/distro/include/fsl-base.inc | 4 1 file changed, 4 deletions(-) diff --git a/conf/distro/include/fsl-base.inc b/conf/distro/include/fsl-base.inc index 4505f18..67b5e61 100644 --- a/conf/distro/include/fsl-base.inc +++ b/conf/distro/include/fsl-base.inc @@ -61,10 +61,6 @@ MACHINE_GSTREAMER_1_0_PLUGIN_mx7d = "imx-gst1.0-plugin" MACHINE_GSTREAMER_1_0_PLUGIN_mx7ulp = "imx-gst1.0-plugin" MACHINE_GSTREAMER_1_0_PLUGIN_mx8mq = "imx-gst1.0-plugin" -PREFERRED_VERSION_linux-libc-headers_mx6 = "4.9" -PREFERRED_VERSION_linux-libc-headers_mx7 = "4.9" -PREFERRED_VERSION_linux-libc-headers_mx8 = "4.9" - # Use i.MX Gstreamer Version PREFERRED_VERSION_gstreamer1.0 = "1.14.imx" PREFERRED_VERSION_gstreamer1.0-plugins-base = "1.14.imx" -- 2.19.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 05/14] imx8mmevk.conf/imx-base.inc: Add i.MX 8MM EVK support
Hi Otavio,
On Mon, Oct 1, 2018 at 8:00 PM Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
> On Sun, Sep 30, 2018 at 5:56 AM Yuqing Zhu wrote:
> >
> > Signed-off-by: Yuqing Zhu
> > ---
> > conf/machine/imx8mmevk.conf | 58
> +++
> > conf/machine/include/imx-base.inc | 3 ++
> > 2 files changed, 61 insertions(+)
> > create mode 100644 conf/machine/imx8mmevk.conf
> >
> > diff --git a/conf/machine/imx8mmevk.conf b/conf/machine/imx8mmevk.conf
> > new file mode 100644
> > index 000..8d1c6e5
> > --- /dev/null
> > +++ b/conf/machine/imx8mmevk.conf
> > @@ -0,0 +1,58 @@
> > +#@TYPE: Machine
> > +#@NAME: NXP i.MX8MM Evaluation Kit
> > +#@SOC: i.MX8MM
> > +#@DESCRIPTION: Machine configuration for NXP i.MX8MMini EVK
> > +#@MAINTAINER: Jun Zhu
> > +
> > +MACHINEOVERRIDES =. "mx8:mx8mm:"
> > +
> > +require conf/machine/include/imx-base.inc
> > +require conf/machine/include/arm/arch-arm64.inc
> > +
> > +MACHINE_FEATURES += " pci wifi bluetooth optee qca9377 qca6174"
> > +
> > +MACHINE_SOCARCH_FILTER_append_mx8mm = "virtual/libopenvg
> virtual/libgles1 virtual/libgles2 virtual/egl virtual/mesa virtual/libgl
> virtual/libg2d"
> > +
> > +KERNEL_DEVICETREE = "freescale/fsl-imx8mm-evk.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-ak4497.dtb
> freescale/fsl-imx8mm-evk-ak5558.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-audio-tdm.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-inmate.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-m4.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-rm67191.dtb "
> > +KERNEL_DEVICETREE += "freescale/fsl-imx8mm-evk-root.dtb"
> > +
> > +IMAGE_BOOTFILES_DEPENDS += "imx-m4-demos:do_deploy"
> > +IMAGE_BOOTFILES += "imx8mm_m4_TCM_hello_world.bin \
> > +
> imx8mm_m4_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin \
> > +imx8mm_m4_TCM_rpmsg_lite_str_echo_rtos.bin \
> > +imx8mm_m4_TCM_sai_low_power_audio.bin \
> > +"
> > +
> > +UBOOT_CONFIG ??= "sd"
> > +UBOOT_CONFIG[sd] = "imx8mm_evk_config,sdcard"
> > +UBOOT_CONFIG[fspi] = "imx8mm_evk_fspi_defconfig"
> > +UBOOT_CONFIG[mfgtool] = "imx8mm_evk_config"
> > +SPL_BINARY = "spl/u-boot-spl.bin"
> > +
> > +# Set DDR FIRMWARE
> > +DDR_FIRMWARE_NAME = "lpddr4_pmu_train_1d_imem.bin
> lpddr4_pmu_train_1d_dmem.bin lpddr4_pmu_train_2d_imem.bin
> lpddr4_pmu_train_2d_dmem.bin"
> > +
> > +# Set u-boot DTB
> > +UBOOT_DTB_NAME = "fsl-imx8mm-evk.dtb"
> > +
> > +# Set imx-mkimage boot target
> > +IMXBOOT_TARGETS = "${@bb.utils.contains('UBOOT_CONFIG', 'fspi',
> 'flash_evk_flexspi', 'flash_evk', d)}"
> > +
> > +# Set Serial console
> > +SERIAL_CONSOLE = "115200 ttymxc1"
> > +
> > +IMAGE_BOOTLOADER = "imx-boot"
> > +
> > +BOOT_SPACE = "65536"
> > +
> > +LOADADDR = ""
> > +UBOOT_SUFFIX = "bin"
> > +UBOOT_MAKE_TARGET = ""
> > +IMX_BOOT_SEEK = "33"
> > +
> > +OPTEE_BIN_EXT = "8mm"
> > diff --git a/conf/machine/include/imx-base.inc
> b/conf/machine/include/imx-base.inc
> > index 81f521e..e4c7435 100644
> > --- a/conf/machine/include/imx-base.inc
> > +++ b/conf/machine/include/imx-base.inc
> > @@ -71,6 +71,7 @@ MACHINEOVERRIDES_EXTENDER_mx6ull =
> "imxfbdev:imxpxp:imxepdc"
> > MACHINEOVERRIDES_EXTENDER_mx7d = "imxfbdev:imxpxp:imxepdc"
> > MACHINEOVERRIDES_EXTENDER_mx7ulp =
> "imxfbdev:imxpxp:imxgpu:imxgpu2d:imxgpu3d"
> > MACHINEOVERRIDES_EXTENDER_mx8qm =
> "imxdrm:imxdpu:imxgpu:imxgpu2d:imxgpu3d"
> > +MACHINEOVERRIDES_EXTENDER_mx8mm =
> "imxdrm:imxvpu:imxgpu:imxgpu2d:imxgpu3d"
>
> This uses same as QM and below you set it to another SUFFIX. What are
> the differences?
>
No actually it isn't the same, QM has imxdpu whereas 8MM doesn't.
There are many differences between 8MM and the other 8 series. It is
closest to 8MQ but has gpu2d + vpu encoder.
I don't think we can avoid creating a new suffix.
One other difference, 8MM is the only 8 that doesn't support OpenGL3.0.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 01/14] linux-libc-headers: Use linux-libc-headers v4.9 for L4.9.123-2.3.0_8mm_ga
Hi, +1, I agree with Max that this seems like a bad idea. That is for this reason that we avoided to copy ion.h around, having the packages that need it to look directly to its default location. Can't we do the same for dma-buf.h? Regards, Gary Bisson Boundary Devices, LLC www.boundarydevices.com <http://www.BoundaryDevices.com> On Mon, Oct 1, 2018 at 11:28 AM Max Krummenacher wrote: > Hi > > Why exactly is this needed? > Forking usually is not the solution, it is the beginning of the painfull > process of merging again... > So I have strong feelings against this change. > > By changing linux-libc-headers you also change libc. So nearly everything > built becomes now machine specific. > > Regards > Max > > Note that Install-dma-buf-h.patch is not part of the SRC_URI and thus not > applied. Mainline fixed this with this commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?h=linux-4.14.y&id=2220fc1ab363e6fab1f321430d69be17a8b92bd7 > Later they made the explicit list of uapi headers even unneeded: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.14.y&id=fcc8487d477a3452a1d0ccbdd4c5e0e1e3cb8bed > > > > Am So., 30. Sep. 2018 um 10:55 Uhr schrieb Yuqing Zhu : > >> Hold linux-libc-headers v4.9 in meta-freescale layer, >> which matches the current linux-imx version in L4.9.123-2.3.0_8mm_ga. >> >> Signed-off-by: Yuqing Zhu >> --- >> .../files/Install-dma-buf-h.patch | 12 +++ >> .../linux-libc-headers/linux-libc-headers.inc | 91 >> ++ >> .../linux-libc-headers/linux-libc-headers_4.9.bb | 11 +++ >> 3 files changed, 114 insertions(+) >> create mode 100644 >> recipes-kernel/linux-libc-headers/files/Install-dma-buf-h.patch >> create mode 100644 >> recipes-kernel/linux-libc-headers/linux-libc-headers.inc >> create mode 100644 recipes-kernel/linux-libc-headers/ >> linux-libc-headers_4.9.bb >> >> diff --git >> a/recipes-kernel/linux-libc-headers/files/Install-dma-buf-h.patch >> b/recipes-kernel/linux-libc-headers/files/Install-dma-buf-h.patch >> new file mode 100644 >> index 000..285ccc4 >> --- /dev/null >> +++ b/recipes-kernel/linux-libc-headers/files/Install-dma-buf-h.patch >> @@ -0,0 +1,12 @@ >> +Index: git/include/uapi/linux/Kbuild >> +=== >> +--- git.orig/include/uapi/linux/Kbuild 2017-07-18 10:58:56.217022277 >> -0500 >> git/include/uapi/linux/Kbuild 2017-07-18 16:04:47.096019372 >> -0500 >> +@@ -104,6 +104,7 @@ >> + header-y += dlm.h >> + header-y += dlm_netlink.h >> + header-y += dlm_plock.h >> ++header-y += dma-buf.h >> + header-y += dm-ioctl.h >> + header-y += dm-log-userspace.h >> + header-y += dn.h >> diff --git a/recipes-kernel/linux-libc-headers/linux-libc-headers.inc >> b/recipes-kernel/linux-libc-headers/linux-libc-headers.inc >> new file mode 100644 >> index 000..1657df6 >> --- /dev/null >> +++ b/recipes-kernel/linux-libc-headers/linux-libc-headers.inc >> @@ -0,0 +1,91 @@ >> +SUMMARY = "Sanitized set of kernel headers for the C library's use" >> +SECTION = "devel" >> +LICENSE = "GPLv2" >> + >> +# >> +PLEASE READ >> +# >> +# >> +# You're probably looking here thinking you need to create some new copy >> +# of linux-libc-headers since you have your own custom kernel. To put >> +# this simply, you DO NOT. >> +# >> +# Why? These headers are used to build the libc. If you customise the >> +# headers you are customising the libc and the libc becomes machine >> +# specific. Most people do not add custom libc extensions to the kernel >> +# and have a machine specific libc. >> +# >> +# But you have some kernel headers you need for some driver? That is fine >> +# but get them from STAGING_KERNEL_DIR where the kernel installs itself. >> +# This will make the package using them machine specific but this is much >> +# better than having a machine specific C library. This does mean your >> +# recipe needs a >> +#do_configure[depends] += "virtual/kernel:do_shared_workdir" >> +# but again, that is fine and makes total sense. >> +# >> +# There can also be a case where your kernel extremely old and you want >> +# an older libc ABI for that old kernel. The headers instal
Re: [meta-freescale] Wayland is required for imx8?
Hi, It is a requirement since Vivante libraries all depend on gbm_viv.so which depends on libwayland: $ readelf -d gpu-core/usr/lib/*gbm_viv*.so | grep NEEDED 0x0001 (NEEDED) Shared library: [libdrm.so.2] 0x0001 (NEEDED) Shared library: [libGAL.so] 0x0001 (NEEDED) Shared library: [ *libwayland-server*.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] AFAIK, it will stay this way for i.MX8 platforms. Regards, Gary Bisson Boundary Devices, LLC www.boundarydevices.com <http://www.BoundaryDevices.com> On Sun, Sep 23, 2018 at 1:46 PM Carlos Rafael Giani wrote: > Recently I saw this in the imx-gpu-viv-6.inc file: > > REQUIRED_DISTRO_FEATURES_mx8 = "wayland" > > Since when is Wayland a requirement? What if I want to use X11? What if > I want to render directly to the framebuffer without Wayland or X11? > > Or is this just a build time dependency, and the other two are still > possible? > > -- > ___ > meta-freescale mailing list > meta-freescale@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-freescale > -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH] linux-boundary: bump revision to 0d15f927
Changelog summary:
- Includes stable v4.9.126
- Adds OV5640 MIPI support for our Nitrogen8M
- Improves SDIO perf for WiFi/BT & eMMC
- Improves SPI display support
Signed-off-by: Gary Bisson
---
recipes-kernel/linux/linux-boundary_4.9.x.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-boundary_4.9.x.bb
b/recipes-kernel/linux/linux-boundary_4.9.x.bb
index 580cd9d..2c2e2a4 100644
--- a/recipes-kernel/linux/linux-boundary_4.9.x.bb
+++ b/recipes-kernel/linux/linux-boundary_4.9.x.bb
@@ -15,6 +15,6 @@ SRC_URI =
"git://github.com/boundarydevices/linux-imx6.git;branch=${SRCBRANCH} \
LOCALVERSION = "-2.0.0-ga+yocto"
SRCBRANCH = "boundary-imx_4.9.x_2.0.0_ga"
-SRCREV = "b1200e83d3d2f673f2455073db127942c6e1e7d9"
+SRCREV = "0d15f927e8c6d1f6fa92e1905f39b03522688212"
DEPENDS += "lzop-native bc-native"
COMPATIBLE_MACHINE =
"(nitrogen6x|nitrogen6x-lite|nitrogen6sx|nitrogen7|nitrogen8m)"
--
2.19.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH] weston: install weston.ini to disable idle timeout
In order to get the same behavior as meta-fsl-bsp-release (see
weston_4.0.0.bbappend).
Signed-off-by: Gary Bisson
---
Hi,
This proved to be better not to have the display going to sleep all the
time. Also having the same behavior as NXP BSP to that regard makes
sense.
Let me know if you have any remark about it.
Regards,
Gary
---
recipes-graphics/wayland/weston_4.0.0.imx.bb | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/recipes-graphics/wayland/weston_4.0.0.imx.bb
b/recipes-graphics/wayland/weston_4.0.0.imx.bb
index 7a2aab60..372a0be3 100644
--- a/recipes-graphics/wayland/weston_4.0.0.imx.bb
+++ b/recipes-graphics/wayland/weston_4.0.0.imx.bb
@@ -109,12 +109,16 @@ do_install_append() {
if [ "${@bb.utils.contains('PACKAGECONFIG', 'xwayland', 'yes', 'no',
d)}" = "yes" ]; then
install -Dm 644 ${WORKDIR}/xwayland.weston-start
${D}${datadir}/weston-start/xwayland
fi
+
+ # install default weston.ini
+ install -d ${D}${sysconfdir}/xdg/weston
+ install -m 0644 ${B}/weston.ini ${D}${sysconfdir}/xdg/weston
}
PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'xwayland',
'${PN}-xwayland', '', d)} \
libweston-${WESTON_MAJOR_VERSION} ${PN}-examples"
-FILES_${PN} = "${bindir}/weston ${bindir}/weston-terminal
${bindir}/weston-info ${bindir}/weston-launch ${bindir}/wcap-decode
${libexecdir} ${libdir}/${BPN}/*.so ${datadir}"
+FILES_${PN} = "${bindir}/weston ${bindir}/weston-terminal
${bindir}/weston-info ${bindir}/weston-launch ${bindir}/wcap-decode
${libexecdir} ${libdir}/${BPN}/*.so ${datadir} ${sysconfdir}/xdg/weston"
FILES_libweston-${WESTON_MAJOR_VERSION} = "${libdir}/lib*${SOLIBS}
${libdir}/libweston-${WESTON_MAJOR_VERSION}/*.so"
SUMMARY_libweston-${WESTON_MAJOR_VERSION} = "Helper library for implementing
'wayland window managers'."
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH] gstreamer1.0-plugins-bad: fix build for opencv >= 3.4.2
Since OpenCV was updated to version 3.4.3 in meta-openembedded:
7b9f86ca7 opencv: Update to 3.4.3
The gstreamer-plugins from NXP is therefore out of sync and can't build
without this patch from upstream.
Signed-off-by: Gary Bisson
---
...01-opencv-fix-build-for-opencv-3-4-2.patch | 63 +++
.../gstreamer1.0-plugins-bad_1.14.imx.bb | 1 +
2 files changed, 64 insertions(+)
create mode 100644
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-opencv-fix-build-for-opencv-3-4-2.patch
diff --git
a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-opencv-fix-build-for-opencv-3-4-2.patch
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-opencv-fix-build-for-opencv-3-4-2.patch
new file mode 100644
index ..5c53e8e5
--- /dev/null
+++
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-opencv-fix-build-for-opencv-3-4-2.patch
@@ -0,0 +1,63 @@
+From c247745faaf885fd3fa094198fc0ea288e295dbf Mon Sep 17 00:00:00 2001
+From: Thibault Saunier
+Date: Fri, 13 Jul 2018 14:42:28 -0400
+Subject: [PATCH] opencv: Fix build for opencv >= 3.4.2
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+The `CV_RGB` macro is now in `imgproc.hpp`.
+
+Fixes:
+
+../subprojects/gst-plugins-bad/ext/opencv/gsthanddetect.cpp:497:40: error:
‘CV_RGB’ was not declared in this scope
+cvCircle (img, center, radius, CV_RGB (0, 0, 200), 1, 8, 0);
+^~
+---
+ ext/opencv/MotionCells.cpp | 3 +++
+ ext/opencv/gsthanddetect.cpp| 3 +++
+ ext/opencv/gsttemplatematch.cpp | 3 +++
+ 3 files changed, 9 insertions(+)
+
+diff --git a/ext/opencv/MotionCells.cpp b/ext/opencv/MotionCells.cpp
+index f85989e117..175ec901b2 100644
+--- a/ext/opencv/MotionCells.cpp
b/ext/opencv/MotionCells.cpp
+@@ -51,6 +51,9 @@
+
+ #include
+ #include "MotionCells.h"
++#if (CV_MAJOR_VERSION >= 3)
++#include
++#endif
+ #include
+
+ MotionCells::MotionCells ()
+diff --git a/ext/opencv/gsthanddetect.cpp b/ext/opencv/gsthanddetect.cpp
+index 60fd5be72b..47203fd0ea 100644
+--- a/ext/opencv/gsthanddetect.cpp
b/ext/opencv/gsthanddetect.cpp
+@@ -62,6 +62,9 @@
+
+ /* element header */
+ #include "gsthanddetect.h"
++#if (CV_MAJOR_VERSION >= 3)
++#include
++#endif
+ #include
+
+ GST_DEBUG_CATEGORY_STATIC (gst_handdetect_debug);
+diff --git a/ext/opencv/gsttemplatematch.cpp b/ext/opencv/gsttemplatematch.cpp
+index f39208dc28..ec0b56af88 100644
+--- a/ext/opencv/gsttemplatematch.cpp
b/ext/opencv/gsttemplatematch.cpp
+@@ -63,6 +63,9 @@
+
+ #include "../../gst-libs/gst/gst-i18n-plugin.h"
+ #include "gsttemplatematch.h"
++#if (CV_MAJOR_VERSION >= 3)
++#include
++#endif
+ #include
+
+ GST_DEBUG_CATEGORY_STATIC (gst_template_match_debug);
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.14.imx.bb
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.14.imx.bb
index 313d4da1..f35c825b 100644
--- a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.14.imx.bb
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.14.imx.bb
@@ -23,6 +23,7 @@ SRC_URI = " \
${GST1.0-PLUGINS-BAD_SRC};branch=${SRCBRANCH} \
file://configure-allow-to-disable-libssh2.patch \
file://0001-Makefile.am-don-t-hardcode-libtool-name-when-running.patch \
+file://0001-opencv-fix-build-for-opencv-3-4-2.patch \
"
SRCREV = "07ad0bb676a16c2dffb0f0e415a873f0924cfdc0"
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 2/2] wayland-protocols: Fix PACKAGE_ARCH for i.MX-specific version
Hi,
On Tue, Sep 11, 2018 at 9:44 AM, Andreas Müller wrote:
> On Mon, Sep 10, 2018 at 11:21 PM, Tom Hochstein wrote:
>> Fix the PACKAGE_ARCH so that our i.MX-specific version does not
>> override the standard allarch version.
>>
>> Signed-off-by: Tom Hochstein
>> ---
>> recipes-graphics/wayland/wayland-protocols_1.13.imx.bb | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/recipes-graphics/wayland/wayland-protocols_1.13.imx.bb
>> b/recipes-graphics/wayland/wayland-protocols_1.13.imx.bb
>> index c2ea68e..c722371 100644
>> --- a/recipes-graphics/wayland/wayland-protocols_1.13.imx.bb
>> +++ b/recipes-graphics/wayland/wayland-protocols_1.13.imx.bb
>> @@ -17,7 +17,9 @@ SRC_URI[md5sum] = "29312149dafcd4a0e739ba94995a574d"
>> SRC_URI[sha256sum] =
>> "0758bc8008d5332f431b2a84fea7de64d971ce270ed208206a098ff2ebc68f38"
>> S = "${WORKDIR}/${ARCHIVE_NAME}"
>>
>> -inherit allarch autotools pkgconfig
>> +inherit autotools pkgconfig
>>
>> PACKAGES = "${PN}"
>> FILES_${PN} += "${datadir}/pkgconfig/wayland-protocols.pc"
>> +
>> +PACKAGE_ARCH = "${MACHINE_SOCARCH}"
>> --
>> 2.7.4
>>
>> --
> This does not fix the problem. Tested for:
>
> * MACHINE = "imx6qdl-variscite-som" / MACHINEOVERRIDES .= ":use-mainline-bsp"
> * raspberrypi3
>
> For both is builds wayland-protocols_1.13.imx. So now the situation is
> even worth: It builds fine but the wrong version of wayland protocols.
> I think we need something like wayland-protocols-imx and
> PREFERRED_PROVIDER solution
The preferred_provider should indeed fix the use-mainline-bsp usecase.
However I wonder why we need such recipe, wouldn't a bbappend to the
wayland protocol recipe be sufficient?
Looking at the patches, they could actually be brought down to 2 patches:
1- add hdr10-metadata protocol
2- add alpha-compositing protocol
Those patches really are not intrusive so I'm pretty sure they'd apply
nicely on any version of wayland-protocol.
Or maybe using the upstream version breaks things?
As a FYI, I revived the alpha-compositing thread upstream so that it
could be merged someday [1].
Tom, is there any plan to upstream the hdr10-metadata protocol?
Regards,
Gary
[1] https://patchwork.freedesktop.org/patch/170804/
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [v3,04/43] weston: Fix non-GPU support
Hi Tom, On Fri, Sep 07, 2018 at 01:26:36PM +, Tom Hochstein wrote: > > > > -Original Message- > > From: Gary Bisson > > Sent: Friday, September 7, 2018 7:19 AM > > To: Tom Hochstein > > Cc: meta-freescale@yoctoproject.org > > Subject: Re: [v3,04/43] weston: Fix non-GPU support > > > > Hi Tom, > > > > On Fri, Sep 07, 2018 at 11:41:35AM +, Tom Hochstein wrote: > > > Hi Gary, > > > > > > The problem is the upstreaming is incomplete. > > > > Which upstreaming are you talking about? weston-imx or meta-freescale? > > meta-freescale > > > > > I understand that not all the components are in meta-freescale yet but do > > not understand how can the weston-imx be built when files are missing. I > > still > > believe there's an issue with weston-imx branch as it is today. > > We are patching wayland-protocols, adding HDR10 metadata and alpha > compositing protocols. I believe that should fix the build break you see. Indeed, you're right that should fix it. I could wrap my head around the fact that weston includes files that aren't there (wasn't aware of the wayland-protocols). > > > I am working with Otavio on another set of patches that will fix this. > > > > Ok, do you have an ETA on this? I'm asking because master is currently the > > only branch that can be built for i.MX8M platforms. > > Hopefully today. I need to update my pull request to Otavio, then he will > take it from there. Awesome, I'll make sure to test your series (worst case on Monday). Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [v3,04/43] weston: Fix non-GPU support
Hi Tom, On Fri, Sep 07, 2018 at 11:41:35AM +, Tom Hochstein wrote: > Hi Gary, > > The problem is the upstreaming is incomplete. Which upstreaming are you talking about? weston-imx or meta-freescale? I understand that not all the components are in meta-freescale yet but do not understand how can the weston-imx be built when files are missing. I still believe there's an issue with weston-imx branch as it is today. > I am working with Otavio on another set of patches that will fix this. Ok, do you have an ETA on this? I'm asking because master is currently the only branch that can be built for i.MX8M platforms. Right now it cannot builb an image with Weston for i.MX8M/i.MX6x solely because of this patch... Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [v3,04/43] weston: Fix non-GPU support
Hi Tom, On Tue, Aug 07, 2018 at 10:41:56AM -0500, Tom Hochstein wrote: > The desktop failed to start on i.MX parts without GPU. The problem > is fixed, and now the package must be configured for i.MX GPU > support. > > Signed-off-by: Tom Hochstein > --- > recipes-graphics/wayland/weston_4.0.0.imx.bb | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/recipes-graphics/wayland/weston_4.0.0.imx.bb > b/recipes-graphics/wayland/weston_4.0.0.imx.bb > index fc6a65f..7a2aab6 100644 > --- a/recipes-graphics/wayland/weston_4.0.0.imx.bb > +++ b/recipes-graphics/wayland/weston_4.0.0.imx.bb > @@ -15,7 +15,7 @@ SRC_URI = > "git://source.codeaurora.org/external/imx/weston-imx.git;protocol=http > file://xwayland.weston-start \ > > file://0001-weston-launch-Provide-a-default-version-that-doesn-t.patch \ > " > -SRCREV = "bf74309dd16d86537ff07eabf8b499cb2d25277d" > +SRCREV = "642006cbd89e7ae51a7ce672c899614814dc4ef0" Have you tested this patch only with a non-GPU configuration? Because this revision simply fails to build currently for configuration with GPU, giving the following error: | make: *** No rule to make target 'protocol/alpha-compositing-unstable-v1-protocol.c', needed by 'all'. Stop. | ERROR: oe_runmake failed And indeed the source code seems broken as this patch relies on files that were not pushed: https://source.codeaurora.org/external/imx/weston-imx/commit/?id=26172d61 It's missing: protocol/alpha-compositing-unstable-v1-protocol.c protocol/alpha-compositing-unstable-v1-client-protocol.h protocol/alpha-compositing-unstable-v1-server-protocol.h Please have the Weston team add the missing files or submit a revert patch to meta-freescale. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH] Revert "wayland: Remove file provided by imx-gpu-viv"
This reverts commit 3be51cd536cfb08e95e852ddfdb180a51798b1f0.
This fixes the following issue:
| No package 'wayland-egl' found
Reason is that 3be51cd5 should have been removed as soon as the
following commit was pushed:
f1e39bd1 imx-gpu-viv: Remove wayland-egl files
Since imx-gpu-viv doesn't provide wayland-egl any longer, wayland
recipe has to.
Signed-off-by: Gary Bisson
---
recipes-graphics/wayland/wayland_1.15.%.bbappend | 4
1 file changed, 4 deletions(-)
delete mode 100644 recipes-graphics/wayland/wayland_1.15.%.bbappend
diff --git a/recipes-graphics/wayland/wayland_1.15.%.bbappend
b/recipes-graphics/wayland/wayland_1.15.%.bbappend
deleted file mode 100644
index 31fc0aa6..
--- a/recipes-graphics/wayland/wayland_1.15.%.bbappend
+++ /dev/null
@@ -1,4 +0,0 @@
-# Remove files provided by imx-gpu-viv
-do_install_append_imxgpu () {
-rm -f ${D}${libdir}/pkgconfig/wayland-egl.pc
-}
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 50/52] imx-vpu-hantro: Update to 1.7.0
Hi Tom,
On Fri, Aug 24, 2018 at 9:45 PM, Tom Hochstein
wrote:
>
>
> > -Original Message-
> > From: Tom Hochstein
> > Sent: Tuesday, July 31, 2018 2:44 PM
>
>
> > > -Original Message-
> > > From: Gary Bisson [mailto:gary.bis...@boundarydevices.com]
> > > Sent: Tuesday, July 31, 2018 1:54 AM
>
>
> > > > recipes-bsp/imx-vpu-hantro/{imx-vpu-hantro-1.6.0 =>
> > > > imx-vpu-hantro}/0001-Fix-ion.h-header-inclusion-to-be-standard.patch
> > > > (71%)
> > >
> > > Thanks for porting the patch over. Any chance to get it in the
> > > upstream repo in the future?
> >
> > Thanks for pointing this out. I will get the process started now.
>
> I have misgivings about this patch. The problem is we have packages that
> use ion.h that are applicable to both Android and Linux. Having ion.h live
> in two different locations means we have to complicate the packages.
>
> Isn't it better to just adopt the Android model and install
> /usr/include/linux/ion.h in our linux-imx kernel?
>
Android doesn't actually use ion.h from the kernel but relies on the one
present in the AOSP already (original kernel-headers or bionic libc).
If you want we can have something like:
#ifdef ANDROID
#include
#include
else
#include
#endif
That would cover both cases but I understand what you are saying. I just
wish the staging headers would be installed normally in the first place.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 01/43] xserver-xf86-config: Add support for i.MX 8MQ
Hi Tom, Have you tested this patch on an actual i.MX8MQ platform? Isn't the "vivante" driver mentioned in xorg.conf referring to xf86-video-imx-vivante which cannot be built for i.MX8MQ since it requires libg2d? Moreover since imx-gpu-viv has no x11 backend for i.MX8 I'm curious about how this actually works. https://community.nxp.com/thread/473905#comment-1005537 Regards, Gary Bisson Boundary Devices, LLC www.boundarydevices.com On Mon, Aug 6, 2018 at 10:03 PM, Tom Hochstein wrote: > Add DRM driver. > > Signed-off-by: Tom Hochstein > --- > .../xorg-xserver/xserver-xf86-config/imxdrm/xorg.conf | 15 > +++ > 1 file changed, 15 insertions(+) > create mode 100644 > recipes-graphics/xorg-xserver/xserver-xf86-config/imxdrm/xorg.conf > > diff --git > a/recipes-graphics/xorg-xserver/xserver-xf86-config/imxdrm/xorg.conf > b/recipes-graphics/xorg-xserver/xserver-xf86-config/imxdrm/xorg.conf > new file mode 100644 > index 000..ec12ed9 > --- /dev/null > +++ b/recipes-graphics/xorg-xserver/xserver-xf86-config/imxdrm/xorg.conf > @@ -0,0 +1,15 @@ > +Section "Device" > +Identifier "i.MX Accelerated DRM Device" > +Driver "vivante" > +Option "kmsdev" "/dev/dri/card0" > +EndSection > + > +Section "ServerFlags" > +Option "BlankTime" "0" > +Option "StandbyTime" "0" > +Option "SuspendTime" "0" > +Option "OffTime" "0" > +Option "Xinerama" "off" > +Option "Clone" "on" > +Option "SWcursor" "true" > +EndSection > -- > 2.7.4 > > -- > ___ > meta-freescale mailing list > meta-freescale@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-freescale -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 43/43] imx-vpu: Clarify compatibility for Chips&Media VPU
Hi Tom,
Is there any plan to rename that package to match what is done for hantro?
imx-vpu-
Wouldn't it be clearer to people to have virtual/imxvpu being backed
by either imx-vpu-hantro or imx-vpu-cnm (or chipsnmedia)?
Regards,
Gary Bisson
Boundary Devices, LLC
www.boundarydevices.com
On Mon, Aug 6, 2018 at 10:05 PM, Tom Hochstein wrote:
> Signed-off-by: Tom Hochstein
> ---
> recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
> b/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
> index f0c9d5a..d886e30 100644
> --- a/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
> +++ b/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb
> @@ -1,8 +1,8 @@
> # Copyright (C) 2013-2018 O.S. Systems Software LTDA.
> # Copyright (C) 2013-2016 Freescale Semiconductor
> -# Copyright 2017 NXP
> +# Copyright 2017-2018 NXP
>
> -DESCRIPTION = "Freescale VPU library"
> +DESCRIPTION = "Freescale Chips&Media VPU library"
> LICENSE = "Proprietary"
> LIC_FILES_CHKSUM = "file://COPYING;md5=75abe2fa1d16ca79f87cde926f05f72d"
>
> @@ -32,4 +32,4 @@ do_install () {
> }
>
> PACKAGE_ARCH = "${MACHINE_ARCH}"
> -COMPATIBLE_MACHINE = "(mx6)"
> +COMPATIBLE_MACHINE = "(mx6q|mx6dl)"
> --
> 2.7.4
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Question about Hantro and Amphion hardware codecs
Hi Carlos, On Thu, Aug 2, 2018 at 9:50 AM, Carlos Rafael Giani wrote: > I saw in the imx-vpu-hantro and imx gst plugins packages that both Hantro > and Amphion were mentioned. > > I remember that the imx8m only has a hantro decoder. But apparently there > is also a Hantro encoder. And there is also an "Amphion" codec? > > Where are the Amphion codec and the Hantro encoder used? Is Amphion > reserved for imx8 mini? >From what I saw: - Amphion (VPU "malone) is the IP used in i.MX8QM and i.MX8QXP - Hantro encoder is used i.MX8MMini Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 04/52] imx-dpu-g2d: Limit to i.MX 8MQ support
Hi Tom,
I believe the title is wrong, i.MX8MQ doesn't support the DPU (neither
does i.MX8MM actually).
Do you mean i.MX8QM?
On Mon, Jul 30, 2018 at 9:41 PM, Tom Hochstein wrote:
> Signed-off-by: Tom Hochstein
> ---
> recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> index dd3aa9d..af4fdd0 100644
> --- a/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> +++ b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> @@ -34,4 +34,5 @@ INSANE_SKIP_${PN} += "ldflags"
> FILES_${PN} = "${libdir}/libg2d* /opt"
> FILES_${PN}-dev = "${libdir}/libg2d${SOLIBSDEV} ${includedir}"
>
> -COMPATIBLE_MACHINE = "(mx8mm)"
> +COMPATIBLE_MACHINE = "(^$)"
> +COMPATIBLE_MACHINE_imxgpu2d = "(mx8)"
What is it depending on imxgpu2d?
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 50/52] imx-vpu-hantro: Update to 1.7.0
Hi Tom,
On Mon, Jul 30, 2018 at 02:44:09PM -0500, Tom Hochstein wrote:
Can you provide a changelog for this version bump?
> Signed-off-by: Tom Hochstein
> ---
> ...Fix-ion.h-header-inclusion-to-be-standard.patch | 37
> ++
> recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.6.0.bb | 33 ---
> recipes-bsp/imx-vpu-hantro/imx-vpu-hantro_1.7.0.bb | 35
> 3 files changed, 52 insertions(+), 53 deletions(-)
> rename recipes-bsp/imx-vpu-hantro/{imx-vpu-hantro-1.6.0 =>
> imx-vpu-hantro}/0001-Fix-ion.h-header-inclusion-to-be-standard.patch (71%)
Thanks for porting the patch over. Any chance to get it in the upstream
repo in the future?
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH] utilities.inc: Use only the basename for dtb files
Hi Fabio, On Fri, Jul 20, 2018 at 10:45 PM, Fabio Berton wrote: > Use make_dtb_boot_files function to use basename from > KERNEL_DEVICETREE files. This is useful for dtb with name: > > whatever/my_dtb_file.dtb > > Signed-off-by: Fabio Berton Tested-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH][sumo 4/4] linux-boundary: bump revision to 46f9b57b
Changelog is too long but as a summary:
- Merged stable release up to 4.9.88
- Improved capture driver to work with v4l2src
- Add yet another LDB clock parent
- Improved MIPI DSI support for i.MX6
Signed-off-by: Gary Bisson
---
recipes-kernel/linux/linux-boundary_4.9.x.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-boundary_4.9.x.bb
b/recipes-kernel/linux/linux-boundary_4.9.x.bb
index 9cbfb91..8c5b540 100644
--- a/recipes-kernel/linux/linux-boundary_4.9.x.bb
+++ b/recipes-kernel/linux/linux-boundary_4.9.x.bb
@@ -11,6 +11,6 @@ SRC_URI =
"git://github.com/boundarydevices/linux-imx6.git;branch=${SRCBRANCH} \
LOCALVERSION = "-1.0.0-ga+yocto"
SRCBRANCH = "boundary-imx_4.9.x_1.0.0_ga"
-SRCREV = "ec68e473bd4fb32357103668ebaad38b3a543352"
+SRCREV = "46f9b57bc9312834a51e589cac1a3517cad56a96"
DEPENDS += "lzop-native bc-native"
COMPATIBLE_MACHINE = "(nitrogen6x|nitrogen6x-lite|nitrogen6sx|nitrogen7)"
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH][sumo 2/4] nitrogen*.conf: switch to standard boot.scr script
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen6sx.conf | 2 +-
conf/machine/nitrogen6x-lite.conf | 2 +-
conf/machine/nitrogen6x.conf | 2 +-
conf/machine/nitrogen7.conf | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf
index 1dec579..c526ba9 100644
--- a/conf/machine/nitrogen6sx.conf
+++ b/conf/machine/nitrogen6sx.conf
@@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??=
"linux-fslc"
# wic support
WKS_FILE = "sdimage-bootpart.wks"
IMAGE_BOOT_FILES_append = " \
-6x_bootscript-${MACHINE};6x_bootscript \
+boot.scr-${MACHINE};boot.scr \
"
WKS_FILE_DEPENDS = " \
u-boot-script-boundary \
diff --git a/conf/machine/nitrogen6x-lite.conf
b/conf/machine/nitrogen6x-lite.conf
index 04b24eb..470c800 100644
--- a/conf/machine/nitrogen6x-lite.conf
+++ b/conf/machine/nitrogen6x-lite.conf
@@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??=
"linux-fslc"
# wic support
WKS_FILE = "sdimage-bootpart.wks"
IMAGE_BOOT_FILES_append = " \
-6x_bootscript-${MACHINE};6x_bootscript \
+boot.scr-${MACHINE};boot.scr \
"
WKS_FILE_DEPENDS = " \
u-boot-script-boundary \
diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf
index 9073d80..ff52561 100644
--- a/conf/machine/nitrogen6x.conf
+++ b/conf/machine/nitrogen6x.conf
@@ -53,7 +53,7 @@ PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??=
"linux-fslc"
# wic support
WKS_FILE = "sdimage-bootpart.wks"
IMAGE_BOOT_FILES_append = " \
-6x_bootscript-${MACHINE};6x_bootscript \
+boot.scr-${MACHINE};boot.scr \
"
WKS_FILE_DEPENDS = " \
u-boot-script-boundary \
diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf
index 0f1a58e..388c4a3 100644
--- a/conf/machine/nitrogen7.conf
+++ b/conf/machine/nitrogen7.conf
@@ -19,7 +19,7 @@ PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??=
"linux-fslc"
# wic support
WKS_FILE = "sdimage-bootpart.wks"
IMAGE_BOOT_FILES_append = " \
-6x_bootscript-${MACHINE};6x_bootscript \
+boot.scr-${MACHINE};boot.scr \
"
WKS_FILE_DEPENDS = " \
u-boot-script-boundary \
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH][sumo 3/4] nitrogen*.conf: fix u-boot preferred provider
And switch to defconfig as now supported in v2017.07 release. The missing virtual/bootloader variable was generating the following error: $ bitbake u-boot-boundary ... ERROR: Nothing PROVIDES 'u-boot-boundary' u-boot-boundary was skipped: PREFERRED_PROVIDER_virtual/bootloader set to u-boot-fslc, not u-boot-boundary u-boot-boundary was skipped: incompatible with machine nitrogen6x (not in COMPATIBLE_MACHINE) Signed-off-by: Gary Bisson --- conf/machine/nitrogen6sx.conf | 5 +++-- conf/machine/nitrogen6x-lite.conf | 5 +++-- conf/machine/nitrogen6x.conf | 5 +++-- conf/machine/nitrogen7.conf | 5 +++-- 4 files changed, 12 insertions(+), 8 deletions(-) diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf index c526ba9..9aa43d4 100644 --- a/conf/machine/nitrogen6sx.conf +++ b/conf/machine/nitrogen6sx.conf @@ -12,7 +12,8 @@ include conf/machine/include/tune-cortexa9.inc KERNEL_DEVICETREE = "imx6sx-nitrogen6sx.dtb" KERNEL_IMAGETYPE = "zImage" -PREFERRED_PROVIDER_u-boot = "u-boot-boundary" +PREFERRED_PROVIDER_u-boot ??= "u-boot-boundary" +PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot-boundary" PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" @@ -28,7 +29,7 @@ WKS_FILE_DEPENDS = " \ bmap-tools-native \ " -UBOOT_MACHINE ?= "nitrogen6sx_config" +UBOOT_MACHINE ?= "nitrogen6sx_defconfig" SERIAL_CONSOLE = "115200 ttymxc0" diff --git a/conf/machine/nitrogen6x-lite.conf b/conf/machine/nitrogen6x-lite.conf index 470c800..44cf5c2 100644 --- a/conf/machine/nitrogen6x-lite.conf +++ b/conf/machine/nitrogen6x-lite.conf @@ -12,7 +12,8 @@ include conf/machine/include/tune-cortexa9.inc KERNEL_DEVICETREE = "imx6dl-nit6xlite.dtb" KERNEL_IMAGETYPE = "zImage" -PREFERRED_PROVIDER_u-boot = "u-boot-boundary" +PREFERRED_PROVIDER_u-boot ??= "u-boot-boundary" +PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot-boundary" PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" @@ -28,7 +29,7 @@ WKS_FILE_DEPENDS = " \ bmap-tools-native \ " -UBOOT_MACHINE ?= "nit6xlite_config" +UBOOT_MACHINE ?= "nit6xlite_defconfig" SERIAL_CONSOLE = "115200 ttymxc1" diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf index ff52561..e777a14 100644 --- a/conf/machine/nitrogen6x.conf +++ b/conf/machine/nitrogen6x.conf @@ -46,7 +46,8 @@ KERNEL_DEVICETREE_remove_use-mainline-bsp = "imx6dl-nitrogen6_vm.dtb imx6dl-nitr KERNEL_IMAGETYPE = "zImage" -PREFERRED_PROVIDER_u-boot = "u-boot-boundary" +PREFERRED_PROVIDER_u-boot ??= "u-boot-boundary" +PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot-boundary" PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" @@ -62,7 +63,7 @@ WKS_FILE_DEPENDS = " \ bmap-tools-native \ " -UBOOT_MACHINE ?= "nitrogen6q_config" +UBOOT_MACHINE ?= "nitrogen6q_defconfig" SERIAL_CONSOLE = "115200 ttymxc1" diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf index 388c4a3..57160e0 100644 --- a/conf/machine/nitrogen7.conf +++ b/conf/machine/nitrogen7.conf @@ -12,7 +12,8 @@ require conf/machine/include/tune-cortexa7.inc KERNEL_DEVICETREE = "imx7d-nitrogen7.dtb" KERNEL_IMAGETYPE = "zImage" -PREFERRED_PROVIDER_u-boot = "u-boot-boundary" +PREFERRED_PROVIDER_u-boot ??= "u-boot-boundary" +PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot-boundary" PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" @@ -28,7 +29,7 @@ WKS_FILE_DEPENDS = " \ bmap-tools-native \ " -UBOOT_MACHINE ?= "nitrogen7_config" +UBOOT_MACHINE ?= "nitrogen7_defconfig" SERIAL_CONSOLE = "115200 ttymxc0" -- 2.18.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH][sumo 0/4] Update Boundary Devices paltforms
Hi,
This series updates the U-Boot and Kernel versions for Boundary Devices
platforms.
Main change is the switch to U-Boot v2017.07 which now uses the standard
bootdistro commands/variables. Therefore the 6x_bootscript/6x_upgrade
scripts are deprecated in favor of more generic boot.scr.
Let me know if you have any question.
Regards,
Gary
Gary Bisson (4):
u-boot-boundary: bump version to v2017.07
nitrogen*.conf: switch to standard boot.scr script
nitrogen*.conf: fix u-boot preferred provider
linux-boundary: bump revision to 46f9b57b
conf/machine/nitrogen6sx.conf | 7 +--
conf/machine/nitrogen6x-lite.conf | 7 +--
conf/machine/nitrogen6x.conf | 7 +--
conf/machine/nitrogen7.conf | 7 +--
...inc => u-boot-boundary-common_2017.07.inc} | 6 +--
.../default-gcc.patch | 39 --
...bb => u-boot-boundary-fw-utils_2017.07.bb} | 1 -
..._2016.03.bb => u-boot-boundary_2017.07.bb} | 0
.../u-boot/u-boot-script-boundary_2016.03.bb | 54 ---
.../u-boot/u-boot-script-boundary_2017.07.bb | 45
recipes-kernel/linux/linux-boundary_4.9.x.bb | 2 +-
11 files changed, 65 insertions(+), 110 deletions(-)
rename recipes-bsp/u-boot/{u-boot-boundary-common_2016.03.inc =>
u-boot-boundary-common_2017.07.inc} (72%)
delete mode 100644
recipes-bsp/u-boot/u-boot-boundary-fw-utils/default-gcc.patch
rename recipes-bsp/u-boot/{u-boot-boundary-fw-utils_2016.03.bb =>
u-boot-boundary-fw-utils_2017.07.bb} (97%)
rename recipes-bsp/u-boot/{u-boot-boundary_2016.03.bb =>
u-boot-boundary_2017.07.bb} (100%)
delete mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_2016.03.bb
create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_2017.07.bb
--
2.18.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH][sumo 1/4] u-boot-boundary: bump version to v2017.07
Brings many updates/fixes, most important one being the use of standard
bootdistro commands/variables.
Therefore the legacy 6x_bootscript/upgrade scripts have been removed in
favor of boot.scr and upgrade.scr.
Also, the HOSTCC patch isn't needed anymore since included in mainline
U-Boot.
Signed-off-by: Gary Bisson
---
...inc => u-boot-boundary-common_2017.07.inc} | 6 +--
.../default-gcc.patch | 39 --
...bb => u-boot-boundary-fw-utils_2017.07.bb} | 1 -
..._2016.03.bb => u-boot-boundary_2017.07.bb} | 0
.../u-boot/u-boot-script-boundary_2016.03.bb | 54 ---
.../u-boot/u-boot-script-boundary_2017.07.bb | 45
6 files changed, 48 insertions(+), 97 deletions(-)
rename recipes-bsp/u-boot/{u-boot-boundary-common_2016.03.inc =>
u-boot-boundary-common_2017.07.inc} (72%)
delete mode 100644
recipes-bsp/u-boot/u-boot-boundary-fw-utils/default-gcc.patch
rename recipes-bsp/u-boot/{u-boot-boundary-fw-utils_2016.03.bb =>
u-boot-boundary-fw-utils_2017.07.bb} (97%)
rename recipes-bsp/u-boot/{u-boot-boundary_2016.03.bb =>
u-boot-boundary_2017.07.bb} (100%)
delete mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_2016.03.bb
create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_2017.07.bb
diff --git a/recipes-bsp/u-boot/u-boot-boundary-common_2016.03.inc
b/recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
similarity index 72%
rename from recipes-bsp/u-boot/u-boot-boundary-common_2016.03.inc
rename to recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
index 1dc609a..4263fa1 100644
--- a/recipes-bsp/u-boot/u-boot-boundary-common_2016.03.inc
+++ b/recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
@@ -2,10 +2,10 @@ DESCRIPTION = "U-Boot for Boundary Devices boards"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
-PV = "v2016.03+git${SRCPV}"
+PV = "v2017.07+git${SRCPV}"
-SRCREV = "0dbffd30b6a81b53c8a4780490ea625ccbfa5596"
-SRCBRANCH = "boundary-v2016.03"
+SRCREV = "445823ef2abfff2fc1c63cc53c57c1e139f88b1b"
+SRCBRANCH = "boundary-v2017.07"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
S = "${WORKDIR}/git"
diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils/default-gcc.patch
b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/default-gcc.patch
deleted file mode 100644
index 04184df..000
--- a/recipes-bsp/u-boot/u-boot-boundary-fw-utils/default-gcc.patch
+++ /dev/null
@@ -1,39 +0,0 @@
-OE needs to be able to change the default compiler. If we pass in HOSTCC
-through the make command, it overwrites not only this setting but also the
-setting in tools/Makefile wrapped in ifneq ($(CROSS_BUILD_TOOLS),) which
-breaks the build.
-
-We therefore use override to ensure the value of HOSTCC is overwritten when
-needed.
-
-RP: Updated the patch to the version being submitted to upstream u-boot
-
-Upstream-Status: Submitted [emailed to Masahiro Yamada for discussion]
-RP 2017/3/11
-
-Index: git/tools/Makefile
-===
git.orig/tools/Makefile
-+++ git/tools/Makefile
-@@ -262,7 +262,7 @@ $(LICENSE_H): $(obj)/bin2header $(srctre
- subdir- += env
-
- ifneq ($(CROSS_BUILD_TOOLS),)
--HOSTCC = $(CC)
-+override HOSTCC = $(CC)
-
- quiet_cmd_crosstools_strip = STRIP $^
- cmd_crosstools_strip = $(STRIP) $^; touch $@
-Index: git/tools/env/Makefile
-===
git.orig/tools/env/Makefile
-+++ git/tools/env/Makefile
-@@ -8,7 +8,7 @@
- # fw_printenv is supposed to run on the target system, which means it should
be
- # built with cross tools. Although it may look weird, we only replace "HOSTCC"
- # with "CC" here for the maximum code reuse of scripts/Makefile.host.
--HOSTCC = $(CC)
-+override HOSTCC = $(CC)
-
- # Compile for a hosted environment on the target
- HOST_EXTRACFLAGS = $(patsubst -I%,-idirafter%, $(filter -I%,
$(UBOOTINCLUDE))) \
diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2016.03.bb
b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
similarity index 97%
rename from recipes-bsp/u-boot/u-boot-boundary-fw-utils_2016.03.bb
rename to recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
index fa0718b..f5dd879 100644
--- a/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2016.03.bb
+++ b/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2017.07.bb
@@ -4,7 +4,6 @@ SUMMARY = "U-Boot bootloader fw_printenv/setenv utilities"
DEPENDS = "mtd-utils"
SRC_URI += " \
- file://default-gcc.patch \
file://fw_env.config \
"
diff --git a/recipes-bsp/u-boot/u-boot-boundary_2016.03.bb
b/recipes-bsp/u-boot/u-boot-boundary_2017.07.bb
similarity index 100%
rename from recipes-bsp/u-boot/u-boot-boundary_2016.03.bb
re
Re: [meta-freescale] [PATCH v2 04/19] imx-gpu-viv: Add i.MX 8 support
Hi Ian,
Le jeu. 28 juin 2018 à 1:48 AM, Ian Coolidge a
écrit :
> Just as a follow up...
>
> core-image-weston is unbuildable due to some libdrm issue it looks like:
>
> | ../git/libweston/compositor-drm.c: In function 'drm_fb_addfb':
> | ../git/libweston/compositor-drm.c:907:23: error:
> 'DRM_FORMAT_MOD_AMPHION_TILED' undeclared (first use in this function); did
> you mean 'DRM_FORMAT_MOD_VIVANTE_TILED'?
> |if (fb->modifier == DRM_FORMAT_MOD_AMPHION_TILED) {
> |^~~~
> |DRM_FORMAT_MOD_VIVANTE_TILED
> | ../git/libweston/compositor-drm.c:907:23: note: each undeclared
> identifier is reported only once for each function it appears in
> | ../git/libweston/compositor-drm.c: In function 'drm_assign_planes':
> | ../git/libweston/compositor-drm.c:3383:37: error: 'DRM_FORMAT_P010'
> undeclared (first use in this function); did you mean 'DRM_FORMAT_R16'?
> | || dmabuf->attributes.format == DRM_FORMAT_P010)
> | ^~~
> | DRM_FORMAT_R16
>
> Which I'm guessing can't be a coincidence.
>
That's because you need libdrm-imx from codeaurora that matches the weston
version.
https://source.codeaurora.org/external/imx/libdrm-imx/
Regards,
Gary
>
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 30/32] imx-base.inc: Add imxdpu and imxdpublit to MACHINEOVERRIDES_EXTENDER
Hi Tom, On Wed, Jun 27, 2018 at 02:00:29PM +, Tom Hochstein wrote: > After thinking on this some more, let me start over. > > > -Original Message- > > From: meta-freescale-boun...@yoctoproject.org [mailto:meta-freescale- > > boun...@yoctoproject.org] On Behalf Of Gary Bisson > > Sent: Tuesday, June 26, 2018 3:20 AM > > To: Otavio Salvador > > Cc: meta-freescale Mailing List > > Subject: Re: [meta-freescale] [PATCH 30/32] imx-base.inc: Add imxdpu and > > imxdpublit to MACHINEOVERRIDES_EXTENDER > > > > Hi Otavio, Tom, > > > > On Mon, Jun 25, 2018 at 04:30:30PM -0300, Otavio Salvador wrote: > > > From: Tom Hochstein > > > > > > - imx-gpu-g2d requires DPU-blit support > > > > Can you elaborate on that? What has changed in the g2d package so that it > > now depends on DPU-blit? > > Nothing has changed, this just makes an existing requirement explicit. i.MX 6 > and 7 with 2D GPU do in fact have a separate DPU blitting engine, different > from the DPU used for i.MX 8. What does "DPU" mean to you? I think what you mean is "i.MX6 and 7 can do 2D blit operations with their 2D GPU". Using the term DPU doesn't make sense to me, please elaborate. My definition of DPU is "Display Processing Unit" as defined in i.MX8QM docs, therefore using the same term for CPU that don't have that IP is confusing, isn't it? > > > - imx-dpu-g2d requires DPU support > > > > > > Signed-off-by: Tom Hochstein > > > Signed-off-by: Otavio Salvador > > > --- > > > > > > conf/machine/include/imx-base.inc | 14 +++--- > > > recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb | 4 +++- > > > .../imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb | 4 +++- > > > 3 files changed, 13 insertions(+), 9 deletions(-) > > > > > > diff --git a/conf/machine/include/imx-base.inc > > > b/conf/machine/include/imx-base.inc > > > index 346d1c77..6ba5014d 100644 > > > --- a/conf/machine/include/imx-base.inc > > > +++ b/conf/machine/include/imx-base.inc > > > @@ -59,17 +59,17 @@ DEFAULTTUNE_vf ?= "cortexa5thf-neon" > > > INHERIT += "machine-overrides-extender" > > > > > > MACHINEOVERRIDES_EXTENDER_mx25 = "use-mainline-bsp" > > > -MACHINEOVERRIDES_EXTENDER_mx6q = > > "imxipu:imxvpu:imxgpu2d:imxgpu3d" > > > -MACHINEOVERRIDES_EXTENDER_mx6dl = > > "imxpxp:imxipu:imxvpu:imxgpu2d:imxgpu3d:imxepdc" > > > -MACHINEOVERRIDES_EXTENDER_mx6sx = "imxpxp:imxgpu2d:imxgpu3d" > > > -MACHINEOVERRIDES_EXTENDER_mx6sl = "imxpxp:imxgpu2d:imxepdc" > > > +MACHINEOVERRIDES_EXTENDER_mx6q = > > "imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d" > > > +MACHINEOVERRIDES_EXTENDER_mx6dl = > > "imxpxp:imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d:imxepdc" > > > +MACHINEOVERRIDES_EXTENDER_mx6sx = > > "imxpxp:imxgpu2d:imxdpublit:imxgpu3d" > > > +MACHINEOVERRIDES_EXTENDER_mx6sl = > > "imxpxp:imxgpu2d:imxdpublit:imxepdc" > > > > ?? I don't understand that naming at all. Shouldn't imxdpublit be necessary > > on HW that has a DPU (ie none of the above)? > > > > > MACHINEOVERRIDES_EXTENDER_mx6sll = "imxpxp:imxepdc" > > > MACHINEOVERRIDES_EXTENDER_mx6ul = "imxpxp" > > > MACHINEOVERRIDES_EXTENDER_mx6ull = "imxpxp:imxepdc" > > > MACHINEOVERRIDES_EXTENDER_mx7d = "imxpxp:imxepdc" > > > -MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxgpu3d" > > > -MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxgpu3d" > > > -MACHINEOVERRIDES_EXTENDER_mx8mm = > > "imxvpu:imxgpu2d:imxgpu3d" > > > +MACHINEOVERRIDES_EXTENDER_mx7ulp = > > "imxpxp:imxgpu2d:imxdpublit:imxgpu3d" > > > +MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxdpu:imxgpu3d" > > > > This is wrong, mx8mq doesn't have a DPU. > > You are correct about that, my mistake. > > So at this point just need to fix this patch. Note, that I need to submit an > update for imx-gpu-sdk that also depends on imxdpublit. Sorry but that still doesn't tell me why we're not using imxgpu2d as before? Why creating a "2dblit" feature, it was known in the first place that imxgpu2d is capable of 2dblit. Actually let's generalize it and say that "libg2d" (whether it is gpu or dpu) is capable of blitting. The only issue I see is that in the case of imx8mm, both gpu-g2d and dpu-g2d can be built, but that should be easily selectable via a preferred provider for lig2d no? Also I find it more flexible to leave it to the user to select which 2D blitting engine he wants to use instead of forcing one over the other. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 07/19] imx-base.inc: Add imxdpu and imxdpublit to MACHINEOVERRIDES_EXTENDER
Hi Tom, On Wed, Jun 27, 2018 at 12:44:36PM +, Tom Hochstein wrote: > Sorry for the confusion, this design is not quite ready. The original idea > was to separate legacy as 'dpublit' and mx8 as 'dpu', What do you call 'dpublit'? How can imx6 SoCs suddenly have a new feature? > although now we plan to offer 'GPU-G2D' for all mx8 as well. I don't understand, isn't g2d only available for imx8mmini? At least i.MX8M doesn't include a 2D GPU. >I'll simplify it for now and then talk with Prabhu when he gets back from >vacation in a couple of weeks. Please skip that patch entirely then if not ready. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 07/19] imx-base.inc: Add imxdpu and imxdpublit to MACHINEOVERRIDES_EXTENDER
Hi,
I still do not understand that patch.
On Tue, Jun 26, 2018 at 02:37:16PM -0300, Otavio Salvador wrote:
> From: Tom Hochstein
>
> - imx-gpu-g2d requires DPU-blit support
> - imx-dpu-g2d requires DPU support
>
> Signed-off-by: Tom Hochstein
> Signed-off-by: Otavio Salvador
> ---
>
> conf/machine/include/imx-base.inc | 14 +++---
> recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb | 4 +++-
> .../imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb | 4 +++-
> 3 files changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/conf/machine/include/imx-base.inc
> b/conf/machine/include/imx-base.inc
> index 2e8f03a6..2bf79541 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -59,17 +59,17 @@ DEFAULTTUNE_vf ?= "cortexa5thf-neon"
> INHERIT += "machine-overrides-extender"
>
> MACHINEOVERRIDES_EXTENDER_mx25 = "use-mainline-bsp"
> -MACHINEOVERRIDES_EXTENDER_mx6q = "imxipu:imxvpu:imxgpu2d:imxgpu3d"
> -MACHINEOVERRIDES_EXTENDER_mx6dl =
> "imxpxp:imxipu:imxvpu:imxgpu2d:imxgpu3d:imxepdc"
> -MACHINEOVERRIDES_EXTENDER_mx6sx = "imxpxp:imxgpu2d:imxgpu3d"
> -MACHINEOVERRIDES_EXTENDER_mx6sl = "imxpxp:imxgpu2d:imxepdc"
> +MACHINEOVERRIDES_EXTENDER_mx6q =
> "imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d"
> +MACHINEOVERRIDES_EXTENDER_mx6dl =
> "imxpxp:imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d:imxepdc"
> +MACHINEOVERRIDES_EXTENDER_mx6sx = "imxpxp:imxgpu2d:imxdpublit:imxgpu3d"
> +MACHINEOVERRIDES_EXTENDER_mx6sl = "imxpxp:imxgpu2d:imxdpublit:imxepdc"
> MACHINEOVERRIDES_EXTENDER_mx6sll = "imxpxp:imxepdc"
> MACHINEOVERRIDES_EXTENDER_mx6ul = "imxpxp"
> MACHINEOVERRIDES_EXTENDER_mx6ull = "imxpxp:imxepdc"
> MACHINEOVERRIDES_EXTENDER_mx7d = "imxpxp:imxepdc"
> -MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxgpu3d"
> -MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxgpu3d"
> -MACHINEOVERRIDES_EXTENDER_mx8mm = "imxvpu:imxgpu2d:imxgpu3d"
> +MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxdpublit:imxgpu3d"
> +MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxdpu:imxgpu3d"
i.MX8MQ doesnt have a DPU, imx-dpu-g2d_1.4.2 should NOT be built for
this platform.
> +MACHINEOVERRIDES_EXTENDER_mx8mm = "imxvpu:imxgpu2d:imxdpu:imxgpu3d"
>
> MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp = " \
> mx6 \
> diff --git a/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> index dd3aa9dd..9a89fa66 100644
> --- a/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> +++ b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> @@ -34,4 +34,6 @@ INSANE_SKIP_${PN} += "ldflags"
> FILES_${PN} = "${libdir}/libg2d* /opt"
> FILES_${PN}-dev = "${libdir}/libg2d${SOLIBSDEV} ${includedir}"
>
> -COMPATIBLE_MACHINE = "(mx8mm)"
> +# Compatible only with i.MX DPU
> +COMPATIBLE_MACHINE = "(^$)"
> +COMPATIBLE_MACHINE_imxdpu = "${MACHINE}"
> diff --git a/recipes-graphics/imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb
> b/recipes-graphics/imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb
> index eab1d31b..a4dbe4e3 100644
> --- a/recipes-graphics/imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb
> +++ b/recipes-graphics/imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb
> @@ -35,4 +35,6 @@ FILES_${PN} = "${libdir}/libg2d* /opt"
> FILES_${PN}-dev = "${includedir}"
> INSANE_SKIP_${PN} = "ldflags"
>
> -COMPATIBLE_MACHINE = "(mx6|mx7ulp)"
> +# Compatible only with i.MX DPU-blit
What? The DPU naming is highly confusing, do you mean that the CPU is
capable of doing 2D blit?
> +COMPATIBLE_MACHINE = "(^$)"
> +COMPATIBLE_MACHINE_imxdpublit = "${MACHINE}"
Why not using:
COMPATIBLE_MACHINE_imxgpu2d = "${MACHINE}"
Why creating imxdpublit whereas there's already imxgpu2d? Then
virtual/libg2d is either provided by imx-gpu-2d or imx-dpu-2d.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH v2 04/19] imx-gpu-viv: Add i.MX 8 support
Hi Tom, Otavio,
Sorry to insist but my previous comments have not been taken into
account in this series.
On Tue, Jun 26, 2018 at 02:37:13PM -0300, Otavio Salvador wrote:
> From: Tom Hochstein
>
> Signed-off-by: Tom Hochstein
> Signed-off-by: Otavio Salvador
> ---
>
> .../imx-gpu-viv/imx-gpu-viv-6.inc | 37 ---
> .../imx-gpu-viv_6.2.4.p1.2-aarch64.bb | 6 +++
> 2 files changed, 37 insertions(+), 6 deletions(-)
> create mode 100644
> recipes-graphics/imx-gpu-viv/imx-gpu-viv_6.2.4.p1.2-aarch64.bb
>
> diff --git a/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> b/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> index 6cc8cbb1..d5023bdf 100644
> --- a/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> +++ b/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> @@ -12,11 +12,11 @@ DEPENDS += " \
> bb.utils.contains('DISTRO_FEATURES', 'x11', 'virtual/libx11
> libxdamage libxext libxfixes', \
> '', d), d)} \
> "
> -DEPENDS += "libdrm"
> DEPENDS += " \
> ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'libxcb libxshmfence
> libxxf86vm', \
> '', d)} \
> "
> +DEPENDS_append_mx8 = " libdrm wayland"
>
> # imx-gpu-viv does not provide everything it needs to for virtual/libgl
> # on x11 backend or on Wayland backend with XWayland support.
> @@ -29,6 +29,8 @@ EXTRA_PROVIDES_append_imxgpu3d = " \
> virtual/libgles1 \
> virtual/libgles2 \
> "
> +EXTRA_PROVIDES_append_mx8 = " \
> +virtual/libopenvx \
This is wrong, only available for mx8qm.
> "
> PROVIDES += " \
> imx-gpu-viv \
> @@ -51,6 +53,8 @@ inherit fsl-eula-unpack
> SRC_URI = "${FSL_MIRROR}/${PN}-${PV}.bin;fsl-eula=true"
>
> # Note : If you add a package here, to prevent a naming conflict see the
> python_anonymous() futher below
> +IMX_PACKAGES_GBM = ""
> +IMX_PACKAGES_GBM_mx8 = "libgbm-imx libgbm-imx-dev"
> PACKAGES =+ "libclc-imx libclc-imx-dev \
> libgl-imx libgl-imx-dev \
> libgles-imx libgles-imx-dev \
> @@ -64,7 +68,7 @@ PACKAGES =+ "libclc-imx libclc-imx-dev \
> libgal-imx libgal-imx-dev \
> libvivante-dri-imx \
> libvsc-imx \
> - libgbm-imx libgbm-imx-dev \
> + ${IMX_PACKAGES_GBM} \
> libwayland-viv-imx libwayland-viv-imx-dev \
> libgc-wayland-protocol-imx libgc-wayland-protocol-imx-dev \
> libwayland-egl-imx-dev \
> @@ -122,9 +126,19 @@ python __anonymous() {
> IS_MX6SL = "0"
> IS_MX6SL_mx6sl = "1"
>
> +IS_MX8 = "0"
> +IS_MX8_mx8 = "1"
> +
> PACKAGE_FP_TYPE = "hardfp"
>
> +HAS_GBM = "false"
> +HAS_GBM_mx8 = "true"
> +
> +# GLES 3.1 is supported for all i.MX 8
Not true, i.MX 8M Mini is GLES 2.0 only according to NXP website.
> +# GLES 3.2 is supported for i.MX 8QM only
> GLES3_HEADER_REMOVALS = "gl31.h gl32.h"
> +GLES3_HEADER_REMOVALS_remove_mx8 = "gl31.h"
> +GLES3_HEADER_REMOVALS_remove_mx8qm = "gl32.h"
>
> do_install () {
> install -d ${D}${libdir}
> @@ -140,6 +154,9 @@ do_install () {
> rm -rf ${D}${includedir}/vulkan/vulkan.h
>
> install -d ${D}${libdir}/pkgconfig
> +if ${HAS_GBM}; then
> +install -m 0644 ${S}/gpu-core/usr/lib/pkgconfig/gbm.pc
> ${D}${libdir}/pkgconfig/gbm.pc
> +fi
>
> # The preference order, based in DISTRO_FEATURES, is Wayland (with or
> without X11), X11 and fb
> if [ "${USE_WL}" = "yes" ]; then
> @@ -212,6 +229,14 @@ do_install () {
> ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so.2
> ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so
>
> +if [ "${IS_MX8}" = "1" ]; then
> +# Install the vulkan driver in a sub-folder. When installed in the
> same
> +# folder as the vulkan loader layer library, an incorrect linkage is
> +# created from libvulkan.so.1 to our library instead of the loader
> +# layer library.
> +install -d ${D}${libdir}/vulkan
> +mv ${D}${libdir}/libvulkan-${backend}.so
> ${D}${libdir}/vulkan/libvulkan_VSI.so
> +fi
Therefore i.MX 8M Mini cannot support Vulkan.
Let me know if I should offer follow-up patches.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 19/32] xf86-video-imxfb-vivante: Update to version 6.2.4.p1
Hi Fabio,
On Mon, Jun 25, 2018 at 04:30:19PM -0300, Otavio Salvador wrote:
> From: Fabio Berton
>
> - Remove .inc file to use only one .bb file
> - Update O.S. Systems License
> - Remove unused patch
> - Set SDKTARGETSYSROOT to use STAGING_DIR_HOST
> - Remove unnecessary CFLAGS
>
> Signed-off-by: Fabio Berton
> Signed-off-by: Otavio Salvador
> ---
>
> ...top-using-Git-to-write-local-version.patch | 87 ---
> .../xf86-video-imxfb-vivante_6.2.2.p0.bb | 9 --
> ...=> xf86-video-imxfb-vivante_6.2.4.p1.2.bb} | 34 +++-
> 3 files changed, 13 insertions(+), 117 deletions(-)
> delete mode 100644
> recipes-graphics/xorg-driver/xf86-video-imxfb-vivante/Stop-using-Git-to-write-local-version.patch
> delete mode 100644
> recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_6.2.2.p0.bb
> rename recipes-graphics/xorg-driver/{xf86-video-imxfb-vivante.inc =>
> xf86-video-imxfb-vivante_6.2.4.p1.2.bb} (66%)
Minor remark on this patch, your title is missing a ".2" at the end,
otherwise doesn't match the version you bump to.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 30/32] imx-base.inc: Add imxdpu and imxdpublit to MACHINEOVERRIDES_EXTENDER
Hi Otavio, Tom, On Mon, Jun 25, 2018 at 04:30:30PM -0300, Otavio Salvador wrote: > From: Tom Hochstein > > - imx-gpu-g2d requires DPU-blit support Can you elaborate on that? What has changed in the g2d package so that it now depends on DPU-blit? > - imx-dpu-g2d requires DPU support > > Signed-off-by: Tom Hochstein > Signed-off-by: Otavio Salvador > --- > > conf/machine/include/imx-base.inc | 14 +++--- > recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb | 4 +++- > .../imx-gpu-g2d/imx-gpu-g2d_6.2.4.p1.2.bb | 4 +++- > 3 files changed, 13 insertions(+), 9 deletions(-) > > diff --git a/conf/machine/include/imx-base.inc > b/conf/machine/include/imx-base.inc > index 346d1c77..6ba5014d 100644 > --- a/conf/machine/include/imx-base.inc > +++ b/conf/machine/include/imx-base.inc > @@ -59,17 +59,17 @@ DEFAULTTUNE_vf ?= "cortexa5thf-neon" > INHERIT += "machine-overrides-extender" > > MACHINEOVERRIDES_EXTENDER_mx25 = "use-mainline-bsp" > -MACHINEOVERRIDES_EXTENDER_mx6q = "imxipu:imxvpu:imxgpu2d:imxgpu3d" > -MACHINEOVERRIDES_EXTENDER_mx6dl = > "imxpxp:imxipu:imxvpu:imxgpu2d:imxgpu3d:imxepdc" > -MACHINEOVERRIDES_EXTENDER_mx6sx = "imxpxp:imxgpu2d:imxgpu3d" > -MACHINEOVERRIDES_EXTENDER_mx6sl = "imxpxp:imxgpu2d:imxepdc" > +MACHINEOVERRIDES_EXTENDER_mx6q = > "imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx6dl = > "imxpxp:imxipu:imxvpu:imxgpu2d:imxdpublit:imxgpu3d:imxepdc" > +MACHINEOVERRIDES_EXTENDER_mx6sx = "imxpxp:imxgpu2d:imxdpublit:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx6sl = "imxpxp:imxgpu2d:imxdpublit:imxepdc" ?? I don't understand that naming at all. Shouldn't imxdpublit be necessary on HW that has a DPU (ie none of the above)? > MACHINEOVERRIDES_EXTENDER_mx6sll = "imxpxp:imxepdc" > MACHINEOVERRIDES_EXTENDER_mx6ul = "imxpxp" > MACHINEOVERRIDES_EXTENDER_mx6ull = "imxpxp:imxepdc" > MACHINEOVERRIDES_EXTENDER_mx7d = "imxpxp:imxepdc" > -MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxgpu3d" > -MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxgpu3d" > -MACHINEOVERRIDES_EXTENDER_mx8mm = "imxvpu:imxgpu2d:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxdpublit:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxdpu:imxgpu3d" This is wrong, mx8mq doesn't have a DPU. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 27/32] imx-gpu-viv: Add i.MX 8 support
Hi Otavio, Tom,
On Mon, Jun 25, 2018 at 04:30:27PM -0300, Otavio Salvador wrote:
> From: Tom Hochstein
>
> Signed-off-by: Tom Hochstein
> Signed-off-by: Otavio Salvador
> ---
>
> .../imx-gpu-viv/imx-gpu-viv-6.inc | 37 ---
> .../imx-gpu-viv_6.2.4.p1.2-aarch64.bb | 6 +++
> 2 files changed, 37 insertions(+), 6 deletions(-)
> create mode 100644
> recipes-graphics/imx-gpu-viv/imx-gpu-viv_6.2.4.p1.2-aarch64.bb
>
> diff --git a/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> b/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> index 6cc8cbb1..d5023bdf 100644
> --- a/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> +++ b/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc
> @@ -12,11 +12,11 @@ DEPENDS += " \
> bb.utils.contains('DISTRO_FEATURES', 'x11', 'virtual/libx11
> libxdamage libxext libxfixes', \
> '', d), d)} \
> "
> -DEPENDS += "libdrm"
> DEPENDS += " \
> ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'libxcb libxshmfence
> libxxf86vm', \
> '', d)} \
> "
> +DEPENDS_append_mx8 = " libdrm wayland"
>
> # imx-gpu-viv does not provide everything it needs to for virtual/libgl
> # on x11 backend or on Wayland backend with XWayland support.
> @@ -29,6 +29,8 @@ EXTRA_PROVIDES_append_imxgpu3d = " \
> virtual/libgles1 \
> virtual/libgles2 \
> "
> +EXTRA_PROVIDES_append_mx8 = " \
> +virtual/libopenvx \
Isn't OpenVx only available on i.MX8QM? Same I think it'd be better not
to expose openvx for imx8mq since it's not supported.
https://www.nxp.com/products/processors-and-microcontrollers/applications-processors/i.mx-applications-processors/i.mx-8-processors:IMX8-SERIES
Also, it seems the i.MX8M Mini only supports OpenGL ES 2.0, not 3.1 and
that Vulkan isn't supported either.
I know it complexifies the recipe but it still should matches what the
HW is capable of, otherwise users will be lost.
To be honest I'd leave i.MX8M Mini out of the picture for now since only
the i.MX8MQ is publicly available.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 25/32] imx-dpu-g2d: Add new G2D implementation based on DPU
Hi Otavio, Tom,
On Mon, Jun 25, 2018 at 04:30:25PM -0300, Otavio Salvador wrote:
> From: Tom Hochstein
>
> Signed-off-by: Tom Hochstein
> Signed-off-by: Otavio Salvador
> ---
>
> .../imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb | 37 +++
> 1 file changed, 37 insertions(+)
> create mode 100644 recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
>
> diff --git a/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> new file mode 100644
> index ..8abbfad8
> --- /dev/null
> +++ b/recipes-graphics/imx-dpu-g2d/imx-dpu-g2d_1.4.2.bb
> @@ -0,0 +1,37 @@
> +# Copyright (C) 2016 Freescale Semiconductor
> +# Copyright 2017-2018 NXP
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +DESCRIPTION = "G2D graphics library and apps for i.MX with DRM"
> +LICENSE = "Proprietary"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=75abe2fa1d16ca79f87cde926f05f72d"
> +
> +RDEPENDS_${PN} = "virtual/libgal-x11 libdrm"
> +
> +PROVIDES += "virtual/libg2d"
> +
> +SRC_URI = "${FSL_MIRROR}/${PN}-${PV}.bin;fsl-eula=true"
> +
> +S="${WORKDIR}/${PN}-${PV}"
> +
> +inherit fsl-eula-unpack
> +
> +SRC_URI[md5sum] = "9beeb2c66f1bad4e82a77487486a31c8"
> +SRC_URI[sha256sum] =
> "905e797d7fb573b5fea616940b07dc15d817fe2f5e94668f883e9faaa516989a"
> +
> +do_install () {
> +
> +install -d ${D}${libdir}
> +install -d ${D}${includedir}
> +
> +cp -r ${S}/g2d/usr/lib/*.so* ${D}${libdir}
> +cp -Pr ${S}/g2d/usr/include/* ${D}${includedir}
> +cp -r ${S}/gpu-demos/opt ${D}
> +}
> +
> +INSANE_SKIP_${PN} += "ldflags"
> +
> +FILES_${PN} = "${libdir}/libg2d* /opt"
> +FILES_${PN}-dev = "${libdir}/libg2d${SOLIBSDEV} ${includedir}"
> +
> +COMPATIBLE_MACHINE = "(mx8)"
Shouldn't the compatible be more specific here to only match platforms
that actually have a DPU? mx8m for instance should be excluded.
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 29/32] imx-base.inc: Add i.MX 8M support
Hi Otavio, Tom, Glad to see this series reaching the mailing list. I have a few comments. First the title only mentions i.MX8M whereas the patch seems to also add i.MX8M Mini support, it'd be clearer to state both in the title. On Mon, Jun 25, 2018 at 04:30:29PM -0300, Otavio Salvador wrote: > From: Tom Hochstein > > Signed-off-by: Tom Hochstein > Signed-off-by: Otavio Salvador > --- > > conf/machine/include/imx-base.inc | 13 ++--- > 1 file changed, 10 insertions(+), 3 deletions(-) > > diff --git a/conf/machine/include/imx-base.inc > b/conf/machine/include/imx-base.inc > index 419ab1bc..346d1c77 100644 > --- a/conf/machine/include/imx-base.inc > +++ b/conf/machine/include/imx-base.inc > @@ -30,9 +30,10 @@ UBOOT_ENTRYPOINT_mx7 = "0x80008000" > UBOOT_ENTRYPOINT_vf = "0x80008000" > > PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg" > -XSERVER_DRIVER = "xf86-video-fbdev" > -XSERVER_DRIVER_imxgpu2d = "xf86-video-imx-vivante" > -XSERVER_DRIVER_vf = "xf86-video-modesetting" > +XSERVER_DRIVER = "xf86-video-fbdev" > +XSERVER_DRIVER_imxgpu2d = "xf86-video-imx-vivante" > +XSERVER_DRIVER_vf = "xf86-video-modesetting" > +XSERVER_DRIVER_append_mx8 = " xf86-video-modesetting" > XSERVER_DRIVER_use-mainline-bsp = "xf86-video-armada" > XSERVER = "xserver-xorg \ > xf86-input-evdev \ > @@ -52,6 +53,7 @@ DEFAULTTUNE_mx6 ?= "cortexa9thf-neon" > DEFAULTTUNE_mx6ul ?= "cortexa7thf-neon" > DEFAULTTUNE_mx6ull ?= "cortexa7thf-neon" > DEFAULTTUNE_mx7 ?= "cortexa7thf-neon" > +DEFAULTTUNE_mx8 ?= "aarch64" > DEFAULTTUNE_vf ?= "cortexa5thf-neon" > > INHERIT += "machine-overrides-extender" > @@ -66,6 +68,8 @@ MACHINEOVERRIDES_EXTENDER_mx6ul = "imxpxp" > MACHINEOVERRIDES_EXTENDER_mx6ull = "imxpxp:imxepdc" > MACHINEOVERRIDES_EXTENDER_mx7d = "imxpxp:imxepdc" > MACHINEOVERRIDES_EXTENDER_mx7ulp = "imxpxp:imxgpu2d:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx8mq = "imxvpu:imxgpu3d" > +MACHINEOVERRIDES_EXTENDER_mx8mm = "imxvpu:imxgpu2d:imxgpu3d" > > MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp = " \ > mx6 \ > @@ -97,6 +101,8 @@ MACHINE_SOCARCH_SUFFIX_vf60 = "-vf60" > MACHINE_SOCARCH_SUFFIX_vf50 = "-vf50" > MACHINE_SOCARCH_SUFFIX_mx6ul = "-mx6ul" > MACHINE_SOCARCH_SUFFIX_mx6ull = "-mx6ul" > +MACHINE_SOCARCH_SUFFIX_mx8mm = "-mx8mm" > +MACHINE_SOCARCH_SUFFIX_mx8mq = "-mx8m" > MACHINE_SOCARCH_SUFFIX_use-mainline-bsp = "-imx" > > MACHINE_ARCH_FILTER = "virtual/kernel" > @@ -158,6 +164,7 @@ MACHINE_FIRMWARE_append_mx6sll = " firmware-imx-epdc" > MACHINE_FIRMWARE_append_mx6ull = " firmware-imx-epdc" > MACHINE_FIRMWARE_append_mx53 = " firmware-imx-vpu-imx53 > firmware-imx-sdma-imx53" > MACHINE_FIRMWARE_append_mx51 = " firmware-imx-vpu-imx51 > firmware-imx-sdma-imx51" > +MACHINE_FIRMWARE_append_mx8 = " linux-firmware-ath10k" Shouldn't this be board specific? Yes the EVK requires ath10k driver but it's not a CPU requirement. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH 0/8] Upstream Multimedia patches for L4.9.51_MX8MQ GA release
Hi On Wed, Jun 06, 2018 at 11:44:17AM +0800, Yuqing Zhu wrote: > -Gstreamer > Create the new gstreamer recipes with i.MX specific version based on v1.12. > Switch to use i.MX fork of GST. > Merge inc/bb files. > Set PREFERRED_VERSION for Gstreamer to use i.MX ones in fsl-base distro > > -imx codec/parser/vpuwrap/gst1.0-plugin > Upgrade to new version: v4.3.4 Why not using the imx_4.9.88_2.0.0_ga instead of the imx_4.9.51_8mq_ga? It seems more recent and targets all i.MX platforms publicly available (i.MX6, i.MX7(ULP), i.MX8M)? Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH] imx-m4fwloader: Add recipe
Hi Vanessa, On Fri, Mar 9, 2018 at 2:27 PM, Vanessa Maegima wrote: > This patch includes a tool for loading firmware to the M4 core from Linux > user space > on the i.MX6SX and i.MX7D boards. > > Tested on an i.MX7D SabreSD board. How long will m4fwloader be maintained? It seems that NXP has started yet another project to control the M4 from user-space which works for both 6SX/7D and i.MX8? https://source.codeaurora.org/external/imxsupport/m4ctrl/ Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH] linux-boundary: Bump kernel version to 4.9.x_1.0.0
Kernel based on NXP imx_4.9.x_1.0.0_ga kernel release.
Also includes stable release (4.9.74 as of this patch).
Signed-off-by: Gary Bisson
---
Hi,
This patch was tested on rocko but it requires the series from Tom that
adds the 6.2.2.p0 graphics. Otherwise the galcore module won't build
againt 4.9. So I'm not sure which branch you want to push that patch to.
Is Tom's series going to make it to rocko branch?
Note that our tree includes a hack to overcome the 4GB of RAM issue with
the graphics driver so there's nothing blocking on our end. A warning
about this in the log and/or recipe should be sufficient (not sure many
platforms have more than 2GB). Hopefully the 6.2.4 version fixes that
issue.
Regards,
Gary
---
.../defconfig | 93 +++---
...-boundary_4.1.15.bb => linux-boundary_4.9.x.bb} | 6 +-
2 files changed, 66 insertions(+), 33 deletions(-)
rename recipes-kernel/linux/{linux-boundary-4.1.15 =>
linux-boundary-4.9.x}/defconfig (87%)
rename recipes-kernel/linux/{linux-boundary_4.1.15.bb =>
linux-boundary_4.9.x.bb} (78%)
diff --git a/recipes-kernel/linux/linux-boundary-4.1.15/defconfig
b/recipes-kernel/linux/linux-boundary-4.9.x/defconfig
similarity index 87%
rename from recipes-kernel/linux/linux-boundary-4.1.15/defconfig
rename to recipes-kernel/linux/linux-boundary-4.9.x/defconfig
index b335f52..e3901be 100644
--- a/recipes-kernel/linux/linux-boundary-4.1.15/defconfig
+++ b/recipes-kernel/linux/linux-boundary-4.9.x/defconfig
@@ -1,6 +1,5 @@
CONFIG_KERNEL_LZO=y
CONFIG_SYSVIPC=y
-CONFIG_FHANDLE=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_IKCONFIG=y
@@ -28,12 +27,10 @@ CONFIG_SOC_IMX6Q=y
CONFIG_SOC_IMX6SL=y
CONFIG_SOC_IMX6SX=y
CONFIG_SOC_IMX7D=y
-CONFIG_ARM_KERNMEM_PERMS=y
CONFIG_PCI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_IMX6=y
CONFIG_SMP=y
-CONFIG_HAVE_ARM_ARCH_TIMER=y
CONFIG_VMSPLIT_2G=y
CONFIG_PREEMPT=y
CONFIG_AEABI=y
@@ -42,10 +39,9 @@ CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=32768
CONFIG_CMA=y
CONFIG_SECCOMP=y
-CONFIG_CMDLINE="console=ttymxc1,115200"
+CONFIG_CMDLINE="noinitrd console=ttymxc0,115200"
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE=y
-CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
@@ -68,16 +64,35 @@ CONFIG_SYN_COOKIES=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_LRO is not set
-CONFIG_IPV6=y
CONFIG_NETFILTER=y
CONFIG_NF_CONNTRACK=m
# CONFIG_NF_CONNTRACK_PROCFS is not set
+CONFIG_NF_TABLES=m
+CONFIG_NF_TABLES_INET=m
+CONFIG_NFT_EXTHDR=m
+CONFIG_NFT_META=m
+CONFIG_NFT_CT=m
+CONFIG_NFT_COUNTER=m
+CONFIG_NFT_LOG=m
+CONFIG_NFT_LIMIT=m
+CONFIG_NFT_MASQ=m
+CONFIG_NFT_REDIR=m
+CONFIG_NFT_NAT=m
+CONFIG_NFT_REJECT=m
+CONFIG_NFT_COMPAT=m
+CONFIG_NFT_HASH=m
CONFIG_NF_CONNTRACK_IPV4=m
-CONFIG_NF_NAT_IPV4=m
+CONFIG_NFT_CHAIN_NAT_IPV4=m
+CONFIG_NFT_MASQ_IPV4=m
+CONFIG_NFT_REDIR_IPV4=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
+CONFIG_IP_NF_NAT=m
+CONFIG_IP_NF_TARGET_MASQUERADE=m
+CONFIG_IP_NF_TARGET_NETMAP=m
+CONFIG_IP_NF_TARGET_REDIRECT=m
+CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=y
CONFIG_LLC2=y
CONFIG_CAN=y
@@ -106,7 +121,7 @@ CONFIG_DEVTMPFS_MOUNT=y
# CONFIG_STANDALONE is not set
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
CONFIG_DMA_CMA=y
-CONFIG_CMA_SIZE_MBYTES=320
+CONFIG_CMA_SIZE_MBYTES=0
CONFIG_CONNECTOR=y
CONFIG_MTD=y
CONFIG_MTD_CMDLINE_PARTS=y
@@ -118,9 +133,11 @@ CONFIG_MTD_PHYSMAP_OF=y
CONFIG_MTD_M25P80=y
CONFIG_MTD_SST25L=y
CONFIG_MTD_SPI_NOR=y
+CONFIG_SPI_FSL_QUADSPI=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=65536
+CONFIG_FTP628=m
CONFIG_EEPROM_AT24=y
CONFIG_EEPROM_AT25=y
# CONFIG_SCSI_PROC_FS is not set
@@ -168,14 +185,15 @@ CONFIG_USB_NET_CDC_MBIM=m
# CONFIG_USB_NET_NET1080 is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
# CONFIG_USB_NET_ZAURUS is not set
+CONFIG_USB_NET_QMI_WWAN=m
CONFIG_USB_HSO=m
-CONFIG_ATH_CARDS=m
CONFIG_ATH9K=m
# CONFIG_ATH9K_RFKILL is not set
CONFIG_BRCMFMAC=m
CONFIG_IWLWIFI=m
+CONFIG_IWLDVM=m
+CONFIG_IWLMVM=m
CONFIG_RTL8192CE=m
-CONFIG_WL_TI=y
CONFIG_WL12XX=m
CONFIG_WLCORE_SDIO=m
# CONFIG_WILINK_PLATFORM_DATA is not set
@@ -183,6 +201,7 @@ CONFIG_INPUT_POLLDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_EVDEV=y
CONFIG_KEYBOARD_GPIO=m
+CONFIG_KEYBOARD_IMX=m
CONFIG_KEYBOARD_CWC_HOOKSWITCH=y
# CONFIG_MOUSE_PS2 is not set
CONFIG_INPUT_TOUCHSCREEN=y
@@ -192,14 +211,14 @@ CONFIG_TOUCHSCREEN_CR_MULTI=m
CONFIG_TOUCHSCREEN_EGALAX=m
CONFIG_TOUCHSCREEN_FT5X06=m
CONFIG_TOUCHSCREEN_GOODIX=m
-CONFIG_TOUCHSCREEN_GSLX680=m
CONFIG_TOUCHSCREEN_ILI210X=m
CONFIG_TOUCHSCREEN_PIC16F616=m
+CONFIG_TOUCHSCREEN_MC13783=m
CONFIG_TOUCHSCREEN_TSC2004=m
+CONFIG_TOUCHSCREEN_SILEAD=m
CONFIG_TOUCHSCREEN_AR1010_UART=m
CONFIG_INPUT_MISC=y
CONFIG
Re: [meta-freescale] [PATCH v3 5/8] xf86-video-imxfb-vivante: Upgrade to 6.2.2.p0
Hi Stefan, On Thu, Dec 7, 2017 at 10:55 AM, Stefan Agner wrote: > > Hi Tom, > > On 2017-11-21 13:56, Tom Hochstein wrote: > > Signed-off-by: Tom Hochstein > > --- > > recipes-graphics/xorg-driver/xf86-video-imxfb-vivante.inc | 8 > > +++- > > .../xorg-driver/xf86-video-imxfb-vivante_5.0.11.p8.6.bb| 10 > > -- > > .../xorg-driver/xf86-video-imxfb-vivante_6.2.2.p0.bb | 9 > > + > > I tried to give this patchset a shot, however it fails for me due to a > HTTP 404: > http://www.freescale.com/lgfiles/NMG/MAD/YOCTO//xserver-xorg-video-imx-viv-6.2.2.p0.tar.gz > > Is this not officially released yet or is there anything else I miss? Maybe they removed the package since the project now has its own git repo: https://source.codeaurora.org/external/imx/xf86-video-imx-vivante/ That is what they use in their Yocto recipe: https://source.codeaurora.org/external/imx/meta-fsl-bsp-release/tree/imx/meta-bsp/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_6.2.2.p0.bb?h=nxp/imx-morty Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH] linux-boundary: fix defconfig after bump
Our in-kernel defconfig is named boundary_defconfig FYI. Signed-off-by: Gary Bisson --- .../linux/linux-boundary-4.1.15/defconfig | 81 +++--- 1 file changed, 71 insertions(+), 10 deletions(-) diff --git a/recipes-kernel/linux/linux-boundary-4.1.15/defconfig b/recipes-kernel/linux/linux-boundary-4.1.15/defconfig index 557c500..b335f52 100644 --- a/recipes-kernel/linux/linux-boundary-4.1.15/defconfig +++ b/recipes-kernel/linux/linux-boundary-4.1.15/defconfig @@ -10,9 +10,6 @@ CONFIG_CGROUPS=y CONFIG_CGROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y CONFIG_NAMESPACES=y -# CONFIG_UTS_NS is not set -# CONFIG_IPC_NS is not set -# CONFIG_PID_NS is not set CONFIG_BLK_DEV_INITRD=y CONFIG_EXPERT=y CONFIG_PERF_EVENTS=y @@ -26,14 +23,17 @@ CONFIG_MODULE_SRCVERSION_ALL=y # CONFIG_BLK_DEV_BSG is not set CONFIG_PARTITION_ADVANCED=y CONFIG_ARCH_MXC=y +CONFIG_SOC_IMX51=y CONFIG_SOC_IMX6Q=y CONFIG_SOC_IMX6SL=y CONFIG_SOC_IMX6SX=y +CONFIG_SOC_IMX7D=y CONFIG_ARM_KERNMEM_PERMS=y CONFIG_PCI=y CONFIG_PCI_MSI=y CONFIG_PCI_IMX6=y CONFIG_SMP=y +CONFIG_HAVE_ARM_ARCH_TIMER=y CONFIG_VMSPLIT_2G=y CONFIG_PREEMPT=y CONFIG_AEABI=y @@ -42,7 +42,7 @@ CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=32768 CONFIG_CMA=y CONFIG_SECCOMP=y -CONFIG_CMDLINE="noinitrd console=ttymxc0,115200" +CONFIG_CMDLINE="console=ttymxc1,115200" CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y @@ -51,6 +51,7 @@ CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y CONFIG_ARM_IMX6Q_CPUFREQ=y +CONFIG_ARM_IMX7D_CPUFREQ=y CONFIG_CPU_IDLE=y CONFIG_VFP=y CONFIG_NEON=y @@ -82,6 +83,7 @@ CONFIG_LLC2=y CONFIG_CAN=y CONFIG_CAN_FLEXCAN=y CONFIG_CAN_M_CAN=y +CONFIG_CAN_MCP251X=m CONFIG_BT=y CONFIG_BT_RFCOMM=y CONFIG_BT_RFCOMM_TTY=y @@ -94,6 +96,7 @@ CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_LL=y CONFIG_CFG80211=m +CONFIG_NL80211_TESTMODE=y CONFIG_CFG80211_WEXT=y CONFIG_MAC80211=m CONFIG_RFKILL=y @@ -134,6 +137,7 @@ CONFIG_PATA_IMX=y CONFIG_MD=y CONFIG_BLK_DEV_DM=y CONFIG_NETDEVICES=y +CONFIG_TUN=m # CONFIG_NET_CADENCE is not set # CONFIG_NET_VENDOR_BROADCOM is not set # CONFIG_NET_VENDOR_CIRRUS is not set @@ -182,13 +186,17 @@ CONFIG_KEYBOARD_GPIO=m CONFIG_KEYBOARD_CWC_HOOKSWITCH=y # CONFIG_MOUSE_PS2 is not set CONFIG_INPUT_TOUCHSCREEN=y -CONFIG_TOUCHSCREEN_AR1020_I2C=y -CONFIG_TOUCHSCREEN_CR_MULTI=y -CONFIG_TOUCHSCREEN_EGALAX=y -CONFIG_TOUCHSCREEN_FT5X06=y +CONFIG_TOUCHSCREEN_AR1020_I2C=m +CONFIG_TOUCHSCREEN_ATMEL_MXT=m +CONFIG_TOUCHSCREEN_CR_MULTI=m +CONFIG_TOUCHSCREEN_EGALAX=m +CONFIG_TOUCHSCREEN_FT5X06=m CONFIG_TOUCHSCREEN_GOODIX=m -CONFIG_TOUCHSCREEN_ILI210X=y -CONFIG_TOUCHSCREEN_TSC2004=y +CONFIG_TOUCHSCREEN_GSLX680=m +CONFIG_TOUCHSCREEN_ILI210X=m +CONFIG_TOUCHSCREEN_PIC16F616=m +CONFIG_TOUCHSCREEN_TSC2004=m +CONFIG_TOUCHSCREEN_AR1010_UART=m CONFIG_INPUT_MISC=y CONFIG_INPUT_UINPUT=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y @@ -196,10 +204,14 @@ CONFIG_DEVPTS_MULTIPLE_INSTANCES=y # CONFIG_DEVKMEM is not set CONFIG_SERIAL_IMX=y CONFIG_SERIAL_IMX_CONSOLE=y +CONFIG_SERIAL_GPS_MAX7W=m +CONFIG_SERIAL_SC16IS7XX=m CONFIG_SERIAL_FSL_LPUART=y CONFIG_SERIAL_FSL_LPUART_CONSOLE=y +CONFIG_SERIAL_XR20M117X=m CONFIG_FSL_OTP=y CONFIG_MAGSTRIPE=m +CONFIG_SAS=m # CONFIG_I2C_COMPAT is not set CONFIG_I2C_CHARDEV=y CONFIG_I2C_MUX_GPIO=y @@ -212,6 +224,10 @@ CONFIG_SPI_IMX=y CONFIG_SPI_SPIDEV=y CONFIG_GPIO_SYSFS=y CONFIG_POWER_SUPPLY=y +CONFIG_POWER_RESET=y +CONFIG_POWER_RESET_GPIO=y +CONFIG_SENSORS_ADS1000=m +CONFIG_SENSORS_MAG3110=y # CONFIG_MXC_MMA8451 is not set CONFIG_THERMAL=y CONFIG_CPU_THERMAL=y @@ -219,30 +235,50 @@ CONFIG_IMX_THERMAL=y CONFIG_DEVICE_THERMAL=y CONFIG_WATCHDOG=y CONFIG_IMX2_WDT=y +CONFIG_MFD_MC13XXX_SPI=m +CONFIG_MFD_MAX77823=y +CONFIG_MFD_ARIZONA_SPI=m +CONFIG_MFD_WM5102=y CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y CONFIG_REGULATOR_ANATOP=y +CONFIG_REGULATOR_ARIZONA=m +CONFIG_REGULATOR_MC13892=m +CONFIG_REGULATOR_PFUZE100=y CONFIG_MEDIA_SUPPORT=y CONFIG_MEDIA_CAMERA_SUPPORT=y +CONFIG_MEDIA_ANALOG_TV_SUPPORT=y CONFIG_MEDIA_RADIO_SUPPORT=y CONFIG_MEDIA_USB_SUPPORT=y CONFIG_USB_VIDEO_CLASS=m +CONFIG_MEDIA_PCI_SUPPORT=y +CONFIG_VIDEO_TW686X=m CONFIG_V4L_PLATFORM_DRIVERS=y CONFIG_VIDEO_MXC_OUTPUT=y CONFIG_VIDEO_MXC_CAPTURE=m CONFIG_MXC_CAMERA_OV5640=m CONFIG_MXC_CAMERA_OV5642=m CONFIG_MXC_CAMERA_OV5640_MIPI=m +CONFIG_MXC_VIDEO_GS2971=m +CONFIG_MXC_HDMI_CSI2_TC358743=m +CONFIG_TC358743_AUDIO=y CONFIG_MXC_TVIN_ADV7180=m CONFIG_MXC_IPU_DEVICE_QUEUE_SDC=m CONFIG_VIDEO_MXC_IPU_OUTPUT=y CONFIG_VIDEO_MXC_PXP_V4L2=y +CONFIG_VIDEO_MXC_CSI_CAMERA=m +CONFIG_MXC_CAMERA_SUBDEV_OV5640=m +CONFIG_MXC_CAMERA_SUBDEV_OV5642=m +CONFIG_MXC_VADC=m +CONFIG_MXC_MIPI_CSI=m +CONFIG_MXC_CAMERA_SUBDEV_OV5640_MIPI=m CONFIG_SOC_CAMERA=y CONFIG_DRM=y CONFIG_DRM_VIVANTE=y CONFIG_FB=y CONFIG_FB_MXS=y CONFIG_FB_MXC_SYNC_PANEL=y +CONFIG_FB_MXC_TVOUT_ADV739X=y
Re: [meta-freescale] [PATCH v2 05/14] imx-gpu-viv: Upgrade to 6.2.2.p0
Hi Tom, On Wed, Nov 15, 2017 at 10:02 PM, Tom Hochstein wrote: > Key Features of the Vivante 6.2.2.p0 Driver Series > > - Full support for Khronos Vulkan 1.0 API and WSI extension APIs > Vulkan is a new generation graphics and compute API that provides > high-efficiency, cross-platform access to modern GPUs used in a wide > variety of devices. Vivante’s Vulkan 1.0 implementation has passed > Khronos Vulkan 1.0 Conformance Test. Vivante GC7000XS* GPU core has > been certified by Khronos as a Vulkan 1.0 compliant product. > - Full support for Khronos OpenGL ES 3.2 API > The new OpenGL ES 3.2 and OpenGL ES Shading Language 3.20 > specifications bring AEP, plus additional functionality, into core > OpenGL ES. Vivante OpenGL ES 3.2 implementation has passed Khronos > OpenGL ES 3.2 Conformance Test. And Vivante GC7000XS* GPU core has > been certified by Khronos as an OpenGL ES 3.2 compliant product. > - Draw calls specifying a base vertex parameter > - Floating-point framebuffers > - Robust buffer access control > - Support for querying CONTEXT_FLAGS, as needed by debug and robust buffer > access functionality. > - Khronos OpenVX 1.0.1 API > - Khronos OpenCL 1.2 API > > Improvements > > 1. Added mutex protection for referencing gctSIGNAL in gckOS_MapSignal to fix > a MT race issue. > 2. Streamlined GPU address calculation base on MC20 (0/1) and MMU (0/1) > combinations. > 3. Fixed multiple Android HWC 2.0 rendering issues. Refined HWC 2.0 driver > implementation. > 4. Improved HWC2.0 composition performance by composing damaged regions only. > 6. Enabled offline/online compiler IR assembly dump function for users. > 7. Implemented the direct rendering support (no-resolve) for Wayland platform. > 8. Added EGL_EXT_buffer_age extension for Wayland and fbdev platforms. > 9. Updated wayland-viv protocol to support tile status sync from client to > server. > 10. Improved OpenCL 1.2 builtin function support with native GPU instructions. > 11. Enabled OpenCL 1.2 API trace dump function controlled by VIV_TRACE > environment variable. > 12. Support for OpenGL4.0 > 13. Cleaned up driver code issues reported by Klocwork and Coverity. > > Changes and Bug Fixes > > VG3D: MGS-2972 fix 3D OpenVG render target orientation > EGL:MGS-2790 6sx-sdb Met memory dump when do xwld stress test > EGL:MGS-2885 fix recursive call to dequeue buffer issue on wayland > EGL:MGS-2785 Meet segmentation fault when test qt5nmapper on wayland > EGL:MGS-2734 fix x11 memory leak issue > Gralloc:MA-9561 fix crash issue on new gralloc1 interface. > 2D: MGS-2900 fix filterblt memory leak > VG2D/6SL: MGS-2882 fix video memory allocator > OCL:MGS-2732 clCopyImage with max_images in OCL1.1 cts, crashes. > GLES: MGS-2747 enable the full config for ES3 CTS > GLES: MGS-1832 fix Mirada performance issue. optimize cpu load for fence > check > WEBGL: MGS-2779 webgl 1.0.2 conformance test met out of memory > General:MGS-2923 fix gc2000 gpu hang when flush TS cache > General:MGS-2907 fix wrong cache invalidate with dma_map_area > General:MGS-2902 fix wrong release_mem_region > General:MGS-2848 fix gpu hang for flat mapping optimization > General:MGS-2848 Optimize MMUv1 FlatMapping performances > General:MGS-2857 fix spinlock in gpu kernel driver > General:MGS-2805 Enable gcdENABLE_VG by default. > General:MGS-2827 fix serious performance drop on imx6q > General:MGS-2832 fix axi bus error with correct baseaddress > General:MA-9483 Refine android native fence code to match 4.9 kernel > General:MA-9473 Fix gpu random crash issue caused by NULL pointer > General:MGS-2804 fix flat mapping overflow issue > General:MGS-2786 fix gpu kernel panic with debugfs > General:GS-2776 fix galcore device open failure > General:MGS-2767 i.MX7ULP GPU suspend/resume problem > Coverity:MGS-2858 Double free in __driUtilUpdateExtraDrawableInfo > > Known Issues > > OpenCL 1.1 CTS failures. Will be addresed in 6.2.3 > MGS-3027 GPU: X11 manywin draw error. 100% > MGS-2935 [imx6QP] X11: glxs app test some frames render incorrectly. 100% > MGS-2860 [MX7ULP/imx6SLEVK] X11/Xwld: XWindow 2D Acceleration performance > test met "X Error of failed request: BadMatch (invalid parameter attributes)" > error. 100% > MGS-2829 [imx6qp/imx6d] xwld: mm06 Samurai and Proxycon performance > regression comparing with L4.1 using 5.0.11p8 > MGS-2310 [imx6qp/imx6dq/imx6dl/imx6sx] webgl: two items performance data is > lower than L4.1_GA > MGS-1828 [imx6qp_sd/imx6Q/imx6dl] X11/xwld: VGMARK on vg3d have some items > performance drop comparing with L4.1 GA > MGS-1350 [imx6qp-sd] X/FB: Some Basemark test items performance drop > comparing with L3.14.52GA which use 5.0.11p7 If I may, I have one more issue to add to the list: [imx6q/imx6qp/imx6dl] Does not work if cma region is above 'base + 2G' Have you tried this driver on an i.MX6 platform with 4GB of RAM & kernel 4.9 (rel_imx_4.9.x_1.0.0_ga)? Here it fails because the region of cma in such case is located at the en
Re: [meta-freescale] [PATCH 03/14] imx-gpu-apitrace: Move apitrace out of imx-gpu-viv v6
Hi Tom, On Thu, 2017-10-19 at 13:36 -0500, Tom Hochstein wrote: > Signed-off-by: Tom Hochstein > --- > .../0001-add-docs-HOWTO.markdown.patch | 61 +++ > ...cs-Freescale_apitrace_user_guide.markdown.patch | 91 > ...0003-add-docs-Freescale_apitrace.markdown.patch | 133 ++ > .../0004-add-docs-apitrace_test.markdown.patch | 144 ++ > .../0005-add-apitrace_dalvik.sh.patch | 75 +++ > .../0006-add-test_android.sh.patch | 72 +++ > .../imx-gpu-apitrace/0007-add-test_yocto.sh.patch | 131 ++ > .../0008-docs-mention-apitrace_dalvik.sh.patch | 28 ++ > .../0009-add-retrace-glws_nonx.cpp.patch | 515 > + > .../0010-cmake-use-glws_nonx-for-Vivante.patch | 62 +++ > .../0011-cli_trace-export-ENABLE_API_TRACE-1.patch | 37 ++ > .../0012-use-dlsym-to-get-function-pointers.patch | 31 ++ > ...ver-does-not-support-GL_RGB-in-openGL-dri.patch | 36 ++ > ...-hangs-when-retracing-OGLESParticles-on-m.patch | 28 ++ > ...5-egl-define-egl-native-types-for-non-x11.patch | 36 ++ > ...-don-t-recreate-the-EGL-surface-on-resize.patch | 32 ++ > .../imx-gpu-apitrace/0017-add-Image-getMD5.patch | 69 +++ > ...ace-use-Image-getMD5-for-image-comparison.patch | 175 +++ > ...race-don-t-use-dlsym-on-aliased-functions.patch | 91 > .../0020-egl-glx-trace-add-ApiTraceEnabled.patch | 79 > .../0021-LocalWriter-make-a-writer-ignorable.patch | 101 > ...-retrace-tutorial3-is-different-with-trac.patch | 82 > .../0023-add-support-for-Vivante-extensions.patch | 444 > ++ > ...70-ccc-cannot-trace-mesa-demos-vertexrate.patch | 34 ++ > ...025-MGS-1271-ccc-disable-X-debug-function.patch | 30 ++ > ...-MGS-1721-ccc-fix-broken-build-on-AArch64.patch | 43 ++ > ...c-blank-screen-when-retracing-es20-sdk-ap.patch | 58 +++ > ...c-add-the-TOT-commit-SHA1-inside-the-bina.patch | 55 +++ > ...-avoid-memcpy-in-glTexDirectInvalidateVIV.patch | 283 +++ > ...-retrace-support-eglCreatePixmapSurface-o.patch | 98 > ...acktrace-define-HAVE_STDINT_H-in-config.h.patch | 36 ++ > .../0032-changed-disable-X11-mechanism.patch | 18 + > ...c-Miss-usr-bin-eglretrace-file-in-FB-and-.patch | 70 +++ > .../0034-MGS-make-multiarch-optional.patch | 22 + > ...en-don-t-override-symbols-in-Vivante-libs.patch | 101 > .../imx-gpu-apitrace/imx-gpu-apitrace_7.1.0.bb | 57 +++ > 36 files changed, 3458 insertions(+) > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0001-add-docs-HOWTO.markdown.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0002-add-docs-Freescale_apitrace_user_guide.markdown.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0003-add-docs-Freescale_apitrace.markdown.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0004-add-docs-apitrace_test.markdown.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0005-add-apitrace_dalvik.sh.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0006-add-test_android.sh.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0007-add-test_yocto.sh.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0008-docs-mention-apitrace_dalvik.sh.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0009-add-retrace-glws_nonx.cpp.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0010-cmake-use-glws_nonx-for-Vivante.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0011-cli_trace-export-ENABLE_API_TRACE-1.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0012-use-dlsym-to-get-function-pointers.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0013-Vivante-driver-does-not-support-GL_RGB-in-openGL- > dri.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0014-MGS-469-GPU-hangs-when-retracing-OGLESParticles-on- > m.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0015-egl-define-egl-native-types-for-non-x11.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0016-don-t-recreate-the-EGL-surface-on-resize.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0017-add-Image-getMD5.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0018-retrace-use-Image-getMD5-for-image-comparison.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0019-egltrace-don-t-use-dlsym-on-aliased-functions.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu- > apitrace/0020-egl-glx-trace-add-ApiTraceEnabled.patch > create mode 100644 recipes-graphics/imx-gpu-apitrace/imx-gpu
Re: [meta-freescale] [PATCH 3/3] linux-fslc: Add recipe for version 4.13
Hi Fabio, On Fri, Aug 25, 2017 at 9:06 PM, Fabio Berton wrote: > This commit add linux-fslc recipe version 4.13-rc6. > > Signed-off-by: Fabio Berton > --- > recipes-kernel/linux/linux-fslc_4.13.bb | 17 + > 1 file changed, 17 insertions(+) > create mode 100644 recipes-kernel/linux/linux-fslc_4.13.bb Not sure this is the correct approach, IMO the 4.13 should have its own defconfig since this version now supports capture for i.MX6: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/drivers/staging/media/imx So I'd recommend adding the following options to the defconfig: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/?h=imx/defconfig&id=b834bc1c Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH] linux-fslc: Bump revision to 836377e382
This commit merge tag v4.9.43 into 4.9.x+fslc and add the
following change on top:
- 2e5f5cc50c72 ARM: dts: imx7d-pico: Add initial support
- 47e80564c4db ARM: imx_v6_v7_defconfig: Select the coda driver as module
- 62dd13a066b9 ARM: dts: imx6qdl-nitrogen6_som2: fix PCIe reset
Signed-off-by: Gary Bisson
---
recipes-kernel/linux/linux-fslc_4.9.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-fslc_4.9.bb
b/recipes-kernel/linux/linux-fslc_4.9.bb
index 00c0d992..5e2f0a9a 100644
--- a/recipes-kernel/linux/linux-fslc_4.9.bb
+++ b/recipes-kernel/linux/linux-fslc_4.9.bb
@@ -12,6 +12,6 @@ include linux-fslc.inc
PV = "4.9+git${SRCPV}"
SRCBRANCH = "4.9.x+fslc"
-SRCREV = "b69ecd63c1237ba4130fd189cbb5287f17ff56d3"
+SRCREV = "836377e3825c9001cc8fee2f8bc2aacae003f1ca"
COMPATIBLE_MACHINE = "(mxs|mx5|mx6|vf|use-mainline-bsp)"
--
2.14.1
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH V2] linux-boundary: change kernel command line defaults (console, initrd)
Hi Eric, On Sun, Aug 20, 2017 at 10:40 PM, Eric Nelson wrote: > Most boards from Boundary Devices default to using UART2 (ttymxc1) > as their console. Update the default kernel command line to match. > > Also remove the 'noinitrd' flag which has little practical use. > > Note that these changes only change the default kernel command line > and are normally overridden by U-Boot through ATAGS. > > Signed-off-by: Eric Nelson Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH] machine/various: update wic dependency notation
Hi Eric, On Sun, Aug 20, 2017 at 2:50 AM, Eric Nelson wrote: > As noted in [1], the notation for wic dependencies has changed. > Update machines other than wandboard with the new notation. > > [1]: > https://lists.yoctoproject.org/pipermail/meta-freescale/2017-June/020668.html > Signed-off-by: Eric Nelson > > Signed-off-by: Eric Nelson Double SOB? Otherwise: Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH] linux-boundary: change kernel command line defaults (console, initrd)
Hi Eric, On Sun, Aug 20, 2017 at 4:01 AM, Eric Nelson wrote: > All boards from Boundary Devices default to using UART2 (ttymxc1) > as their console. Update the default kernel command line to match. Actually that isn't true any more, our latest boards use UART1 (tymxc0): https://github.com/Freescale/meta-freescale-3rdparty/blob/master/conf/machine/nitrogen7.conf#L39 https://github.com/Freescale/meta-freescale-3rdparty/blob/master/conf/machine/nitrogen6sx.conf#L39 But I'm not against this patch, I would just reword to "most Boundary Devices platforms". Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [distro][PATCH] Add recipe for RTSP server
Hi Vanessa, Marco, On Tue, Aug 15, 2017 at 9:36 PM, Marco Frank wrote: > Hi, > > 2017-08-15 16:17 GMT-03:00 Vanessa Maegima : >> >> >> Add recipe for gst-variable-rtsp-server, RTSP server for live-stream >> from a v4l2 video source. >> >> Signed-off-by: Vanessa Maegima > > Tested by: Marco Franchi Just curious, what does this program bring that gst-rtsp-server doesn't? https://github.com/GStreamer/gst-rtsp-server Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 6/6] nitrogen7: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen7.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf index db604ad..30cfb73 100644 --- a/conf/machine/nitrogen7.conf +++ b/conf/machine/nitrogen7.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx7d-nitrogen7.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 4/6] nitrogen6x-lite: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen6x-lite.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen6x-lite.conf b/conf/machine/nitrogen6x-lite.conf index b3356e5..11efddf 100644 --- a/conf/machine/nitrogen6x-lite.conf +++ b/conf/machine/nitrogen6x-lite.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx6dl-nit6xlite.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 5/6] nitrogen7: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen7.conf | 9 +
1 file changed, 9 insertions(+)
diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf
index 7ea21b2..db604ad 100644
--- a/conf/machine/nitrogen7.conf
+++ b/conf/machine/nitrogen7.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx7d-nitrogen7.dtb;imx7d-nitrogen7.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 2/6] nitrogen6sx: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen6sx.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf index 0a4fbd7..45b79f4 100644 --- a/conf/machine/nitrogen6sx.conf +++ b/conf/machine/nitrogen6sx.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx6sx-nitrogen6sx.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 3/6] nitrogen6x-lite: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen6x-lite.conf | 9 +
1 file changed, 9 insertions(+)
diff --git a/conf/machine/nitrogen6x-lite.conf
b/conf/machine/nitrogen6x-lite.conf
index c626ed1..b3356e5 100644
--- a/conf/machine/nitrogen6x-lite.conf
+++ b/conf/machine/nitrogen6x-lite.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx6dl-nit6xlite.dtb;imx6dl-nit6xlite.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 1/6] nitrogen6sx: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen6sx.conf | 9 +
1 file changed, 9 insertions(+)
diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf
index 43f3a2e..0a4fbd7 100644
--- a/conf/machine/nitrogen6sx.conf
+++ b/conf/machine/nitrogen6sx.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx6sx-nitrogen6sx.dtb;imx6sx-nitrogen6sx.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2 0/6] conf: boundary: add mainline BSP support to all platforms
Hi, This series adds support for mainline BSP use for all our platforms. It has been tested on each one of the platforms. One thing to note is that the current imx_v6_v7_defconfig selects the fbdev driver by default, so Etnaviv can't be tested for i.MX6SX for now. Changelog v1->v2: - Remove unnecessary MACHINE_ESSENTIAL_EXTRA_RDEPENDS Regards, Gary Gary Bisson (6): nitrogen6sx: Add wic image tool support nitrogen6sx: Add 'use-mainline-bsp' support nitrogen6x-lite: Add wic image tool support nitrogen6x-lite: Add 'use-mainline-bsp' support nitrogen7: Add wic image tool support nitrogen7: Add 'use-mainline-bsp' support conf/machine/nitrogen6sx.conf | 12 +++- conf/machine/nitrogen6x-lite.conf | 12 +++- conf/machine/nitrogen7.conf | 12 +++- 3 files changed, 33 insertions(+), 3 deletions(-) -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH 0/6] conf: boundary: add mainline BSP support to all platforms
I actually just made a test without it and the boot/ folder (in the root partition) still contains the zImage... Is there an easy/proper way to make an image that mounts the boot partition into boot/? Regards, Gary On Thu, Apr 27, 2017 at 4:54 PM, Otavio Salvador wrote: > Please, do a v2. > > On Thu, Apr 27, 2017 at 11:47 AM, Gary Bisson > wrote: >> Hi Otavio, >> >> On Thu, Apr 27, 2017 at 4:39 PM, Otavio Salvador >> wrote: >>> >>> On Thu, Apr 27, 2017 at 6:33 AM, Gary Bisson >>> wrote: >>> > Those patches are largely inspired by what Otavio did on Nitrogen6x. >>> > Not sure the MACHINE_ESSENTIAL_EXTRA_RDEPENDS are actually needed, this >>> > duplicates the zImage + dtb files which are located in the first 'boot' >>> > partition as well as the 'root' partition under the boot/ folder. >>> > This series keeps that RDEPENDS to match Nitrogen6x but I'm wondering if >>> > that shouldn't be removed. >>> >>> You are right, they can. :-) >> >> Should I send a v2 right away or do you have other remarks? >> >> Regards, >> Gary > > > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty][PATCH 0/6] conf: boundary: add mainline BSP support to all platforms
Hi Otavio, On Thu, Apr 27, 2017 at 4:39 PM, Otavio Salvador wrote: > > On Thu, Apr 27, 2017 at 6:33 AM, Gary Bisson > wrote: > > Those patches are largely inspired by what Otavio did on Nitrogen6x. > > Not sure the MACHINE_ESSENTIAL_EXTRA_RDEPENDS are actually needed, this > > duplicates the zImage + dtb files which are located in the first 'boot' > > partition as well as the 'root' partition under the boot/ folder. > > This series keeps that RDEPENDS to match Nitrogen6x but I'm wondering if > > that shouldn't be removed. > > You are right, they can. :-) Should I send a v2 right away or do you have other remarks? Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 6/6] nitrogen7: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen7.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf index b669ffc..ff69a09 100644 --- a/conf/machine/nitrogen7.conf +++ b/conf/machine/nitrogen7.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx7d-nitrogen7.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 5/6] nitrogen7: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen7.conf | 13 +
1 file changed, 13 insertions(+)
diff --git a/conf/machine/nitrogen7.conf b/conf/machine/nitrogen7.conf
index 7ea21b2..b669ffc 100644
--- a/conf/machine/nitrogen7.conf
+++ b/conf/machine/nitrogen7.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx7d-nitrogen7.dtb;imx7d-nitrogen7.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
@@ -29,4 +38,8 @@ UBOOT_MACHINE ?= "nitrogen7_config"
SERIAL_CONSOLE = "115200 ttymxc0"
MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-wl12xx"
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
+kernel-image \
+kernel-devicetree \
+"
MACHINE_FEATURES += " pci wifi bluetooth"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 2/6] nitrogen6sx: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen6sx.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf index 6dea99c..38dc414 100644 --- a/conf/machine/nitrogen6sx.conf +++ b/conf/machine/nitrogen6sx.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx6sx-nitrogen6sx.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 4/6] nitrogen6x-lite: Add 'use-mainline-bsp' support
The 'use-mainline-bsp' makes use of linux-fslc as kernel. Signed-off-by: Gary Bisson --- conf/machine/nitrogen6x-lite.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/conf/machine/nitrogen6x-lite.conf b/conf/machine/nitrogen6x-lite.conf index a64ca45..779e100 100644 --- a/conf/machine/nitrogen6x-lite.conf +++ b/conf/machine/nitrogen6x-lite.conf @@ -13,7 +13,8 @@ KERNEL_DEVICETREE = "imx6dl-nit6xlite.dtb" KERNEL_IMAGETYPE = "zImage" PREFERRED_PROVIDER_u-boot = "u-boot-boundary" -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" +PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc" # Use SPI NOR U-Boot by default IMAGE_BOOTLOADER ?= "" -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 3/6] nitrogen6x-lite: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen6x-lite.conf | 13 +
1 file changed, 13 insertions(+)
diff --git a/conf/machine/nitrogen6x-lite.conf
b/conf/machine/nitrogen6x-lite.conf
index c626ed1..a64ca45 100644
--- a/conf/machine/nitrogen6x-lite.conf
+++ b/conf/machine/nitrogen6x-lite.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx6dl-nit6xlite.dtb;imx6dl-nit6xlite.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
@@ -29,4 +38,8 @@ UBOOT_MACHINE ?= "nit6xlite_config"
SERIAL_CONSOLE = "115200 ttymxc1"
MACHINE_EXTRA_RRECOMMENDS += " bcm4330-nvram-config"
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
+kernel-image \
+kernel-devicetree \
+"
MACHINE_FEATURES += " pci wifi bluetooth"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 1/6] nitrogen6sx: Add wic image tool support
Required when mainline BSP is used. See 79b9c97f for more details.
Signed-off-by: Gary Bisson
---
conf/machine/nitrogen6sx.conf | 13 +
1 file changed, 13 insertions(+)
diff --git a/conf/machine/nitrogen6sx.conf b/conf/machine/nitrogen6sx.conf
index 43f3a2e..6dea99c 100644
--- a/conf/machine/nitrogen6sx.conf
+++ b/conf/machine/nitrogen6sx.conf
@@ -21,6 +21,15 @@ IMAGE_BOOTLOADER ?= ""
# Ensure boot scripts will be available at rootfs time
do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
+# wic support
+WKS_FILE ?= "sdimage-bootpart.wks"
+IMAGE_BOOT_FILES = " \
+6x_bootscript-${MACHINE};6x_bootscript \
+${KERNEL_IMAGETYPE} \
+${KERNEL_IMAGETYPE}-imx6sx-nitrogen6sx.dtb;imx6sx-nitrogen6sx.dtb \
+"
+IMAGE_DEPENDS_wic_append = " dosfstools-native mtools-native"
+
# Boot scripts to install
BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
@@ -29,4 +38,8 @@ UBOOT_MACHINE ?= "nitrogen6sx_config"
SERIAL_CONSOLE = "115200 ttymxc0"
MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-wl12xx"
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
+kernel-image \
+kernel-devicetree \
+"
MACHINE_FEATURES += " pci wifi bluetooth"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH 0/6] conf: boundary: add mainline BSP support to all platforms
Hi, This series adds support for mainline BSP use for all our platforms. It has been tested on each one of the platforms. One thing to note is that the current imx_v6_v7_defconfig selects the fbdev driver by default, so Etnaviv can't be tested for i.MX6SX for now. Those patches are largely inspired by what Otavio did on Nitrogen6x. Not sure the MACHINE_ESSENTIAL_EXTRA_RDEPENDS are actually needed, this duplicates the zImage + dtb files which are located in the first 'boot' partition as well as the 'root' partition under the boot/ folder. This series keeps that RDEPENDS to match Nitrogen6x but I'm wondering if that shouldn't be removed. Regards, Gary Gary Bisson (6): nitrogen6sx: Add wic image tool support nitrogen6sx: Add 'use-mainline-bsp' support nitrogen6x-lite: Add wic image tool support nitrogen6x-lite: Add 'use-mainline-bsp' support nitrogen7: Add wic image tool support nitrogen7: Add 'use-mainline-bsp' support conf/machine/nitrogen6sx.conf | 16 +++- conf/machine/nitrogen6x-lite.conf | 16 +++- conf/machine/nitrogen7.conf | 16 +++- 3 files changed, 45 insertions(+), 3 deletions(-) -- 2.11.0 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH v2] u-boot-boundary, u-boot-script-boundary: Bump revision to 568947b
The main goal of this update is to address the issues reported by
Otavio using 6x_bootscript-mainline.txt with mainline Linux [1].
Here is a full log of the bump:
568947b9d1 6x_bootscript-mainline: introduce rfspart variable
8c7e53d06f 6x_bootscript-mainline: use UUID to identify root partition
eb4c55af25 6x_bootscript-mainline: fixup LVDS2 display handling
6e4b9009e7 ahci: extend data io wait to 20s
4e4c6006f7 boundary.h: add CONFIG_CMD_PART
bc55c1e287 6x_bootscript-mainline: change default bootdir to be /
d1c5c4bf98 nitrogen6_max: add ND-070PCAP-1024x600
e7b6e555c4 fbpanel: add ND-070PCAP-1024x600
cf2b52b5d9 mtp: update 2G quadplus calibration based on 15 boards
b8b3e1958b mtp: gadget mac is in ethaddr not eth1addr, because no FEC
143d864e2b ahci: extend data io wait to 15s
7ef83873fe 6x_upgrade: re-introduce fs-specific load commands
9dcb694789 lshore: add pin definitions for rev1.1
fd3d0f65c6 ddr-setup.cfg: increase WALAT to 1 cycle
[1]
https://lists.yoctoproject.org/pipermail/meta-freescale/2017-March/020299.html
Signed-off-by: Gary Bisson
---
Changelog:
v1 -> v2:
- Add one more patch to fix root file-system partition number
---
recipes-bsp/u-boot/u-boot-boundary_git.bb| 2 +-
recipes-bsp/u-boot/u-boot-script-boundary_git.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/u-boot/u-boot-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-boundary_git.bb
index aa478ea..10f8e40 100644
--- a/recipes-bsp/u-boot/u-boot-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-boundary_git.bb
@@ -9,7 +9,7 @@ PROVIDES = "u-boot"
PV = "v2016.03+git${SRCPV}"
-SRCREV = "d4aa4cce1f7fbd5df8e2cac72996826a8a096dac"
+SRCREV = "568947b9d1dd4e966008fceb4617392a82dc753c"
SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
diff --git a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
index e4108f9..4ef163e 100644
--- a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
@@ -4,7 +4,7 @@ DEPENDS = "u-boot-mkimage-native"
PV = "v2016.03+git${SRCPV}"
-SRCREV = "d4aa4cce1f7fbd5df8e2cac72996826a8a096dac"
+SRCREV = "568947b9d1dd4e966008fceb4617392a82dc753c"
SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [3rdparty][PATCH] u-boot-boundary, u-boot-script-boundary: Bump revision to 8c7e53d0
The main goal of this update is to address the issues reported by
Otavio using 6x_bootscript-mainline.txt with mainline Linux [1].
Here is a full log of the bump:
8c7e53d06f 6x_bootscript-mainline: use UUID to identify root partition
eb4c55af25 6x_bootscript-mainline: fixup LVDS2 display handling
6e4b9009e7 ahci: extend data io wait to 20s
4e4c6006f7 boundary.h: add CONFIG_CMD_PART
bc55c1e287 6x_bootscript-mainline: change default bootdir to be /
d1c5c4bf98 nitrogen6_max: add ND-070PCAP-1024x600
e7b6e555c4 fbpanel: add ND-070PCAP-1024x600
cf2b52b5d9 mtp: update 2G quadplus calibration based on 15 boards
b8b3e1958b mtp: gadget mac is in ethaddr not eth1addr, because no FEC
143d864e2b ahci: extend data io wait to 15s
7ef83873fe 6x_upgrade: re-introduce fs-specific load commands
9dcb694789 lshore: add pin definitions for rev1.1
fd3d0f65c6 ddr-setup.cfg: increase WALAT to 1 cycle
[1]
https://lists.yoctoproject.org/pipermail/meta-freescale/2017-March/020299.html
Signed-off-by: Gary Bisson
---
recipes-bsp/u-boot/u-boot-boundary_git.bb| 2 +-
recipes-bsp/u-boot/u-boot-script-boundary_git.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/u-boot/u-boot-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-boundary_git.bb
index aa478ea..5df87d3 100644
--- a/recipes-bsp/u-boot/u-boot-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-boundary_git.bb
@@ -9,7 +9,7 @@ PROVIDES = "u-boot"
PV = "v2016.03+git${SRCPV}"
-SRCREV = "d4aa4cce1f7fbd5df8e2cac72996826a8a096dac"
+SRCREV = "8c7e53d06ff70d63ce724e0fdf019f4a9d7e0994"
SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
diff --git a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
index e4108f9..2d6f1ee 100644
--- a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
@@ -4,7 +4,7 @@ DEPENDS = "u-boot-mkimage-native"
PV = "v2016.03+git${SRCPV}"
-SRCREV = "d4aa4cce1f7fbd5df8e2cac72996826a8a096dac"
+SRCREV = "8c7e53d06ff70d63ce724e0fdf019f4a9d7e0994"
SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
--
2.11.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 0/4] Allow easier use of mainline-based BSP on i.MX products (Nitrogen6x support)
Hi Otavio, On Sun, Mar 26, 2017 at 8:54 PM, Otavio Salvador wrote: > >> The only thing that still needs to be figured out is the root= parameter >> which right now requires the following variable to be set when booting a >> Nitrogen6X with WiFi module from first SD slot: >> => setenv root /dev/mmcblk1p2 >> >> The reason is that mainline kernel doesn't allow to change the numbering >> order of SDHC devices based on aliases. Sascha offered a patch which >> never got accepted (but is in the NXP tree) [2]. >> >> So on a device where a WiFi module is present, the first sdcard device >> will be named mmcblk1. But on a SabreLite (no WiFi), it will be mmcblk0 >> as the bootscript thinks it is. >> >> I haven't found a good approach yet to fix it, ideas are welcomed ;) > > Use UUID for booting. It can be done on U-Boot as it can pass the UUID > for the root= argument. See: Great idea! I'm going to do that, I need to add the CMD_PART to our config and update the 6x_bootscript accordingly. I'll let you know once it's done (hopefully I'll have time this week). Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 3/4] nitrogen6x: Add wic image tool support
On Sun, Mar 26, 2017 at 8:37 PM, Otavio Salvador wrote: > On Sat, Mar 25, 2017 at 3:12 PM, Gary Bisson > wrote: >> On Fri, Mar 24, 2017 at 05:12:15PM -0300, Otavio Salvador wrote: >>> The wic image needs to install the bootscript and it loads the >>> respective kernel image and device-tree files from the image, thus >>> those need to be included. >> >> Not sure to understand the wic image requirement. First, is the wic >> image only applies when "use-mainline-bsp" is set? I couldn't find where >> it was mainline specific. > > It is not mainline specific but as we move away the mx6 override the > image class does not work. So I end using it so we can get it building > an out of box image to use. Ok good to know. I just wanted to check that the other dtb shouldn't be declared as well for "regular" NXP-based BSP. In that case: Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 4/4] nitrogen6x: Add 'use-mainline-bsp' support
Hi Otavio, On Sun, Mar 26, 2017 at 8:38 PM, Otavio Salvador wrote: > > On Sat, Mar 25, 2017 at 3:13 PM, Gary Bisson > wrote: > > On Fri, Mar 24, 2017 at 05:12:16PM -0300, Otavio Salvador wrote: > >> The 'use-mainline-bsp' makes use of linux-fslc as kernel and removes > >> the not yet supported device-tree files from installation set. > >> > >> Signed-off-by: Otavio Salvador > >> --- > >> > >> conf/machine/nitrogen6x.conf | 4 > >> 1 file changed, 4 insertions(+) > >> > >> diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf > >> index 8af1b1f..aa068ac 100644 > >> --- a/conf/machine/nitrogen6x.conf > >> +++ b/conf/machine/nitrogen6x.conf > >> @@ -40,10 +40,14 @@ KERNEL_DEVICETREE = "imx6q-sabrelite.dtb \ > >> imx6q-nitrogen6_som2.dtb > >> imx6qp-nitrogen6_som2.dtb \ > >> imx6dl-nitrogen6_vm.dtb > >> imx6dl-nitrogen6_vm-magstripe.dtb \ > >> " > >> +KERNEL_DEVICETREE_remove_use-mainline-bsp = "imx6q-nitrogen6_som2.dtb > >> imx6qp-nitrogen6_som2.dtb \ > >> + imx6dl-nitrogen6_vm.dtb > >> imx6dl-nitrogen6_vm-magstripe.dtb" > >> + > > > > Why do you remove the imx6q-nitrogen6_som2 whereas it is now in > > linux-fslc (and in 4.10)? > > We are still using 4.9 so it does not provide som2. If you can add it, good. It is already part of linux-fslc: https://github.com/Freescale/linux-fslc/commit/404a65b0 Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 4/4] nitrogen6x: Add 'use-mainline-bsp' support
Hi Otavio, On Fri, Mar 24, 2017 at 05:12:16PM -0300, Otavio Salvador wrote: > The 'use-mainline-bsp' makes use of linux-fslc as kernel and removes > the not yet supported device-tree files from installation set. > > Signed-off-by: Otavio Salvador > --- > > conf/machine/nitrogen6x.conf | 4 > 1 file changed, 4 insertions(+) > > diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf > index 8af1b1f..aa068ac 100644 > --- a/conf/machine/nitrogen6x.conf > +++ b/conf/machine/nitrogen6x.conf > @@ -40,10 +40,14 @@ KERNEL_DEVICETREE = "imx6q-sabrelite.dtb \ > imx6q-nitrogen6_som2.dtb imx6qp-nitrogen6_som2.dtb \ > imx6dl-nitrogen6_vm.dtb > imx6dl-nitrogen6_vm-magstripe.dtb \ > " > +KERNEL_DEVICETREE_remove_use-mainline-bsp = "imx6q-nitrogen6_som2.dtb > imx6qp-nitrogen6_som2.dtb \ > + imx6dl-nitrogen6_vm.dtb > imx6dl-nitrogen6_vm-magstripe.dtb" > + Why do you remove the imx6q-nitrogen6_som2 whereas it is now in linux-fslc (and in 4.10)? Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 3/4] nitrogen6x: Add wic image tool support
Hi Otavio, On Fri, Mar 24, 2017 at 05:12:15PM -0300, Otavio Salvador wrote: > The wic image needs to install the bootscript and it loads the > respective kernel image and device-tree files from the image, thus > those need to be included. Not sure to understand the wic image requirement. First, is the wic image only applies when "use-mainline-bsp" is set? I couldn't find where it was mainline specific. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 2/4] nitrogen6x: Use weak-default for virtual/kernel
Hi Otavio, On Fri, Mar 24, 2017 at 05:12:14PM -0300, Otavio Salvador wrote: > The virtual/kernel sometimes need to be overriden, adding the > weak-default allow for easier handler of different providers. > > Signed-off-by: Otavio Salvador > --- > > conf/machine/nitrogen6x.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf > index f9b6cab..f35460d 100644 > --- a/conf/machine/nitrogen6x.conf > +++ b/conf/machine/nitrogen6x.conf > @@ -43,7 +43,7 @@ KERNEL_DEVICETREE = "imx6q-sabrelite.dtb \ > KERNEL_IMAGETYPE = "zImage" > > PREFERRED_PROVIDER_u-boot = "u-boot-boundary" > -PREFERRED_PROVIDER_virtual/kernel ?= "linux-boundary" > +PREFERRED_PROVIDER_virtual/kernel ??= "linux-boundary" > > # Use SPI NOR U-Boot by default > IMAGE_BOOTLOADER ?= "" > -- > 2.12.1 Same here, looks good. Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 1/4] u-boot-script-boundary: Enable 'use-mainline-bsp' support
Hi Otavio, On Fri, Mar 24, 2017 at 05:12:13PM -0300, Otavio Salvador wrote: > To easy the test with Linux mainline, we are making use of the new > 'use-mainline-bsp' override. > > Signed-off-by: Otavio Salvador Looks good. Reviewed-by: Gary Bisson Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [3rdparty PATCH 0/4] Allow easier use of mainline-based BSP on i.MX products (Nitrogen6x support)
Hi Otavio, First of all, thank you for this series and the great job you've done to add mainline support, this is highly appreciated! On Fri, Mar 24, 2017 at 05:12:12PM -0300, Otavio Salvador wrote: > > This patchset makes use of the infrastructure added to meta-freescale > to enable easier use of mainline-based BSP. To enable it, include: > > MACHINEOVERRIDES .= ":use-mainline-bsp" > > To the local.conf and everything is done automatically. > > The bootscript still needs some love to work out of box but this will > be left for Boundary Devices ;-) I've fixed one of the two issues already [1] so bootdir doesn't need to be set any more. The only thing that still needs to be figured out is the root= parameter which right now requires the following variable to be set when booting a Nitrogen6X with WiFi module from first SD slot: => setenv root /dev/mmcblk1p2 The reason is that mainline kernel doesn't allow to change the numbering order of SDHC devices based on aliases. Sascha offered a patch which never got accepted (but is in the NXP tree) [2]. So on a device where a WiFi module is present, the first sdcard device will be named mmcblk1. But on a SabreLite (no WiFi), it will be mmcblk0 as the bootscript thinks it is. I haven't found a good approach yet to fix it, ideas are welcomed ;) Regards, Gary [1] https://github.com/boundarydevices/u-boot-imx6/commit/bc55c1e2 [2] https://patchwork.kernel.org/patch/4223911/ -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Is there any point in keeping linux-imx.inc?
Hi Ernst, On Fri, Dec 16, 2016 at 1:27 PM, Ernst Sjöstrand wrote: > Hi, > > well I'm just saying that > linux-fscl-imx is using the exact same code (SHA1:s even I would say!) as > linux-imx, > it's the same code in http://git.freescale.com/git/cgit.cgi/imx/linux-imx > as in > https://github.com/Freescale/linux-fslc/tree/4.1-2.0.x-imx > You are mistaken, it really isn't the same tree. First the community tree (fslc) includes patches for other vendors than NXP and therefore supports more boards. It also includes all the security updates from the mainline stable 4.1 branch which is why NXP kernel is 4.1.15 whereas the fslc is, as of today, 4.1.35. http://git.freescale.com/git/cgit.cgi/imx/linux-imx.git/tree/Makefile?id=rel_imx_4.1.15_2.0.0_ga#n3 https://github.com/Freescale/linux-fslc/blob/4.1-2.0.x-imx/Makefile#L3 Please make a diff of the two trees and you'll see by yourself. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Cellular modem support for IMX7 Linux distribution
Hi Johan, Well for software support the Huawei website provides many documentation on how to integrate the different pieces: http://consumer.huawei.com/en/solutions/m2m-solutions/products/support/application-guides/mu609mini-pcie-en.htm In our case, I offered this hw combination because the driver is already present in our kernel tree and the user-space components also available on our Debian/ubuntu images. Regards, Gary On Wed, Sep 14, 2016 at 9:25 AM, Lantz Johan < johan.la...@sigmaconnectivity.se> wrote: > Hi Gary, > > > > Thanks for your help and sorry for a late response. I was not looking for > a solution I was asking about availability in software for Linux. I could > not find any software on the provided links. > > > > BR, > > /Johan > > > > *From:* Gary Bisson [mailto:gary.bis...@boundarydevices.com] > *Sent:* den 12 september 2016 14:20 > *To:* Lantz Johan > *Cc:* meta-freescale@yoctoproject.org > *Subject:* Re: [meta-freescale] Cellular modem support for IMX7 Linux > distribution > > > > Hi Johan, > > > > You can have a look at this cellular module: > > https://boundarydevices.com/product/mu609/ > > > > It works on our Nitrogen7 i.MX7 board: > > https://boundarydevices.com/product/nitrogen7/ > > > > Hope this helps. > > > > Regards, > > Gary > > > > On Tue, Aug 30, 2016 at 1:50 PM, Lantz Johan sigmaconnectivity.se> wrote: > > Hi, > > > > I’m looking for any software support for a Cellular modem connected to > IMX7 platform using a Linux distribution. Anyone having any knowledge about > what is already supported regarding API’s and interfaces such as USB, PCIe > and UART to connect an external modem with a socket that could be accesses > via an application or command line. I guess that UART will be preferred and > use of AT commands. > > > > BR, > > /Johan > > > -- > ___ > meta-freescale mailing list > meta-freescale@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-freescale > > > -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Cellular modem support for IMX7 Linux distribution
Hi Johan, You can have a look at this cellular module: https://boundarydevices.com/product/mu609/ It works on our Nitrogen7 i.MX7 board: https://boundarydevices.com/product/nitrogen7/ Hope this helps. Regards, Gary On Tue, Aug 30, 2016 at 1:50 PM, Lantz Johan < johan.la...@sigmaconnectivity.se> wrote: > Hi, > > > > I’m looking for any software support for a Cellular modem connected to > IMX7 platform using a Linux distribution. Anyone having any knowledge about > what is already supported regarding API’s and interfaces such as USB, PCIe > and UART to connect an external modem with a socket that could be accesses > via an application or command line. I guess that UART will be preferred and > use of AT commands. > > > > BR, > > /Johan > > -- > ___ > meta-freescale mailing list > meta-freescale@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-freescale > > -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Nitrogen6x2g Ubuntu kernel 3-14-52 : black screen
Hi, On Wed, Jun 22, 2016 at 1:02 AM, Miroslav Lazic wrote: > Hi, > > I'm using Nitrogen6x 2Gb with Ubuntu image from > https://boundarydevices.com/mx-linux-kernel-3-14-52 and U-Boot > 2015.07-15001-g440d481 (Oct 07 2015 - 12:32:09 -0700). This mailing list is about Yocto, not Ubuntu. Next time please ask your question on our blog or NXP community forum. > Also, I set > allow_noncea=1 > bootargs=video=mxcfb0:dev=ldb,1024x600M@60,if=RGB666 If you read the blog post carefully, it says: This release uses the same mechanism as the 3.14.28 which means that U-Boot is in charge of setting the display parameters in the device tree. So it requires to use U-Boot v2015.07 or higher. Please make sure to read our blog post about this release: https://boundarydevices.com/compiling-latest-u-boot-for-i-mx6-2015-edition/ There you'll learn how to setup the displays, which cannot be done with the bootargs. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] master/krogoth kernel crash for imx7D
Hi Daiane, I've had this CAAM issue in the past: http://lists.denx.de/pipermail/u-boot/2016-March/250112.html Are you using mainline U-Boot? If so you need to enable the secure mode, otherwise CAAM won't work. See the patch I made on our Github repo to fix it: https://github.com/boundarydevices/u-boot-imx6/commit/38b5fa7e Regards, Gary On Thu, Jun 23, 2016 at 7:10 PM, Daiane Angolini wrote: > I'm facing the following kernel crash for imx7dsabresd. Any hint? > > Starting kernel ... > > Booting Linux on physical CPU 0x0 > Linux version 4.1.15-1.1.0+ga4d2a08 (fsl@fsl-Precision-M4800) (gcc > version 5.3.0 (GCC) ) #1 SMP PREEMPT Thu Jun 23 15:50:23 CEST 2016 > CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7d > CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > Machine model: Freescale i.MX7D SabreSD Board > Reserved memory: created CMA memory pool at 0xac00, size 320 MiB > Reserved memory: initialized node linux,cma, compatible id shared-dma-pool > Memory policy: Data cache writealloc > PERCPU: Embedded 12 pages/cpu @ab71c000 s16908 r8192 d24052 u49152 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096 > Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw > PID hash table entries: 4096 (order: 2, 16384 bytes) > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Memory: 698868K/1048576K available (7944K kernel code, 422K rwdata, > 2832K rodata, 428K init, 440K bss, 22028K reserved, 327680K > cma-reserved, 0K highmem) > Virtual kernel memory layout: > vector : 0x - 0x1000 ( 4 kB) > fixmap : 0xffc0 - 0xfff0 (3072 kB) > vmalloc : 0xc080 - 0xff00 (1000 MB) > lowmem : 0x8000 - 0xc000 (1024 MB) > pkmap : 0x7fe0 - 0x8000 ( 2 MB) > modules : 0x7f00 - 0x7fe0 ( 14 MB) > .text : 0x80008000 - 0x80a8e398 (10777 kB) > .init : 0x80a8f000 - 0x80afa000 ( 428 kB) > .data : 0x80afa000 - 0x80b63b40 ( 423 kB) >.bss : 0x80b66000 - 0x80bd40c0 ( 441 kB) > SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 > Preemptible hierarchical RCU implementation. > Additional per-CPU info printed with stalls. > RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. > RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 > NR_IRQS:16 nr_irqs:16 16 > Architected cp15 timer(s) running at 8.00MHz (phys). > clocksource arch_sys_counter: mask: 0xff max_cycles: > 0x1d854df40, max_idle_ns: 440795202120 ns > sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns > Switching to timer-based delay loop, resolution 125ns > mxc_clocksource_init 300 > Ignoring duplicate/late registration of read_current_timer delay > clocksource mxc_timer1: mask: 0x max_cycles: 0x, > max_idle_ns: 637086815595 ns > Console: colour dummy device 80x30 > Calibrating delay loop (skipped), value calculated using timer > frequency.. 16.00 BogoMIPS (lpj=8) > pid_max: default: 32768 minimum: 301 > Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) > Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) > CPU: Testing write buffer coherency: ok > /cpus/cpu@0 missing clock-frequency property > /cpus/cpu@1 missing clock-frequency property > CPU0: thread -1, cpu 0, socket 0, mpidr 8000 > Setting up static identity map for 0x80008280 - 0x800082d8 > CPU1: failed to come online > Brought up 1 CPUs > SMP: Total of 1 processors activated (16.00 BogoMIPS). > CPU: All CPU(s) started in SVC mode. > devtmpfs: initialized > device-tree: Duplicate name in lcdif@3073, renamed to "display#1" > VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 > clocksource jiffies: mask: 0x max_cycles: 0x, > max_idle_ns: 1911260446275 ns > pinctrl core: initialized pinctrl subsystem > NET: Registered protocol family 16 > DMA: preallocated 256 KiB pool for atomic coherent allocations > cpuidle: using governor ladder > cpuidle: using governor menu > DDR type is DDR3! > hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. > hw-breakpoint: maximum watchpoint size is 8 bytes. > imx7d-pinctrl 302c.iomuxc-lpsr: initialized IMX pinctrl driver > imx7d-pinctrl 3033.iomuxc: initialized IMX pinctrl driver > MU is ready for cross core communication! > mxs-dma 3300.dma-apbh: initialized > SCSI subsystem initialized > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > 3080.aips-bus:usbphy_nop1 supply vcc not found, using dummy regulator > 3080.aips-bus:usbphy_nop2 supply vcc not found, using dummy regulator > i2c i2c-0: IMX I2C adapter registered > i2c i2c-0: can't use DMA > i2c i2c-1: IMX I2C adapter registered > i2c i2c-1: can't use DMA > i2c i
Re: [meta-freescale] [meta-fsl-arm-extra] SabreLite: Can't run epiphany
Hi Gary, On Fri, Apr 15, 2016 at 6:12 PM, Gary Thomas wrote: > epiphany on my SabreLite does not run. When I try to start it, > I see fleeting messages about some error trying to display the > page. These repeat every few seconds, ad nauseum... > > Using Poky/Yocto: > Build Configuration: > BB_VERSION= "1.30.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-15.10" > TARGET_SYS= "arm-amltd-linux-gnueabi" > MACHINE = "nitrogen6x" > DISTRO= "amltd" > DISTRO_VERSION= "2.1+snapshot-20160415" > TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard > cortexa9" > TARGET_FPU= "hard" > meta = "master:20a0121b558b32179220e394a66cb90dc6ff3879" > meta-fsl-arm = "master:682b957545172a79cfb19108a9d0b61209f8671e" > meta-fsl-arm-extra = "master:39eb21c4c24a0be6d8277b566ebd52b657fbc2bb" > > Check out http://www.mlbassoc.com/misc/VIDEO0036.mp4 to see this in action. CC Ian, he is the one who can help you with that. Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-kobs: Fix compile error
Gary, All, On Fri, Apr 15, 2016 at 4:43 AM, Gary Thomas wrote: > Recent compiler updates now require to use 'uintX_t' types. > As a FYI, I've made a patch for that in Buildroot: https://github.com/buildroot/buildroot/blob/master/package/freescale-imx/imx-kobs/0002-Fix-build-for-recent-toolchains.patch This issue only appears with kernel headers >= 4.4 since mtd-user.h isn't including stdint.h any more. Also, for those using musl, another patch is needed: https://github.com/buildroot/buildroot/blob/master/package/freescale-imx/imx-kobs/0001-Fix-musl-build.patch Regards, Gary -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH v2 1/2] gstreamer1.0-plugins-imx: Update to version 0.12.1
'DISTRO_FEATURES', 'x11', 'virtual/libx11', \
> + base_contains('DISTRO_FEATURES', 'wayland', 'wayland', \
> + '', d),d)}"
> +
> +PACKAGECONFIG ?= ""
> +PACKAGECONFIG_mx6q = "uniaudiodec mp3encoder v4l2src g2d eglvivsink ipu
> vpu"
> +PACKAGECONFIG_mx6dl = "uniaudiodec mp3encoder v4l2src pxp g2d eglvivsink
> ipu vpu"
> +PACKAGECONFIG_mx6sx = "uniaudiodec mp3encoder v4l2src pxp g2d eglvivsink"
> +PACKAGECONFIG_mx6sl = "uniaudiodec mp3encoder v4l2src pxp g2d"
> +PACKAGECONFIG_mx7 = "uniaudiodec mp3encoder v4l2src pxp"
> +
> +PACKAGECONFIG[g2d] = ",--disable-g2d,imx-gpu-viv"
> +PACKAGECONFIG[pxp] = ",--disable-pxp,"
> +PACKAGECONFIG[ipu] = ",--disable-ipu,"
> +PACKAGECONFIG[vpu] = ",--disable-vpu,libimxvpuapi"
> +PACKAGECONFIG[eglvivsink] =
> "${EGL_PLATFORM_CONF},--disable-eglvivsink,${EGLVIVSINK_DEPENDS}"
> +PACKAGECONFIG[v4l2src] = ",--disable-v4l2src,"
> +PACKAGECONFIG[uniaudiodec] = ",--disable-uniaudiodec,libfslcodec"
> +PACKAGECONFIG[mp3encoder] = ",--disable-mp3encoder,libfslcodec"
>
> # LIBV is used by gst-plugins-package.inc to specify the GStreamer
> version (0.10 vs 1.0)
> LIBV = "1.0"
> @@ -42,7 +63,7 @@ require
> recipes-multimedia/gstreamer/gst-plugins-package.inc
> # the following line is required to produce one package for each plugin
> PACKAGES_DYNAMIC = "^${PN}-.*"
>
> -COMPATIBLE_MACHINE = "(mx6)"
> +COMPATIBLE_MACHINE = "(mx6|mx7)"
>
> # disable the false alarm (the "it isn't a build dependency" QA warning)
> INSANE_SKIP_gstreamer1.0-plugins-imx-imxaudio = "build-deps"
> --
> 2.5.0
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
Reviewed-by: Gary Bisson
Tested-by: Gary Bisson
Tested on Jethro branch on Nitrogen6x and Nitrogen7, making all the plugins
are available and working.
Here are the plugins available on Nitrogen6x (i.MX6Q):
root@nitrogen6x:~# gst-inspect-1.0 | grep imx
imxeglvivsink: imxeglvivsink: Freescale EGL video sink
imxg2d: imxg2dvideosink: Freescale G2D video sink
imxg2d: imxg2dvideotransform: Freescale G2D video transform
imxg2d: imxg2dcompositor: Freescale G2D video compositor
imxvpu: imxvpudec: Freescale VPU video decoder
imxvpu: imxvpuenc_h263: Freescale VPU h.263 video encoder
imxvpu: imxvpuenc_h264: Freescale VPU h.264 video encoder
imxvpu: imxvpuenc_mpeg4: Freescale VPU MPEG-4 video encoder
imxvpu: imxvpuenc_mjpeg: Freescale VPU motion JPEG video encoder
imxipu: imxipuvideotransform: Freescale IPU video transform
imxipu: imxipuvideosink: Freescale IPU video sink
imxipu: imxipucompositor: Freescale IPU video compositor
imxv4l2videosrc: imxv4l2videosrc: V4L2 CSI Video Source
imxaudio: imxuniaudiodec: Freescale i.MX uniaudio decoder
imxaudio: imxmp3audioenc: Freescale i.MX MP3 encoder
Here are the plugins available on Nitrogen7 (i.MX7):
root@nitrogen7:~# gst-inspect-1.0 | grep imx
imxpxp: imxpxpvideotransform: Freescale PxP video transform
imxpxp: imxpxpvideosink: Freescale PxP video sink
imxv4l2videosrc: imxv4l2videosrc: V4L2 CSI Video Source
imxaudio: imxmp3audioenc: Freescale i.MX MP3 encoder
imxaudio: imxuniaudiodec: Freescale i.MX uniaudio decoder
Regards,
Gary
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] gstreamer1.0-plugins-imx: Update to version 0.12.1
Carlos, All,
On Wed, Apr 6, 2016 at 10:29 AM, Carlos Rafael Giani
wrote:
>
>
> On 2016-04-06 10:10, Gary Bisson wrote:
>>
>> Carlos, All,
>>
>> On Wed, Apr 6, 2016 at 9:36 AM, Carlos Rafael Giani
>> wrote:
>>>
>>> The recipe now uses PACKAGECONFIG to allow for enabling/disabling
>>> plugins.
>>> Also, mx7 support has been added, and the libfslcodec->imx_codec renaming
>>> has been included.
>>>
>>> Changes:
>>>
>>> * compositor: Rename ImxCompositor(Pad) to ImxVideoCompositor(Pad)
>>>This prevents conflicts if both the NXP plugins and the gstreamer-imx
>>>are installed in the same rootfs
>>>
>>> * Add switches to wscript configuration to enable/disable plugins
>>>Until now, all plugins were built (unless their dependencies were
>>>missing). On some i.MX machines, some features are missing. For
>>>example, the i.MX7 has no VPU. To ensure deterministic builds, it is
>>>useful to selectively disable plugins in the build.
>>>
>>> * ipu+pxp: : Fix deadlocks and incorrect logging in case of init error
>>>This was causing a freeze if for example one tries to use PxP elements
>>>on an i.MX6 Dual/Quad
>>>
>>> * imxv4l2videosrc fixes and enhancements:
>>>* fixes to interlacing support (incl. workarounds for analog TV input)
>>>* remove format restriction in get_caps function
>>> this removes the limitation on I420 formats
>>>* simplified determination of fps (necessary due to driver
>>> limitations)
>>>
>>> * eglvivsink: wayland: Do not commit before buffers are swapped
>>>This fixes eglSwapBuffer swaps with damaged frames
>>>
>>> * Documentation additions
>>>Adds GPU memory leak notess to the FAQ
>>>
>>> * vpu: encoder: Expose motion estimation range as property
>>>
>>> * vpu: decoder: Drop output frame if its buffer cannot be allocated
>>>
>>> Signed-off-by: Carlos Rafael Giani
>>> ---
>>> 12.0.bb => gstreamer1.0-plugins-imx_0.12.1.bb} | 34
>>> +-
>>> 1 file changed, 26 insertions(+), 8 deletions(-)
>>> rename recipes-multimedia/gstreamer/{gstreamer1.0-plugins-imx_0.12.0.bb
>>> => gstreamer1.0-plugins-imx_0.12.1.bb} (61%)
>>>
>>> diff --git
>>> a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
>>> b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
>>> similarity index 61%
>>> rename from
>>> recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
>>> rename to recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
>>> index eaccb29..852388d 100644
>>> --- a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
>>> +++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
>>> @@ -2,11 +2,9 @@ DESCRIPTION = "GStreamer 1.0 plugins for i.MX platforms"
>>> LICENSE = "LGPLv2+"
>>> LIC_FILES_CHKSUM =
>>> "file://LICENSE;md5=55ca817ccb7d5b5b66355690e9abc605"
>>> SECTION = "multimedia"
>>> -# gstreamer1.0-plugins-bad is in DEPENDS because imxv4l2videosrc
>>> requires
>>> -# the GstPhotography headers and libraries
>>> -DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base
>>> gstreamer1.0-plugins-bad imx-gpu-viv \
>>> - libfslcodec libimxvpuapi virtual/kernel virtual/egl
>>> virtual/libgles2 \
>>> - ${@base_contains('DISTRO_FEATURES', 'x11', 'virtual/libx11',
>>> '', d)}"
>>> +# gstreamer1.0-plugins-bad is in DEPENDS because the build script scans
>>> for the
>>> +# GstPhotography headers and libraries
>>> +DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base
>>> gstreamer1.0-plugins-bad virtual/kernel"
>>
>> Shouldn't plugins-bad be a dependency for v4l2src only?
>
>
> The configuration switches only switch on/off the actual plugins (and their
> immediate dependencies, like GLES libraries, or libimxvpuapi).
> And, gstphotography is a dependency-less component of -bad. In the -bad
> tree, gstphotography can be found in gst-libs/ , while stuff that has
> external dependencies is in ext/.
> What this means is that gstphotography is *not* enabled/disabled by the
> v4l2src switch in the build script. This is intentional - dependency-less
> GStreamer *libraries* might be used by more th
Re: [meta-freescale] [meta-fsl-arm][PATCH] gstreamer1.0-plugins-imx: Update to version 0.12.1
Carlos, All,
On Wed, Apr 6, 2016 at 9:36 AM, Carlos Rafael Giani
wrote:
> The recipe now uses PACKAGECONFIG to allow for enabling/disabling plugins.
> Also, mx7 support has been added, and the libfslcodec->imx_codec renaming
> has been included.
>
> Changes:
>
> * compositor: Rename ImxCompositor(Pad) to ImxVideoCompositor(Pad)
> This prevents conflicts if both the NXP plugins and the gstreamer-imx
> are installed in the same rootfs
>
> * Add switches to wscript configuration to enable/disable plugins
> Until now, all plugins were built (unless their dependencies were
> missing). On some i.MX machines, some features are missing. For
> example, the i.MX7 has no VPU. To ensure deterministic builds, it is
> useful to selectively disable plugins in the build.
>
> * ipu+pxp: : Fix deadlocks and incorrect logging in case of init error
> This was causing a freeze if for example one tries to use PxP elements
> on an i.MX6 Dual/Quad
>
> * imxv4l2videosrc fixes and enhancements:
> * fixes to interlacing support (incl. workarounds for analog TV input)
> * remove format restriction in get_caps function
> this removes the limitation on I420 formats
> * simplified determination of fps (necessary due to driver limitations)
>
> * eglvivsink: wayland: Do not commit before buffers are swapped
> This fixes eglSwapBuffer swaps with damaged frames
>
> * Documentation additions
> Adds GPU memory leak notess to the FAQ
>
> * vpu: encoder: Expose motion estimation range as property
>
> * vpu: decoder: Drop output frame if its buffer cannot be allocated
>
> Signed-off-by: Carlos Rafael Giani
> ---
> 12.0.bb => gstreamer1.0-plugins-imx_0.12.1.bb} | 34
> +-
> 1 file changed, 26 insertions(+), 8 deletions(-)
> rename recipes-multimedia/gstreamer/{gstreamer1.0-plugins-imx_0.12.0.bb =>
> gstreamer1.0-plugins-imx_0.12.1.bb} (61%)
>
> diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
> b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
> similarity index 61%
> rename from recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
> rename to recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
> index eaccb29..852388d 100644
> --- a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.0.bb
> +++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-imx_0.12.1.bb
> @@ -2,11 +2,9 @@ DESCRIPTION = "GStreamer 1.0 plugins for i.MX platforms"
> LICENSE = "LGPLv2+"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=55ca817ccb7d5b5b66355690e9abc605"
> SECTION = "multimedia"
> -# gstreamer1.0-plugins-bad is in DEPENDS because imxv4l2videosrc requires
> -# the GstPhotography headers and libraries
> -DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-bad
> imx-gpu-viv \
> - libfslcodec libimxvpuapi virtual/kernel virtual/egl
> virtual/libgles2 \
> - ${@base_contains('DISTRO_FEATURES', 'x11', 'virtual/libx11', '',
> d)}"
> +# gstreamer1.0-plugins-bad is in DEPENDS because the build script scans for
> the
> +# GstPhotography headers and libraries
> +DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-bad
> virtual/kernel"
Shouldn't plugins-bad be a dependency for v4l2src only?
> # add the audioparsers and the videoparsersbad plugins as RDEPENDS ;
> audioparsers
> # for the uniaudio decoder, videoparsersbad for the VPU video decoder
> # the gstreamer1.0-plugins-imx RDEPENDS is necessary to ensure the -good
> recipe is
Same for the RDEPENDS, I think they should be runtime dependencies of
uniaudiodec and vpu.
> @@ -16,7 +14,7 @@ RDEPENDS_gstreamer1.0-plugins-imx-imxaudio =
> "gstreamer1.0-plugins-good-audiopar
> RDEPENDS_gstreamer1.0-plugins-imx-imxvpu =
> "gstreamer1.0-plugins-bad-videoparsersbad"
>
> SRCBRANCH ?= "master"
> -SRCREV = "f8ad953c458be6a89f474a948b6401664a6a1745"
> +SRCREV = "11a7b366f211e54e0ec67c692287603a02640ff6"
> SRC_URI = "git://github.com/Freescale/gstreamer-imx.git;branch=${SRCBRANCH}"
>
> S = "${WORKDIR}/git"
> @@ -33,7 +31,27 @@ EGLVIVSINK_PLATFORM = "${@base_contains('DISTRO_FEATURES',
> 'x11', 'x11', \
>base_contains('DISTRO_FEATURES', 'wayland',
> 'wayland', \
>'fb', d),d)}"
>
> -EXTRA_OECONF = "--egl-platform=${EGLVIVSINK_PLATFORM}
> --kernel-headers=${STAGING_KERNEL_DIR}/include"
> +EGL_PLATFORM_CONF = "--egl-platform=${EGLVIVSINK_PLATFORM}"
> +EXTRA_OECONF = "--kernel-headers=${STAGING_KERNEL_DIR}/include"
> +
> +EGLVIVSINK_DEPENDS = " \
> +virtual/egl virtual/libgles2 \
> +${@base_contains('DISTRO_FEATURES', 'x11', 'virtual/libx11', \
> + base_contains('DISTRO_FEATURES', 'wayland', 'wayland', \
> + '', d),d)}"
> +
> +PACKAGECONFIG ?= ""
> +PACKAGECONFIG_mx6 = "g2d pxp ipu vpu eglvivsink v4l2src uniaudiodec
> mp3encoder"
Wouldn't it be better to split things here for each version of the
mx6, mx6sx doesn't need vpu nor ipu for instance, mx6sl doesn't
[meta-freescale] [meta-fsl-arm-extra][PATCH 3/4] u-boot-boundary: bump SRCREV to 43467b88 (v2016.03)
Adding support for Nitrogen7.
Signed-off-by: Gary Bisson
---
recipes-bsp/u-boot/u-boot-boundary_git.bb | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/recipes-bsp/u-boot/u-boot-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-boundary_git.bb
index 5e4c757..9eea54e 100644
--- a/recipes-bsp/u-boot/u-boot-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-boundary_git.bb
@@ -2,15 +2,15 @@ require recipes-bsp/u-boot/u-boot.inc
DESCRIPTION = "u-boot for Boundary Devices boards."
LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM =
"file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
+LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
COMPATIBLE_MACHINE = "(imx6qsabrelite|nitrogen6x|nitrogen6sx|nitrogen7)"
PROVIDES = "u-boot"
-PV = "v2015.07+git${SRCPV}"
+PV = "v2016.03+git${SRCPV}"
-SRCREV = "6f020cc6fb24f3c5c5287a7b630fc3bd6e09aa6e"
-SRCBRANCH = "boundary-v2015.07"
+SRCREV = "43467b8804f1c61a7f15db15769641b15c8a6502"
+SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
S = "${WORKDIR}/git"
--
2.7.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm-extra][PATCH 4/4] u-boot-script-boundary: bump SRCREV to 43467b88 (v2016.03)
Adding support for i.MX7D in 6x_bootscript and 6x_upgrade.
Signed-off-by: Gary Bisson
---
recipes-bsp/u-boot/u-boot-script-boundary_git.bb | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
index 9741bbf..3ad140b 100644
--- a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
@@ -1,11 +1,11 @@
LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM =
"file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
+LIC_FILES_CHKSUM =
"file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
DEPENDS = "u-boot-mkimage-native"
-PV = "v2015.07+git${SRCPV}"
+PV = "v2016.03+git${SRCPV}"
-SRCREV = "6f020cc6fb24f3c5c5287a7b630fc3bd6e09aa6e"
-SRCBRANCH = "boundary-v2015.07"
+SRCREV = "43467b8804f1c61a7f15db15769641b15c8a6502"
+SRCBRANCH = "boundary-v2016.03"
SRC_URI =
"git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
S = "${WORKDIR}/git"
--
2.7.0
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
