From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) by mx.groups.io with SMTP id smtpd.web10.4973.1632213376566497650 for ; Tue, 21 Sep 2021 01:36:17 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=hvaQxdQ4; spf=pass (domain: gmail.com, ip: 209.85.167.47, mailfrom: andrey.z@gmail.com) Received: by mail-lf1-f47.google.com with SMTP id b20so19788118lfv.3 for ; Tue, 21 Sep 2021 01:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=hYnMD/l0RkmpSIcl4yF2VVf684APvIhl+rx9CeUxl2M=; b=hvaQxdQ4YMmQUQ0Mnmws/7tm3wm0+O7ncupK88aPhN5+MMFL+/dqgRxn/jay/2MZ0Q Pj0Gu6ig+FxHm6qyfQU/E3hRaSRwEdYLX+XJGmFqXX1WO4CqkJvYbGedn6q0P7XMUGKS dNKYE8UMeGfFeoxxTAj/4W/fNnCFVGVMLZ48142ygPwCXrGuykpqgGPjmIZLcRVVT06z HO8ifX2xwuUiFMpxl/Ud+7x5aJM9uuyteh7Ezb7XTh4gmPvTEs0C7U44lXllHeOSfi6Q LtBry7vhRY83IwwZBdSFk1JKzkMJ0CZiW6SUyWxjGPOBuxwFEfCkQsh+YZt4Pso5ruvm Ceng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=hYnMD/l0RkmpSIcl4yF2VVf684APvIhl+rx9CeUxl2M=; b=UuQVtkuu7xpqBjjbvXTlu7JhudMGWdfNm0jqeOE9J2nZ9q312zdBWam5zZCd6/XwpB QaSnoKYsCREbMLOtO+DV77zHnnD03Uc/H1St7AHAL707zqYO6n+HMFrNz4zQc2czQpjh 7a8zeDnrEqIuL4aD3uk5AGtVP/pjHl/Aa26Sp7+jlFPIXtZKaXCfDJqKwjNRpZE5x2hi LoiOiNJ0gAGHlvHhv12uMEy78UAAKqH+i6/w58YJyGFFAwNOdkYV8bIg/KDYB0OKAmWT l3pfAeKJGj/ttf0dF6/XRchgZilW8CaFwPQwVRdujqBX8sAZ9c4+GAAFScc3ypRlfhgU 4DQQ== X-Gm-Message-State: AOAM531hsXa8hQLIcjmkfnEB35ecZw6GB0HtsQbmtBK5N2Ou3SxK0aF9 tbykuxwWc0KbdkwQ6gqRcNFFeqZfDIp0eyB1+ys= X-Google-Smtp-Source: ABdhPJxtoqIzeFH8s9uV4CpwtzEmnQexqEupEupzBPwcqQ683gKmoDE6WAFF6VScIodYA2DfCWXC6ttBCPHUV5mJJDk= X-Received: by 2002:ac2:560d:: with SMTP id v13mr23374153lfd.342.1632213374495; Tue, 21 Sep 2021 01:36:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Andrey Zhizhikin" Date: Tue, 21 Sep 2021 10:36:03 +0200 Message-ID: Subject: Re: [meta-freescale] Linux v5.10 for i.MX8 development To: Ankur Tyagi Cc: meta-freescale@lists.yoctoproject.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Ankur, On Mon, Sep 20, 2021 at 11:30 PM Ankur Tyagi wr= ote: > > 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 branch "imx_5.4.70_2.3.0" of= linux-imx repo (https://source.codeaurora.org/external/imx/linux-imx/log/?= h=3Dimx_5.4.70_2.3.0) > > Now we are planning to upgrade to Linux v5.10 and here I have few questio= ns: > > 1. Recipe linux-fslc-lts_5.10.bb doesn't support i.MX8 https://github.com= /Freescale/meta-freescale/blob/325ad529187fb1309b0a889c5196c8df039aeea9/rec= ipes-ke... Neither I can see any merge from NXP linux-imx branch "lf-5.10.y= " into linux-fslc branch "5.10.x+fslc". 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 h= appen? 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 ker= nel 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/Freesca= le/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 ke= rnel. It is providing v5.10.35 (https://source.codeaurora.org/external/imx/= linux-imx/log/?h=3Dlf-5.10.y) Correct, but as I've already pointed out - the merge of stable updates to this kernel base is not trivial... :/ > > So ideally, just like v5.4 would like to use linux-fslc repo for v5.10 de= velopment as well. > > > Will appreciate any guidance around appropriate repo for v5.10 developmen= t for i.MX8 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. > > thanks > Ankur >=20 > --=20 Regards, Andrey.