Re: Linux v5.10 for i.MX8 development
Andrey Zhizhikin
Hello Ankur,
On Mon, Sep 20, 2021 at 11:30 PM Ankur Tyagi <ankur.tyagi@...> wrote: 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 derivatives, but I'm not entirely sure of the state for i.MX8 family SoC support since I do not have that HW. Can you specify which derivative you're talking about? Is there any plan for that merge? If yes, any timeline by which it will happen?I've looked into updating NXP branch [lf-5.10.y], and it is not trivial... I'm now short on time to have a full swing of merging the latest stable update on top of it, but probably would get to this eventually. If there are any volunteers here that are willing to undertake this task - this would be really appreciated. If no, then can I use "imx_v8_defconfig" from linux-imx repo to build kernel using linux-fslc repo?You can use the `defconfig` file, which is present in the layer to build [linux-fslc] for i.MX8 machine. It resides in recipes-kernel/linux/linux-fslc/armv8a/defconfig and is synchronized with stable kernel release 5.14. If you however opt-in for [linux-fslc-lts] kernel package, then the kernel config file would be taken from recipes-kernel/linux/linux-fslc-lts/armv8a/defconfig, which is also synchronized with 5.10 from stable. Are there any specific configuration options you need from imx_v8_defconfig, which should be present in the defconfig for mainline recipes? i.MX8 is supported in linux-imx_5.10.bb recipe https://github.com/Freescale/meta-freescale/blob/325ad529187fb1309b0a889c5196c8df039aeea9/recipes-ke... which is using kernel from branch "lf-5.10.y" provided by linux-imx repo but this repo is NXP internal and doesn't get updated with stable Linux kernel. It is providing v5.10.35 (https://source.codeaurora.org/external/imx/linux-imx/log/?h=lf-5.10.y)Correct, but as I've already pointed out - the merge of stable updates to this kernel base is not trivial... :/ As one of the things to try out: you can switch the BSP flavor to use "mainline" instead of "nxp", which would take all upstream components instead of those provided by NXP. Be aware, that if you rely on any functionality which is present in NXP BSP only (e.g. GPU/VPU) - this would be unavailable in Mainline BSP.
-- Regards, Andrey. |
|