Hello Tim, It depends on the definition of "decency". :) Actually, I was referring to 5.14.y kernel, and at least from what I know USB support is present, although I did not test the performance of

Andrey, By decent support for i.MX8M derivatives you mean no USB, no PCI, no DSI, no MIPI right? :) I haven't looked at the yocto kernel recipes but I spend a lot of time with the mainline kernel

An update on this project. From my perspective, all issues are closed now (~20). I let a few open (although they were created a long time ago) because I don't have the complete background to decide a

Hello Andrey, I was referring to COMPATIBLE_MACHINE in linux-fslc-lts_5.10.bb recipe. It doesn't have mx8 in it (sorry above link is broken) We are using i.MX8 Dual core A35 Thank you for sharing

Hello Ankur, When you say that i.MX8 is not supported - to which SoC you're referring to? Mainline kernel on the [master] branch of this layer does provide a descent support for all i.MX8M

Hi, We are currently using Linux v5.4 for i.MX8 provided by recipe linux-fslc-imx_5.4.bb because as mentioned in recipe as well, branch "5.4-2.3.x-imx" from repo "linux-fslc" get changes merged from

Hi, I am trying to develop a custom ASoC machine driver for an i.MX6 project using yocto. I have followed the yocto provided 'hello-mod' recipe as an example for out-of-tree kernel modules, but

Hi, Luo Thank you for your reply, I'll try this linux-qoriq. Best regards Lei

Hi Lei, LSDK 21.08 components will be available in Yocto 3.3 by this month, currently you can get the kernel 5.10 recipes from

Hi, all Version of kernel in lsdk 2108 has been upgraded to 5.10. I want to know if there is any plan to upgrade linux-qoriq in meta-freescale. It has been 5.4 for a long time. Best regards Lei

hi i am not good at English i have a problem with compiling a kernel module a board is imx6sx evk and kernel is 5.10.35 , yocto is hardknott ( is right ? i installed with this command : repo

<daiane.angolini@...> wrote: I am finally reviewing 2020 (latest updated) issues. My plan is to close as much as possible, and to clean what is still an issue and what was already solved by

Hi Neuber, I think you forgot to hit reply-all. The mailbox driver is at drivers/mailbox/imx-mailbox.c in mainline. Sure, feel free to use it. It is just that you will not get any support from the

<daiane.angolini@...> wrote: Mine is @cengizIO ^_^

That is great! Thanks a lot, Cengiz Can! Currently the project with most old open issues is gstreamer-imx. I found out that there are a lot of solved but not closed issues. However, if I find

pon., 16 sie 2021 o 14:44 Andrey Zhizhikin <andrey.z@...> napisał(a): Thanks for pointing it out. I will check it for sure. -- Piotr Piwko http://www.embedded-engineering.pl/

Hello Piotr, That is the trick: [dunfell] uses 5.4-2.1.x-imx branch, where the proper check for the return of of_get_mac_address() is not implemented. [hardknott] uses 5.4-2.3.x-imx branch, which

Hi Neuber, 5.6 is an unsupported kernel version. It is not a good idea to develop using such an unsupported kernel version. Please see the supported ones at https://www.kernel.org/ These drivers

pon., 16 sie 2021 o 13:39 Andrey Zhizhikin <andrey.z@...> napisał(a): Yes I'm sure. I have tested it several times and with this commit reverted, the board boots successfully exactly the same as it

Hello Piotr, From what I see, the d01f449c008a ("of_net: add NVMEM support to of_get_mac_address") is indeed present on all NXP branches in the repository: $ git branch -r --contains d01f449c008a