[linux-yocto] [PATCH] nxp-ls1043: add scc and cfg files for nxp-ls1043 platform

[Meng Li]

Refer to scc and cfg files on branch yocto-5.10, add new scc and cfg
files for BSP nxp-ls1043 on branch yocto-5.15.

Signed-off-by: Meng Li 
---
 bsp/nxp-ls1043/nxp-ls1043-preempt-rt.scc |   8 ++
 bsp/nxp-ls1043/nxp-ls1043-standard.scc   |   8 ++
 bsp/nxp-ls1043/nxp-ls1043.cfg| 158 +++
 bsp/nxp-ls1043/nxp-ls1043.scc|   9 ++
 4 files changed, 183 insertions(+)
 create mode 100644 bsp/nxp-ls1043/nxp-ls1043-preempt-rt.scc
 create mode 100644 bsp/nxp-ls1043/nxp-ls1043-standard.scc
 create mode 100644 bsp/nxp-ls1043/nxp-ls1043.cfg
 create mode 100644 bsp/nxp-ls1043/nxp-ls1043.scc

diff --git a/bsp/nxp-ls1043/nxp-ls1043-preempt-rt.scc 
b/bsp/nxp-ls1043/nxp-ls1043-preempt-rt.scc
new file mode 100644
index ..29f0a993
--- /dev/null
+++ b/bsp/nxp-ls1043/nxp-ls1043-preempt-rt.scc
@@ -0,0 +1,8 @@
+define KMACHINE nxp-ls1043
+define KTYPE preempt-rt
+define KARCH arm64
+
+include ktypes/preempt-rt
+branch nxp-ls1043
+
+include nxp-ls1043.scc
diff --git a/bsp/nxp-ls1043/nxp-ls1043-standard.scc 
b/bsp/nxp-ls1043/nxp-ls1043-standard.scc
new file mode 100644
index ..9c85ada6
--- /dev/null
+++ b/bsp/nxp-ls1043/nxp-ls1043-standard.scc
@@ -0,0 +1,8 @@
+define KMACHINE nxp-ls1043
+define KTYPE standard
+define KARCH arm64
+
+include ktypes/standard
+branch nxp-ls1043
+
+include nxp-ls1043.scc
diff --git a/bsp/nxp-ls1043/nxp-ls1043.cfg b/bsp/nxp-ls1043/nxp-ls1043.cfg
new file mode 100644
index ..319812e8
--- /dev/null
+++ b/bsp/nxp-ls1043/nxp-ls1043.cfg
@@ -0,0 +1,158 @@
+..
+.WARNING
+.
+. This file is a kernel configuration fragment, and not a full kernel
+. configuration file.  The final kernel configuration is made up of
+. an assembly of processed fragments, each of which is designed to
+. capture a specific part of the final configuration (e.g. platform
+. configuration, feature configuration, and board specific hardware
+. configuration).  For more information on kernel configuration, please
+. consult the product documentation.
+.
+..
+
+CONFIG_ARM64=y
+CONFIG_ARM64_VA_BITS_48=y
+CONFIG_ARCH_LAYERSCAPE=y
+CONFIG_SCHED_MC=y
+CONFIG_ARM_SMMU=y
+
+CONFIG_PCI=y
+CONFIG_PCI_LAYERSCAPE=y
+CONFIG_PCI_HOST_GENERIC=y
+CONFIG_PCI_XGENE=y
+CONFIG_PCI_MSI=y
+CONFIG_PCIEPORTBUS=y
+CONFIG_HOTPLUG_PCI=y
+CONFIG_HOTPLUG_PCI_PCIE=y
+
+CONFIG_CPU_IDLE=y
+CONFIG_ARM_CPUIDLE=y
+CONFIG_ARM_PSCI_CPUIDLE=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_STAT=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_QORIQ_CPUFREQ=y
+
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_ADV_OPTIONS=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+CONFIG_MTD_PHYSMAP=y
+CONFIG_MTD_PHYSMAP_OF=y
+CONFIG_MTD_DATAFLASH=y
+CONFIG_MTD_SST25L=y
+CONFIG_MTD_NAND_DENALI_DT=y
+CONFIG_MTD_NAND_FSL_IFC=y
+CONFIG_MTD_RAW_NAND=y
+CONFIG_MEMORY=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_SPI_FSL_QUADSPI=y
+CONFIG_ATA=y
+CONFIG_SATA_AHCI=y
+CONFIG_AHCI_QORIQ=y
+
+CONFIG_FSL_XGMAC_MDIO=y
+
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_DW=y
+CONFIG_SERIAL_OF_PLATFORM=y
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+
+CONFIG_SPI=y
+CONFIG_SPI_FSL_DSPI=y
+CONFIG_SPI_PL022=y
+
+CONFIG_POWER_RESET_XGENE=y
+CONFIG_POWER_RESET_SYSCON=y
+CONFIG_ENERGY_MODEL=y
+CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
+
+CONFIG_CPU_THERMAL=y
+CONFIG_WATCHDOG=y
+CONFIG_IMX2_WDT=y
+
+CONFIG_USB=y
+CONFIG_USB_OTG=y
+CONFIG_USB_XHCI_HCD=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_DWC3=y
+CONFIG_USB_DWC3_HOST=y
+CONFIG_USB_GADGET=y
+
+CONFIG_MMC=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_OF_ESDHC=y
+
+CONFIG_GPIOLIB=y
+CONFIG_OF_GPIO=y
+CONFIG_GPIO_MPC8XXX=y
+
+CONFIG_MDIO_DEVICE=y
+CONFIG_MDIO_BITBANG=y
+CONFIG_PHYLIB=y
+CONFIG_AQUANTIA_PHY=y
+
+#
+# I2C support
+#
+CONFIG_I2C=y
+CONFIG_I2C_IMX=y
+
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_PCF2127=y
+CONFIG_RTC_DRV_DS3232=y
+CONFIG_RTC_DRV_DS1307=y
+CONFIG_RTC_DRV_FSL_FTM_ALARM=y
+CONFIG_FSL_RCPM=y
+
+CONFIG_DMADEVICES=y
+CONFIG_FSL_EDMA=y
+CONFIG_CMA=y
+CONFIG_DMA_CMA=y
+
+CONFIG_VFIO=y
+
+CONFIG_STAGING=y
+
+CONFIG_CLK_QORIQ=y
+
+CONFIG_FSL_GUTS=y
+
+CONFIG_PHY_XGENE=y
+
+CONFIG_CRYPTO_DEV_FSL_CAAM=y
+CONFIG_ARM64_CRYPTO=y
+CONFIG_CRYPTO_SHA1_ARM64_CE=y
+CONFIG_CRYPTO_SHA2_ARM64_CE=y
+CONFIG_CRYPTO_GHASH_ARM64_CE=y
+CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
+CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
+
+# dpaa1
+CONFIG_FSL_SDK_DPA=y
+CONFIG_FSL_SDK_FMAN=y
+CONFIG_FSL_SDK_DPAA_ETH=y
+CONFIG_FSL_DPAA_TS=y
+CONFIG_PTP_1588_CLOCK=y
+CONFIG_PTP_1588_CLOCK_QORIQ=y
+CONFIG_FSL_DPAA_1588=y
+
+# EDAC
+CONFIG_EDAC_LAYERSCAPE=y
+
+# Thermal
+CONFIG_THERMAL=y
+CONFIG_DEVICE_THERMAL=y
+CONFIG_QORIQ_THERMAL=y
diff --git 

[linux-yocto] [yocto-kernel-cache]: nxp-ls1043: add scc and cfg files for nxp-ls1043 platform

[Meng Li]

From: Limeng 

Hi Bruce,

Recently, I am working on nxp ls1043 SoC BSP, and want to add scc and cfg files 
for this BSP in kernel-cache.

Could you please help to merge this patch into yocto-kernel-cache, branch is 
only yocto-5.15?

diffstat info as below:

 nxp-ls1043-preempt-rt.scc |8 ++
 nxp-ls1043-standard.scc   |8 ++
 nxp-ls1043.cfg|  158 ++
 nxp-ls1043.scc|9 ++
 4 files changed, 183 insertions(+)


thanks,
Limeng

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11220): 
https://lists.yoctoproject.org/g/linux-yocto/message/11220
Mute This Topic: https://lists.yoctoproject.org/mt/90599707/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-5.15][PATCH 4/4] bsp/intel-x86: add support for Time-Sensitive Network

[Yongxin Liu]

Signed-off-by: Yongxin Liu 
Signed-off-by: Bruce Ashfield 
(cherry picked from commit dbe03fa9005d388617aca3bcfb1b06ba35d49215)
Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
index 38331ac8..197b5064 100644
--- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
+++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
@@ -6,5 +6,6 @@ define KARCH x86
 include ktypes/preempt-rt
 
 include intel-x86-64.scc
+include features/tsn/tsn.scc
 kconf hardware cfs-bandwidth.cfg
 kconf hardware intel-x86-64-preempt-rt.cfg
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11219): 
https://lists.yoctoproject.org/g/linux-yocto/message/11219
Mute This Topic: https://lists.yoctoproject.org/mt/90597948/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-5.15][PATCH 1/4] bsp/intel-x86: add support for Marvell Alaska PHYs

[Yongxin Liu]

Signed-off-by: Yongxin Liu 
Signed-off-by: Bruce Ashfield 
(cherry picked from commit e5f9159b015681e7a2a86cd67f109ae814f5a5c6)
Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86.cfg | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
index 795d1098..872063fb 100644
--- a/bsp/intel-x86/intel-x86.cfg
+++ b/bsp/intel-x86/intel-x86.cfg
@@ -362,3 +362,6 @@ CONFIG_POWERCAP=y
 CONFIG_INTEL_RAPL=m
 
 CONFIG_EXTCON=y
+
+# MII PHY device drivers
+CONFIG_MARVELL_PHY=y
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11218): 
https://lists.yoctoproject.org/g/linux-yocto/message/11218
Mute This Topic: https://lists.yoctoproject.org/mt/90597947/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-5.15][PATCH 0/4] some kernel configs cherry picked from 5.10 to 5.15

[Yongxin Liu]

Hi Bruce,

Here are some commits are cherry-picked from yocto-5.10.
Could you help to merge them to yocto-5.15?

Yongxin Liu (4):
  bsp/intel-x86: add support for Marvell Alaska PHYs
  bsp/intel-x86: add pinctrl support for Intel Elkhart Lake
  features/tsn: add feature for Time-Sensitive Networking
  bsp/intel-x86: add support for Time-Sensitive Network

 bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 +
 bsp/intel-x86/intel-x86.cfg   | 5 +
 features/tsn/tsn.cfg  | 5 +
 features/tsn/tsn.scc  | 3 +++
 4 files changed, 14 insertions(+)
 create mode 100644 features/tsn/tsn.cfg
 create mode 100644 features/tsn/tsn.scc

-- 
2.34.1

Thanks,
Yongxin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11215): 
https://lists.yoctoproject.org/g/linux-yocto/message/11215
Mute This Topic: https://lists.yoctoproject.org/mt/90597944/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-5.15][PATCH 2/4] bsp/intel-x86: add pinctrl support for Intel Elkhart Lake

[Yongxin Liu]

Currently, this pinctrl for Elkhart Lake is only supported in
intel-x86 bsp, so it cannot be added in features/intel-pinctrl.

Signed-off-by: Yongxin Liu 
Signed-off-by: Bruce Ashfield 
(cherry picked from commit bc4bc1a4e732806879286619e8583530df819908)
Signed-off-by: Yongxin Liu 
---
 bsp/intel-x86/intel-x86.cfg | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
index 872063fb..6b5d1046 100644
--- a/bsp/intel-x86/intel-x86.cfg
+++ b/bsp/intel-x86/intel-x86.cfg
@@ -365,3 +365,5 @@ CONFIG_EXTCON=y
 
 # MII PHY device drivers
 CONFIG_MARVELL_PHY=y
+
+CONFIG_PINCTRL_ELKHARTLAKE=y
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11216): 
https://lists.yoctoproject.org/g/linux-yocto/message/11216
Mute This Topic: https://lists.yoctoproject.org/mt/90597945/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][yocto-5.15][PATCH 3/4] features/tsn: add feature for Time-Sensitive Networking

[Yongxin Liu]

Signed-off-by: Yongxin Liu 
Signed-off-by: Bruce Ashfield 
(cherry picked from commit 4537448afb4a4140771a1cd3e67120cee3f1a591)
Signed-off-by: Yongxin Liu 
---
 features/tsn/tsn.cfg | 5 +
 features/tsn/tsn.scc | 3 +++
 2 files changed, 8 insertions(+)
 create mode 100644 features/tsn/tsn.cfg
 create mode 100644 features/tsn/tsn.scc

diff --git a/features/tsn/tsn.cfg b/features/tsn/tsn.cfg
new file mode 100644
index ..c0cac7db
--- /dev/null
+++ b/features/tsn/tsn.cfg
@@ -0,0 +1,5 @@
+# SPDX-License-Identifier: MIT
+CONFIG_NET_SCH_ETF=m
+CONFIG_NET_SCH_CBS=m
+CONFIG_NET_SCH_MQPRIO=m
+CONFIG_NET_SCH_TAPRIO=m
diff --git a/features/tsn/tsn.scc b/features/tsn/tsn.scc
new file mode 100644
index ..0f33451e
--- /dev/null
+++ b/features/tsn/tsn.scc
@@ -0,0 +1,3 @@
+# SPDX-License-Identifier: MIT
+define KFEATURE_DESCRIPTION "Enable Time-Sensitive Networking support"
+kconf non-hardware tsn.cfg
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11217): 
https://lists.yoctoproject.org/g/linux-yocto/message/11217
Mute This Topic: https://lists.yoctoproject.org/mt/90597946/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] Non-deterministic SHA commit hash when applying patches to kernel git repository

[Bruce Ashfield]

On Wed, Apr 20, 2022 at 3:23 PM Jimmy Assarsson 
wrote:

> On 2022-03-13 04:37, Bruce Ashfield wrote:
> > On Sat, Mar 12, 2022 at 2:12 PM Jimmy Assarsson <
> jimmyassars...@gmail.com > wrote:
> >
> > On 2022-03-09 16:47, Bruce Ashfield wrote:
> >  > On Sat, Feb 26, 2022 at 2:17 AM Jimmy Assarsson
> >  > mailto:jimmyassars...@gmail.com>>
> wrote:
> >  >> On 2022-02-24 16:41, Bruce Ashfield wrote:
> >  >>> On Tue, Feb 22, 2022 at 3:42 AM Jimmy Assarsson
> >  >>> mailto:jimmyassars...@gmail.com>>
> wrote:
> >   On 2022-02-21 05:13, Bruce Ashfield wrote:
> >  > on 19/02/2022 Jimmy Assarsson wrote:
> >  >> On 2022-02-19 20:42, Bruce Ashfield wrote:
> >  >>> On Sat, Feb 19, 2022 at 5:28 AM Jimmy Assarsson
> >  >>> mailto:jimmyassars...@gmail.com>>
> wrote:
> >  
> >   When patching a kernel git repository, in a recipe
> inheriting kernel-yocto.bbclass,
> >   the resulting commit hash will become different every time
> the source is unpacked and patched.
> >  
> >   This is a problem that causes non-reproducible builds,
> when the commit hash is built
> >   into the kernel (CONFIG_LOCALVERSION_AUTO=y).
> >  
> >  
> >   Currently it is not a problem in linux-yocto, since an
> empty .scmversion is
> >   created in kernel_do_configure [1]. This is preventing the
> kernel build from
> >   generating its own .scmversion.
> >  
> >   If removing this commit, setting
> CONFIG_LOCALVERSION_AUTO=y and applying any
> >   patch in the linux-yocto recipe, this will result in a
> non-reproducible build.
> >  >>
> >  >> ...
> >  >>
> >   diff --git a/tools/kgit-s2q b/tools/kgit-s2q
> >   index 706783e..b46a138 100755
> >   --- a/tools/kgit-s2q
> >   +++ b/tools/kgit-s2q
> >   @@ -558,7 +558,7 @@ do
> >    echo "($APPLIED/$COUNT) `basename $i`"
> >    fi
> >  
> >   -   git am --keep-non-patch $DIR/$i > /dev/null 2>&1
> >   +   git am --keep-non-patch
> --committer-date-is-author-date $DIR/$i > /dev/null 2>&1
> >    if [ $? != 0 ];then
> >    git am --abort > /dev/null 2>&1
> >    echo "[INFO]: check of $DIR/$i with
> \"git am\" did not pass, trying reduced context."
> >  
> >  
> >  
> >   I'm not sure if this is a proper solution to fix the
> problem or what side effects it may introduce?
> >  >>>
> >  >>> There's nothing fundamentally wrong with that solution, but
> there are
> >  >>> modes for the kernel builds where we absolutely do not want
> the
> >  >>> reproducible build (and older dates) to be in effect (see
> my comments
> >  >>> on the OE core mailing list when the ability to disable
> reproducible
> >  >>> builds was almost removed).
> >  >>
> >  >> Thanks, now I've looked it up.
> >  >>
> >  >>> We could add an option to the patch queue management that
> was enabled
> >  >>> when reproducible builds are in play, so git am could
> operate like
> >  >>> that.
> >  >>>
> >  >>> Alternatively, you could bbappend the other kernel's
> do_configure and
> >  >>> do the same .scmversion trick to make sure that everything
> is
> >  >>> consistent.
> >  >>
> >  >> I don't follow, can you be more specific?
> >  >> We encountered this problem when building linux-imx (from
> meta-freescale).
> >  >> Preferably the .scmversion workaround in [1] should be
> dropped, so that
> >  >> there is no need to reinvent/mimic the output of
> >  >> linux/scripts/setlocalversion, in a bitbake recipe.
> >  >
> >  > I see no compelling reason to drop the .scmversion in the
> main kernel.bbclass
> >  > (at least not in the short term). It has been there for a
> significant amount
> >  > of time, and removing it now would very likely cause some
> ripple effects
> >  > througout the ecosystem (it is there for a few different
> issues).  While not
> >  > elegant, it is an available and workable solution to the
> problem it is
> >  > solving.
> >  
> >   I agree. And obviously this is not a big issue for others.
> >   There have been at least two failed attempts on removing this
> [4][5][6].
> >  
> >  > I was suggesting that anyone can bbappend any kernel recipe
> to do the similar
> >  > .scmversion set (assuming they aren't using the core kernel
> bbclass
> >  > configure()).
> >  

Re: [linux-yocto] Non-deterministic SHA commit hash when applying patches to kernel git repository

[Jimmy Assarsson]

On 2022-03-13 04:37, Bruce Ashfield wrote:

On Sat, Mar 12, 2022 at 2:12 PM Jimmy Assarsson mailto:jimmyassars...@gmail.com>> wrote:

On 2022-03-09 16:47, Bruce Ashfield wrote:
 > On Sat, Feb 26, 2022 at 2:17 AM Jimmy Assarsson
 > mailto:jimmyassars...@gmail.com>> wrote:
 >> On 2022-02-24 16:41, Bruce Ashfield wrote:
 >>> On Tue, Feb 22, 2022 at 3:42 AM Jimmy Assarsson
 >>> mailto:jimmyassars...@gmail.com>> wrote:
  On 2022-02-21 05:13, Bruce Ashfield wrote:
 > on 19/02/2022 Jimmy Assarsson wrote:
 >> On 2022-02-19 20:42, Bruce Ashfield wrote:
 >>> On Sat, Feb 19, 2022 at 5:28 AM Jimmy Assarsson
 >>> mailto:jimmyassars...@gmail.com>> wrote:
 
  When patching a kernel git repository, in a recipe inheriting 
kernel-yocto.bbclass,
  the resulting commit hash will become different every time the 
source is unpacked and patched.
 
  This is a problem that causes non-reproducible builds, when the 
commit hash is built
  into the kernel (CONFIG_LOCALVERSION_AUTO=y).
 
 
  Currently it is not a problem in linux-yocto, since an empty 
.scmversion is
  created in kernel_do_configure [1]. This is preventing the kernel 
build from
  generating its own .scmversion.
 
  If removing this commit, setting CONFIG_LOCALVERSION_AUTO=y and 
applying any
  patch in the linux-yocto recipe, this will result in a 
non-reproducible build.
 >>
 >> ...
 >>
  diff --git a/tools/kgit-s2q b/tools/kgit-s2q
  index 706783e..b46a138 100755
  --- a/tools/kgit-s2q
  +++ b/tools/kgit-s2q
  @@ -558,7 +558,7 @@ do
                       echo "($APPLIED/$COUNT) `basename $i`"
               fi
 
  -       git am --keep-non-patch $DIR/$i > /dev/null 2>&1
  +       git am --keep-non-patch --committer-date-is-author-date $DIR/$i 
> /dev/null 2>&1
               if [ $? != 0 ];then
                       git am --abort > /dev/null 2>&1
                       echo "[INFO]: check of $DIR/$i with \"git am\" 
did not pass, trying reduced context."
 
 
 
  I'm not sure if this is a proper solution to fix the problem or 
what side effects it may introduce?
 >>>
 >>> There's nothing fundamentally wrong with that solution, but there 
are
 >>> modes for the kernel builds where we absolutely do not want the
 >>> reproducible build (and older dates) to be in effect (see my 
comments
 >>> on the OE core mailing list when the ability to disable 
reproducible
 >>> builds was almost removed).
 >>
 >> Thanks, now I've looked it up.
 >>
 >>> We could add an option to the patch queue management that was 
enabled
 >>> when reproducible builds are in play, so git am could operate like
 >>> that.
 >>>
 >>> Alternatively, you could bbappend the other kernel's do_configure 
and
 >>> do the same .scmversion trick to make sure that everything is
 >>> consistent.
 >>
 >> I don't follow, can you be more specific?
 >> We encountered this problem when building linux-imx (from 
meta-freescale).
 >> Preferably the .scmversion workaround in [1] should be dropped, so 
that
 >> there is no need to reinvent/mimic the output of
 >> linux/scripts/setlocalversion, in a bitbake recipe.
 >
 > I see no compelling reason to drop the .scmversion in the main 
kernel.bbclass
 > (at least not in the short term). It has been there for a 
significant amount
 > of time, and removing it now would very likely cause some ripple 
effects
 > througout the ecosystem (it is there for a few different issues).  
While not
 > elegant, it is an available and workable solution to the problem it 
is
 > solving.
 
  I agree. And obviously this is not a big issue for others.
  There have been at least two failed attempts on removing this 
[4][5][6].
 
 > I was suggesting that anyone can bbappend any kernel recipe to do 
the similar
 > .scmversion set (assuming they aren't using the core kernel bbclass
 > configure()).
 >
 > But from your next statement, that isn't going to work as the sole 
solution,
 > since yes, that will only restore where we keep the git rev out of 
the
 > localversion.
 >
 >>
 >> To be clear, we want the result of CONFIG_LOCALVERSION_AUTO=y, but
 >> with a reproducible output.
 >
 > And that's actually part of the reason the .scmversion is set, the
 > setlocalversion 

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Raj, Khem via lists.yoctoproject.org]

OK I would be fine to go with this assertion and perhaps monitor it closely to 
be classified as intermittent or something one off.

From: Richard Purdie 
Date: Wednesday, April 20, 2022 at 7:19 AM
To: Raj, Khem , 
qa-build-notificat...@lists.yoctoproject.org 
, yocto@lists.yoctoproject.org 

Cc: Yocto TSC , Mittal, Anuj 

Subject: Re: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for 
completed autobuilder build (yocto-3.3.6.rc1)
On Wed, 2022-04-20 at 14:14 +, Raj, Khem wrote:
> Is the sato-sdk on qemuppc also intermittent issue

It doesn't usually happen and works fine in other builds so it is intermittent.
Whether it is one of our "known" intermittent issues, I don't know. I couldn't
get any real information from the system about why it failed. We have better
logging in master.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56825): https://lists.yoctoproject.org/g/yocto/message/56825
Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-raspberrypi][PATCH] bluez-firmware-rpidistro: add compatibility to oe-core/create-spdx

[Andrei Gherzan]

Hi,

On Thu, 14 Apr 2022, at 13:36, Davide Gardenal wrote:
> Add do_create_spdx dependency to fix error when LICENCE is not found
>
> Signed-off-by: Davide Gardenal 

I have pulled this patch in 
https://github.com/agherzan/meta-raspberrypi/pull/1053.

Thanks,
Andrei

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56824): https://lists.yoctoproject.org/g/yocto/message/56824
Mute This Topic: https://lists.yoctoproject.org/mt/90463066/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-raspberrypi][PATCH] meta-raspberrypi: u-boot: remove the randundant patch

[Andrei Gherzan]

Hi,

On Wed, 20 Apr 2022, at 03:03, Meng Li wrote:
> This patch had been merged into u-boot upstream. Its commit is
> 29f7d05a347a("dm: core: Move ofdata_to_platdata() call earlier").
> So, remove the randundant patch to avoid building error.
>
> Signed-off-by: Meng Li 

I have pulled this patch in 
https://github.com/agherzan/meta-raspberrypi/pull/1053.

Thanks,
Andrei

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56823): https://lists.yoctoproject.org/g/yocto/message/56823
Mute This Topic: https://lists.yoctoproject.org/mt/90576652/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [PATCH] [v5.15/standard/x86 and v5.15/standard/preempt-rt/x86] Add GPIO, Time-Aware GPIO, PTP and Time Coordinated computing support for Elkhart Lake in kernel v5.15

[Bruce Ashfield]

In message: [linux-yocto] [PATCH] [v5.15/standard/x86  and 
v5.15/standard/preempt-rt/x86]  Add GPIO, Time-Aware GPIO, PTP and Time 
Coordinated computing support for Elkhart Lake in kernel v5.15
on 20/04/2022 Liu, Yongxin wrote:

> Hi Bruce,
> 
> Could you please help to merge those 23 patches to linux-yocto, branch 
> v5.15/standard/x86 and v5.15/standard/preempt-rt/x86?
> Those patches add support for GPIP/TGPIO, PTP and TCC(Intel Time Coordinated 
> Computing) on Elkhart Lake CRB.
> All the patches are from https://github.com/intel/linux-intel-lts.git.


merged.

Bruce

> 
> 
> The following changes since commit 4dca1ea3e781c0e5ced6aab37e95efc0f522ea2f:
> 
>   Merge branch 'v5.15/standard/base' into v5.15/standard/x86 (2022-04-13 
> 22:32:47 -0400)
> 
> are available in the Git repository at:
> 
>   https://github.com/liux2085/linux-yocto v5.15/x86/pull
> 
> for you to fetch changes up to f6c5e7b6e8019ea19fe5b77ba2b078e50aae6a4a:
> 
>   mfd: intel-ehl-gpio: Introduce MFD framework to PSE GPIO/TGPIO (2022-04-20 
> 21:09:48 +0800)
> 
> 
> Christopher Hall (5):
>   x86/tsc: Add TSC support functions to support ART driven Time-Aware GPIO
>   drivers/ptp: Add Enhanced handling of reserve fields
>   drivers/ptp: Add PEROUT2 ioctl frequency adjustment interface
>   drivers/ptp: Add user-space input polling interface
>   drivers/ptp: Add support for PMC Time-Aware GPIO Driver
> 
> Hao Li (1):
>   drivers/ptp: Add COMPV GPIO Mode for PSE TGPIO
> 
> Qiang Rao (16):
>   tcc: this is kernel driver to interface to TCC PTCM pesudo SRAM
>   tcc: parse PTCT table and record pesudo sram ranges
>   tcc: update license header
>   tcc: L3 psram region should not overlay L2 psram region.
>   tcc: driver should exit if no psram entry found in PTCT.
>   tcc: tcc drvier should not exit even if no psram entry.
>   tcc: return error code to better match varies error scenarios.
>   tcc: l3 psram region size could become zero after exclude l2 inclusive 
> regions
>   tcc: update tcc range end_address.
>   tcc: update RTCT table parser to support two versions
>   Enable support to read a few whitelisted registers.
>   Remove Clock_Cycles_VT from MHL entry.
>   Add new IOCTL to read error log buffer.
>   Display errlog buffer raw data in kernel log as requested once this 
> driver is loaded.
>   Fix issue found in acrn uos when convert cacheid to apicid.
>   Support RPL in measurement function.
> 
> Raymond Tan (1):
>   mfd: intel-ehl-gpio: Introduce MFD framework to PSE GPIO/TGPIO
> 
>  arch/x86/include/asm/tsc.h |6 +
>  arch/x86/kernel/acpi/boot.c|  127 +++
>  arch/x86/kernel/tsc.c  |  116 +-
>  drivers/Kconfig|2 +
>  drivers/Makefile   |1 +
>  drivers/gpio/Kconfig   |   11 +
>  drivers/gpio/Makefile  |1 +
>  drivers/gpio/gpio-ehl-pse-plat.c   |  494 
> ++
>  drivers/mfd/Kconfig|   12 ++
>  drivers/mfd/Makefile   |1 +
>  drivers/mfd/intel-ehl-gpio.c   |  256 ++
>  drivers/ptp/Kconfig|   24 +++
>  drivers/ptp/Makefile   |2 +
>  drivers/ptp/ptp-intel-pmc-tgpio.c  |  867 
> ++
>  drivers/ptp/ptp-intel-tgpio-plat.c |  715 
> +
>  drivers/ptp/ptp_chardev.c  |   86 +---
>  drivers/ptp/ptp_clock.c|   13 ++
>  drivers/tcc/Kconfig|9 +
>  drivers/tcc/Makefile   |6 +
>  drivers/tcc/tcc_buffer.c   | 1666 
> ++
>  drivers/tcc/tcc_buffer.h   |  241 +
>  include/acpi/actbl2.h  |   96 +
>  include/linux/ptp_clock_kernel.h   |2 +
>  include/uapi/linux/ptp_clock.h |   28 ++-
>  24 files changed, 4753 insertions(+), 29 deletions(-)
>  create mode 100644 drivers/gpio/gpio-ehl-pse-plat.c
>  create mode 100644 drivers/mfd/intel-ehl-gpio.c
>  create mode 100644 drivers/ptp/ptp-intel-pmc-tgpio.c
>  create mode 100644 drivers/ptp/ptp-intel-tgpio-plat.c
>  create mode 100644 drivers/tcc/Kconfig
>  create mode 100644 drivers/tcc/Makefile
>  create mode 100644 drivers/tcc/tcc_buffer.c
>  create mode 100644 drivers/tcc/tcc_buffer.h
> 
> 
> Thanks,
> Yongxin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11212): 
https://lists.yoctoproject.org/g/linux-yocto/message/11212
Mute This Topic: https://lists.yoctoproject.org/mt/90583841/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: 

Re: [linux-yocto][v5.15/standard/base][PATCH] netfilter: conntrack: avoid useless indirection during conntrack destruction

[Bruce Ashfield]

In message: [linux-yocto][v5.15/standard/base][PATCH] netfilter: conntrack: 
avoid useless indirection during conntrack destruction
on 18/04/2022 He Zhe wrote:

> From: Florian Westphal 
> 
> nf_ct_put() results in a usesless indirection:
> 
> nf_ct_put -> nf_conntrack_put -> nf_conntrack_destroy -> rcu readlock +
> indirect call of ct_hooks->destroy().
> 
> There are two _put helpers:
> nf_ct_put and nf_conntrack_put.  The latter is what should be used in
> code that MUST NOT cause a linker dependency on the conntrack module
> (e.g. calls from core network stack).
> 
> Everyone else should call nf_ct_put() instead.
> 
> A followup patch will convert a few nf_conntrack_put() calls to
> nf_ct_put(), in particular from modules that already have a conntrack
> dependency such as act_ct or even nf_conntrack itself.
> 
> Signed-off-by: Florian Westphal 
> Signed-off-by: Pablo Neira Ayuso 
> 
> Backport
> 6ae7989c9af0 ("netfilter: conntrack: avoid useless indirection during")
> which is not going to stable tree from mainline to fix the following warning,
> with some necessary context tweaks.

Thanks for the extra explanation about the -stable status of
the patch.

It makes the decision on merging much easier.

This is now merged to v5.15 and I'll send SRCREV updates after
my next round of -stable updates.

Bruce

> 
> root@intel-x86-64:~# ovs-vsctl add-br br0
> device ovs-system entered promiscuous mode
> [ cut here ]
> WARNING: CPU: 2 PID: 711 at include/net/netfilter/nf_conntrack.h:175 
> __ovs_ct_lookup+0x819/0x920 [openvswitch]
> CPU: 2 PID: 711 Comm: ovs-vswitchd Not tainted 5.15.33-rt34-yocto-preempt-rt 
> #1
> Hardware name: Intel(R) Client Systems NUC7i5DNKE/NUC7i5DNB, BIOS 
> DNKBLi5v.86A.0064.2019.0523.1933 05/23/2019
> RIP: 0010:__ovs_ct_lookup+0x819/0x920 [openvswitch]
> Code: b8 fe ff ff ff e9 69 f9 ff ff 41 0f b7 84 24 b0 00 00 00 49 8b 94 24 c0 
> 00 00 00 0f b6 1c 02 83 e3 0f c1 e3 02 e9 c5 fc ff ff <0f> 0b e9 86 f8 ff ff 
> 4c 89 f7 44 89 95 40 ff ff ff e8 61 30 fc ff
> RSP: 0018:914c80a77638 EFLAGS: 00010246
> RAX:  RBX: 903b139fa528 RCX: 
> RDX: 0002 RSI: 914c80a77660 RDI: 
> RBP: 914c80a77710 R08: 903b04819128 R09: aa605c40
> R10: 914c80a779c0 R11:  R12: 903b05dd7000
> R13: 0001 R14: 903b0a603c00 R15: 903b04819120
> FS:  7f9256c9ba80() GS:903c65d0() knlGS:
> CS:  0010 DS:  ES:  CR0: 80050033
> CR2: 7ffe2fad9008 CR3: 00010a5e0002 CR4: 003706e0
> DR0:  DR1:  DR2: 
> DR3:  DR6: fffe0ff0 DR7: 0400
> Call Trace:
>  
>  ? nf_ct_get_tuple+0x144/0x1f0 [nf_conntrack]
>  ? nf_ct_get_tuplepr+0x5f/0x90 [nf_conntrack]
>  ovs_ct_execute+0x3e1/0x5e0 [openvswitch]
>  do_execute_actions+0xed/0x1ab0 [openvswitch]
>  ? ovs_ct_copy_action+0x17b/0x8a0 [openvswitch]
>  ? __ovs_nla_copy_actions+0x884/0xf30 [openvswitch]
>  ? migrate_enable+0xd3/0x150
>  ovs_execute_actions+0x62/0x140 [openvswitch]
>  ? ovs_execute_actions+0x62/0x140 [openvswitch]
>  ovs_packet_cmd_execute+0x294/0x310 [openvswitch]
>  genl_family_rcv_msg_doit+0xe6/0x140
>  genl_rcv_msg+0xde/0x1d0
>  ? ovs_vport_cmd_del+0x200/0x200 [openvswitch]
>  ? genl_get_cmd+0xd0/0xd0
>  netlink_rcv_skb+0x55/0x100
>  genl_rcv+0x29/0x40
>  netlink_unicast+0x234/0x340
>  netlink_sendmsg+0x226/0x470
>  ? netlink_unicast+0x340/0x340
>  sys_sendmsg+0x273/0x2b0
>  ? sendmsg_copy_msghdr+0x7b/0xa0
>  ___sys_sendmsg+0x81/0xc0
>  ? do_futex+0x1c4/0xb70
>  ? rt_spin_unlock+0x18/0x40
>  ? __fget_light+0xa3/0x120
>  __sys_sendmsg+0x62/0xb0
>  ? fpregs_assert_state_consistent+0x27/0x50
>  __x64_sys_sendmsg+0x1d/0x20
>  do_syscall_64+0x43/0x90
>  entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f9256dab82d
> Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 1a 97 f7 ff 8b 54 24 1c 48 
> 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 
> 33 44 89 c7 48 89 44 24 08 e8 5e 97 f7 ff 48
> RSP: 002b:7ffe2fae90a0 EFLAGS: 0293 ORIG_RAX: 002e
> RAX: ffda RBX: 0001 RCX: 7f9256dab82d
> RDX:  RSI: 7ffe2fae9130 RDI: 0011
> RBP: 7ffe2fae9f30 R08:  R09: 0001
> R10: 0006 R11: 0293 R12: 55fab0216e90
> R13:  R14: 55fab0216e90 R15: 7ffe2fae9130
>  
> ---[ end trace 0002 ]---
> 
> Signed-off-by: He Zhe 
> ---
>  include/linux/netfilter/nf_conntrack_common.h |  2 ++
>  include/net/netfilter/nf_conntrack.h  |  8 ++--
>  net/netfilter/nf_conntrack_core.c | 12 ++--
>  3 files changed, 14 insertions(+), 8 deletions(-)
> 
> diff --git a/include/linux/netfilter/nf_conntrack_common.h 
> b/include/linux/netfilter/nf_conntrack_common.h
> index 

Re: [linux-yocto][yocto-kernel-cache v5.10] update kernel-cache for marvell

[Bruce Ashfield]

In message: [linux-yocto][yocto-kernel-cache v5.10] update kernel-cache for 
marvell
on 15/04/2022 Ruiqiang Hao wrote:

> Hi Bruce,
> 
> Please help to merge these 2 patches into our linux-yocto repo.
> 
> repo:
>   yocto-kernel-cache
> branch:
>   yocto-5.10

merged.

Bruce

> 
> Thanks,
> Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11210): 
https://lists.yoctoproject.org/g/linux-yocto/message/11210
Mute This Topic: https://lists.yoctoproject.org/mt/90480861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Richard Purdie]

On Wed, 2022-04-20 at 14:14 +, Raj, Khem wrote:
> Is the sato-sdk on qemuppc also intermittent issue 

It doesn't usually happen and works fine in other builds so it is intermittent.
Whether it is one of our "known" intermittent issues, I don't know. I couldn't
get any real information from the system about why it failed. We have better
logging in master.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56822): https://lists.yoctoproject.org/g/yocto/message/56822
Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g: update to align with NXP SDK

[Bruce Ashfield]

In message: [linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g: update to 
align with NXP SDK
on 14/04/2022 Zhantao Tang wrote:

> Hi Bruce,
> 
> 
> There are 24 patches from bsp32 latest update for the following branch
> 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx
> 
> Would you please help to merge these patches?
> 
> 
> The patch infos as following:
> 
> The following changes since commit 69d0db370dbca8e7a4040941182e5433c677e423:
> 
>   Merge branch 'v5.10/standard/base' into 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx (2022-04-11 15:04:49 -0400)

merged.

Bruce

> 
> are available in the Git repository at:
> 
>   https://github.com/zhantaotang/linux-yocto-std 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx
> 
> for you to fetch changes up to 19dad271f538622eeb4b0ea3728dbe48edb78c78:
> 
>   hse: fix race condition on sync request interrupt (2022-04-14 13:22:13 
> +0800)
> 
> 
> Thanks,
> Zhantao

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11209): 
https://lists.yoctoproject.org/g/linux-yocto/message/11209
Mute This Topic: https://lists.yoctoproject.org/mt/90461467/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [linux-yocto std kernel]: nxp-s32g: update to align with NXP SDK

[Bruce Ashfield]

In message: [linux-yocto] [linux-yocto std kernel]: nxp-s32g: update to align 
with NXP SDK
on 14/04/2022 Zhantao Tang wrote:

> Hi Bruce,
> 
> There are 24 patches from NXP internal share repo to update the following 
> branch
> 
>   v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx
> 
> Would you please help to merge the patches?
> 
> 
> The patches info as following:
> 
> The following changes since commit 315df6b52a3bb839e05c4133f6615276897aece7:
> 
>   Merge branch 'v5.10/standard/base' into 
> v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx (2022-04-11 14:59:54 -0400)
> 
> are available in the Git repository at:
> 
>   https://github.com/zhantaotang/linux-yocto-std 
> v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx

merged.

Bruce

> 
> for you to fetch changes up to 929d7bfc9ace081bd39ea609406355505d06e8ec:
> 
>   hse: fix race condition on sync request interrupt (2022-04-14 13:43:11 
> +0800)
> 
> Thanks,
> Zhantao

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11208): 
https://lists.yoctoproject.org/g/linux-yocto/message/11208
Mute This Topic: https://lists.yoctoproject.org/mt/90461468/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Raj, Khem via lists.yoctoproject.org]

Is the sato-sdk on qemuppc also intermittent issue

From: t...@lists.yoctoproject.org  on behalf of 
Richard Purdie 
Sent: Wednesday, April 20, 2022 12:29:29 AM
To: qa-build-notificat...@lists.yoctoproject.org 
; yocto@lists.yoctoproject.org 

Cc: Yocto TSC ; Mittal, Anuj 

Subject: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for 
completed autobuilder build (yocto-3.3.6.rc1)

On Wed, 2022-04-20 at 06:02 +, Pokybuild User wrote:
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and 
> is available at:
>
>
> 
> https://urldefense.com/v3/__https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1__;!!CQl3mcHX2A!XITvSVzpVXHE-hKopFwPzKrqpC-fi6MhLyNlACbodEIHW7S3PBGSenxMWW9GU4pG$
>
>
> Build hash information:
>
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d

3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56821): https://lists.yoctoproject.org/g/yocto/message/56821
Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [kernel-cache][PATCH] cfg/debug: Remove unused test config

[Bruce Ashfield]

On Fri, Apr 15, 2022 at 2:17 PM Dylan Garrett  wrote:
>
> I'm actually on 5.10.104 right now, but I went ahead and made this patch to 
> the master branch of kernel-cache.
>
> I'm working with an ARMv8-based board, but the warning also reproduces with 
> just qemuarm64.

Thanks for the info.

I've merged the patch to the kernel-cache master and backported (with
the relevant syntax changes) to 5.15 and 5.10 as well .. since that
warning is present on older kernels as well.

Cheers,

Bruce

> 
> From: Bruce Ashfield 
> Sent: Wednesday, April 13, 2022 7:02 AM
> To: Dylan Garrett 
> Cc: linux-yocto@lists.yoctoproject.org 
> Subject: [EXTERNAL] Re: [kernel-cache][PATCH] cfg/debug: Remove unused test 
> config
>
> Out of curiosity, which kernel version are you testing this against ?
>
> Since the value is "=n", I know that you are using the master branch of the 
> kernel-cache (I only recently made those changes to prepare for upstream 
> kernel changes) .. and I just want to make a note of the board/kernel 
> combination that is causing you the warning.
>
> Bruce
>
> On Tue, Apr 12, 2022 at 7:33 PM Dylan Garrett  wrote:
>
> This patch removes the warning message when enabling debug-info.scc:
>
> WARNING: linux-yocto-${PV} do_kernel_configcheck: \
> [kernel config]: This BSP contains fragments with warnings:
>
> [INFO]: the following symbols were not found in the active configuration:
>  - CONFIG_TEST
>
> CONFIG_TEST is not a real config and is apparently an artifact from an
> old test.
>
> Signed-off-by: Dylan Garrett 
> ---
>  cfg/debug/debug-info/debug-info.cfg | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/cfg/debug/debug-info/debug-info.cfg 
> b/cfg/debug/debug-info/debug-info.cfg
> index cb19e5a4..1d75b16b 100644
> --- a/cfg/debug/debug-info/debug-info.cfg
> +++ b/cfg/debug/debug-info/debug-info.cfg
> @@ -1,3 +1,2 @@
>  # SPDX-License-Identifier: MIT
> -CONFIG_TEST=n
>  CONFIG_DEBUG_INFO=y
> --
> 2.25.1
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee at 
> its end
> - "Use the force Harry" - Gandalf, Star Trek II
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11206): 
https://lists.yoctoproject.org/g/linux-yocto/message/11206
Mute This Topic: https://lists.yoctoproject.org/mt/90430551/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] [v5.15/standard/x86 and v5.15/standard/preempt-rt/x86] Add GPIO, Time-Aware GPIO, PTP and Time Coordinated computing support for Elkhart Lake in kernel v5.15

[Yongxin Liu]

Hi Bruce,

Could you please help to merge those 23 patches to linux-yocto, branch 
v5.15/standard/x86 and v5.15/standard/preempt-rt/x86?
Those patches add support for GPIP/TGPIO, PTP and TCC(Intel Time Coordinated 
Computing) on Elkhart Lake CRB.
All the patches are from https://github.com/intel/linux-intel-lts.git.


The following changes since commit 4dca1ea3e781c0e5ced6aab37e95efc0f522ea2f:

  Merge branch 'v5.15/standard/base' into v5.15/standard/x86 (2022-04-13 
22:32:47 -0400)

are available in the Git repository at:

  https://github.com/liux2085/linux-yocto v5.15/x86/pull

for you to fetch changes up to f6c5e7b6e8019ea19fe5b77ba2b078e50aae6a4a:

  mfd: intel-ehl-gpio: Introduce MFD framework to PSE GPIO/TGPIO (2022-04-20 
21:09:48 +0800)


Christopher Hall (5):
  x86/tsc: Add TSC support functions to support ART driven Time-Aware GPIO
  drivers/ptp: Add Enhanced handling of reserve fields
  drivers/ptp: Add PEROUT2 ioctl frequency adjustment interface
  drivers/ptp: Add user-space input polling interface
  drivers/ptp: Add support for PMC Time-Aware GPIO Driver

Hao Li (1):
  drivers/ptp: Add COMPV GPIO Mode for PSE TGPIO

Qiang Rao (16):
  tcc: this is kernel driver to interface to TCC PTCM pesudo SRAM
  tcc: parse PTCT table and record pesudo sram ranges
  tcc: update license header
  tcc: L3 psram region should not overlay L2 psram region.
  tcc: driver should exit if no psram entry found in PTCT.
  tcc: tcc drvier should not exit even if no psram entry.
  tcc: return error code to better match varies error scenarios.
  tcc: l3 psram region size could become zero after exclude l2 inclusive 
regions
  tcc: update tcc range end_address.
  tcc: update RTCT table parser to support two versions
  Enable support to read a few whitelisted registers.
  Remove Clock_Cycles_VT from MHL entry.
  Add new IOCTL to read error log buffer.
  Display errlog buffer raw data in kernel log as requested once this 
driver is loaded.
  Fix issue found in acrn uos when convert cacheid to apicid.
  Support RPL in measurement function.

Raymond Tan (1):
  mfd: intel-ehl-gpio: Introduce MFD framework to PSE GPIO/TGPIO

 arch/x86/include/asm/tsc.h |6 +
 arch/x86/kernel/acpi/boot.c|  127 +++
 arch/x86/kernel/tsc.c  |  116 +-
 drivers/Kconfig|2 +
 drivers/Makefile   |1 +
 drivers/gpio/Kconfig   |   11 +
 drivers/gpio/Makefile  |1 +
 drivers/gpio/gpio-ehl-pse-plat.c   |  494 
++
 drivers/mfd/Kconfig|   12 ++
 drivers/mfd/Makefile   |1 +
 drivers/mfd/intel-ehl-gpio.c   |  256 ++
 drivers/ptp/Kconfig|   24 +++
 drivers/ptp/Makefile   |2 +
 drivers/ptp/ptp-intel-pmc-tgpio.c  |  867 
++
 drivers/ptp/ptp-intel-tgpio-plat.c |  715 
+
 drivers/ptp/ptp_chardev.c  |   86 +---
 drivers/ptp/ptp_clock.c|   13 ++
 drivers/tcc/Kconfig|9 +
 drivers/tcc/Makefile   |6 +
 drivers/tcc/tcc_buffer.c   | 1666 
++
 drivers/tcc/tcc_buffer.h   |  241 +
 include/acpi/actbl2.h  |   96 +
 include/linux/ptp_clock_kernel.h   |2 +
 include/uapi/linux/ptp_clock.h |   28 ++-
 24 files changed, 4753 insertions(+), 29 deletions(-)
 create mode 100644 drivers/gpio/gpio-ehl-pse-plat.c
 create mode 100644 drivers/mfd/intel-ehl-gpio.c
 create mode 100644 drivers/ptp/ptp-intel-pmc-tgpio.c
 create mode 100644 drivers/ptp/ptp-intel-tgpio-plat.c
 create mode 100644 drivers/tcc/Kconfig
 create mode 100644 drivers/tcc/Makefile
 create mode 100644 drivers/tcc/tcc_buffer.c
 create mode 100644 drivers/tcc/tcc_buffer.h


Thanks,
Yongxin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11205): 
https://lists.yoctoproject.org/g/linux-yocto/message/11205
Mute This Topic: https://lists.yoctoproject.org/mt/90583841/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] SRC_URI from AWS codecommit with user and password #yocto

[mail2uvijay]

Hi All,

I have an application writing in Qt/QML for specific embedded target, The repo 
for this application is maintained in AWS codecommit which has user and 
password .
How to mentioned in the recipe SRC_URI to fetch from the repo which has 
user/password. I dont have SSH access for the same.
Let me know if you need more details.
tried this https://www.yoctoproject.org/pipermail/yocto/2014-April/019135.html 
no luck.

Regards,
Vijay

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56820): https://lists.yoctoproject.org/g/yocto/message/56820
Mute This Topic: https://lists.yoctoproject.org/mt/90582260/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] package and booting an initramfs image

[Zoran]

Please, read carefully thru this yocto @ thread.

https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html

Zee
___

On Tue, Apr 19, 2022 at 8:27 PM  wrote:
>
> I have a need to package my kernel, dtb, and rootfs manually and then boot 
> this as an initramfs. I'm not sure which files from the deploy/images 
> directory to use. I see there is an rootfs.cpio.gz file so I'm starting with 
> that. If I unpack that I see the kernel Image and dtb in the /boot folder and 
> what appears to be a filesystem in the rest. If I try to boot this as my 
> kernel in u-boot I get this
> Bad Linux ARM64 Image magic!
> ** No partition table - mmc 2 **
> ** No partition table - mmc 2 **
>
> Does this cpio.gz file have everything I need? How do I boot with it and 
> enter an initramfs?
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56819): https://lists.yoctoproject.org/g/yocto/message/56819
Mute This Topic: https://lists.yoctoproject.org/mt/90568270/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] IPv6 Autogeneration Not Persisting

[Syed, Nabeel via lists.yoctoproject.org]

I'm trying to auto-generate IPv6 for interfaces on a ZPE Systems device but not 
able to. It keeps reverting to a value of '1' after a reboot even though the 
config file clearly has '3'. Anyone run into something similar?


root@device:/home/admin# cat /proc/version
Linux version 5.4.137-yocto-standard (oe-user@oe-host) (gcc version 9.3.0 
(GCC)) #1 SMP PREEMPT Sat Jul 31 06:19:39 UTC 2021

root@device:/home/admin# sysctl net.ipv6.conf.sfp0.addr_gen_mode
net.ipv6.conf.sfp0.addr_gen_mode = 1

root@device:/home/admin# cat /etc/sysctl.conf | grep 
net.ipv6.conf.sfp0.addr_gen_mode
net.ipv6.conf.sfp0.addr_gen_mode=3


Nabeel


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56818): https://lists.yoctoproject.org/g/yocto/message/56818
Mute This Topic: https://lists.yoctoproject.org/mt/90581433/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH] Add EROFS support to dm-verity-img class

[Joshua Harley]

Add support for the EROFS image, and it's compressed options, to the
dm-verity-img.bbclass setup, theoretically this is a simple addition to
the list of types however there is a quirk in how Poky handles the
filesystems in poky/meta/classes/image_types.bbclass.

Specifically the 'IMAGE_CMD' and 'IMAGE_FSTYPES' use a hyphen, e.g.
erofs-lz4, however in the image_type bbclass the task for that would be
"do_image_erofs_lz4", replacing the hyphen with an underscore.

As the dm-verity-img.bbclass adds a dependency to the wic image creation
on the do_image_* task then it fails as there is no
"do_image_erofs-lz4", so simply replace the hypen with an underscore.
---
 classes/dm-verity-img.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass
index 16d395b..cc6a7f5 100644
--- a/classes/dm-verity-img.bbclass
+++ b/classes/dm-verity-img.bbclass
@@ -60,7 +60,7 @@ verity_setup() {
 veritysetup --data-block-size=1024 --hash-offset=$SIZE format $OUTPUT 
$OUTPUT | tail -n +2 | process_verity
 }
 
-VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity"
+VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity erofs.verity 
erofs-lz4.verity erofs-lz4hc.verity"
 IMAGE_TYPES += "${VERITY_TYPES}"
 CONVERSIONTYPES += "verity"
 CONVERSION_CMD_verity = "verity_setup ${type}"
@@ -87,6 +87,6 @@ python __anonymous() {
 # If we're using wic: we'll have to use partition images and not the rootfs
 # source plugin so add the appropriate dependency.
 if 'wic' in image_fstypes:
-dep = ' %s:do_image_%s' % (pn, verity_type)
+dep = ' %s:do_image_%s' % (pn, verity_type.replace("-", "_"))
 d.appendVarFlag('do_image_wic', 'depends', dep)
 }
-- 
2.26.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56817): https://lists.yoctoproject.org/g/yocto/message/56817
Mute This Topic: https://lists.yoctoproject.org/mt/90580696/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Richard Purdie]

On Wed, 2022-04-20 at 06:02 +, Pokybuild User wrote:
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and 
> is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
> 
> 
> Build hash information: 
> 
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d

3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56816): https://lists.yoctoproject.org/g/yocto/message/56816
Mute This Topic: https://lists.yoctoproject.org/mt/90579515/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Pokybuild User]

A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1


Build hash information: 

bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
poky: eee9fba7b4d5d7a268a495688039027390894e6d



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56815): https://lists.yoctoproject.org/g/yocto/message/56815
Mute This Topic: https://lists.yoctoproject.org/mt/90578883/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-