date:20210622

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

2021-06-22 Thread Sangeeta Jain

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.9.rc1 We 
are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Monday, June 28.

Thanks,
Sangeeta

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Wednesday, 23 June, 2021 12:33 AM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder 
> build
> (yocto-3.1.9.rc1)
> 
> 
> A build flagged for QA (yocto-3.1.9.rc1) was completed on the autobuilder and 
> is
> available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.9.rc1
> 
> 
> Build hash information:
> 
> bitbake: 0e0af15b84e07e6763300dcd092b980086b9b9c4
> meta-arm: 59974ccd5f1368b2a1c621ba3efd6d2c44c126dd
> meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
> meta-intel: d8bf86ae6288ae520b8ddd7209a0b448b9693f48
> meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
> oecore: ac8181d9b9ad8360f7dba03aba8b00f008c6ebb4
> poky: 43060f59ba60a0257864f1f7b25b51fac3f2d2cf
> 
> 
> 
> 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 (#53942): https://lists.yoctoproject.org/g/yocto/message/53942
Mute This Topic: https://lists.yoctoproject.org/mt/83730832/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021

2021-06-22 Thread Trevor Woerner

Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021
archive: 
https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Michael Halstead, Paul Barker, Richard
Purdie, Scott Murray, Steve Sakoman, Tony Tascioglu, Trevor Gamblin,
Alejandro Hernandez, Alexandre Belloni, Jan-Simon Möller, Randy MacLeod

== notes ==
- 3.4 m1 (honister) through QA, couple issue found, in review by TSC to decide
on release
- 3.1.9 (dunfell) currently being build then sent to QA
- thanks to PaulG for tracking down null pointer in cgroups mount code (and
others) that have led to solving some AB hangs
- the rcu dump AB vm hangs are still occurring
- 2 new manual sections: reproducible builds, and YP compatible
- multiconfig changes continue to cause issues
- still lots of AB-INT issues, we’re working on trying to define the load
pattern that causes these issues

== general ==
RP: special thanks to Paul Gortmaker for finding the null pointer issue to fix
the LTP builds


PaulB: still working on the pr-server changes. my changes work on my setup but
don’t seem to do well on the AB. if i enable parallelism in my builds
then the oom-killer gets busy. it’s annoying that the output from a test
is buffered until the test is finished, so if a test hangs then i can’t
find out which one is hanging. it looks like we’ll have to dig into
async-io or python parallelism to see if there’s something wrong there
or at least figure out how to get more output before a test finishes
RP: did you look at the trace output i found
PaulB: yes, but not exactly sure what i’m looking at
RP: if bitbake server starts one of the servers, then it’s responsible for
taking it out when it shuts down. so they run individually, but there is
some sharing. that traceback suggests to me that it’s trying to shut down
the pr server at shutdown time but not succeeding. sometimes the sqlite
database takes time to sync to disk for example (especially when there
is high io) but bitbake ends up blocked. it looks like some contention
between the parse threads and the locks. when doing python parallel there
are 2 systems and we have to make sure to not mix the two.
PaulB: in one case it looks like one of the comm sockets is already closed,
but the server is waiting for it to close again, but i would think we’d
get the same traceback every time
RP: maybe it’s stuck somewhere where it shouldn’t be, which makes it skip
some error/exit handling. or maybe add more debug code
PaulB: yes, i think adding timeouts to every wait/callback to see which ones
are timing out
RP: can python give you a dump of what’s in every waitstate?
PaulB: not sure, i’ll have to look at what python provides. bitbake isn’t
what’s telling prserv to exit on the cluster, but it is on my builds
RP: that seems unlikely
PaulB: i can’t generate the same conditions locally as what we’re seeing
on the AB. because of thread contention there seems to be, perhaps, a
resource exhaustion that i can’t reproduce
RP: put a “sleep 5” in the shutdown path in the prserv. it would cause
hashserve to exist longer than bitbake
PaulB: or backout the use of multiprocessing, keep the new json rpc system.
but do a more traditional fork() to start the process up
RP: i suspect we did the fork() for a reason
PaulB: multiprocessing didn’t exist back then
RP: it did, but it was broken. i sent a cooker daemon log which should show
what was running at the time. so we should be able to reverse engineer
what was going on at that time. i’m getting good at reading those, so i
can probably read them and tell you what tests were running at the time
PaulB: if we could just run that one test
RP: i would run just the prserv selftest and put that sleep in there. i’m
convinced it’s one of them
PaulB: i’m afraid i’m going to have to hand this off to someone else.
i’ll give one more push but then i’m out of ideas
RP: okay. it’d be good to get that in because i’m looking forward to it


TrevorW: move to SPDX license identifiers
RP: we have
TrevorW: classes and ptests yes, but not recipes and other places of oecore
RP: any place where we’re writing python we have. it’s a nice cleanup
thing, we’ve been embracing it. we’ve made some of the changes.
we’ve done it with code. the problem with recipes is that if we put that
at the top of the license it’ll get confused with the LICENCE field. so
we’re not quite sure what to do in that case
PaulB: i've been using a linting tool that checks for these identifiers.
again, the problem of what license to put on the recipe and for patches
etc (https://reuse.software/spec)
RP:

[yocto-announce] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

2021-06-22 Thread Vineela

Hello,



We are pleased to announce the first milestone release for Yocto Project 3.4 
(yocto-3.4_M1) is now available for download.



Download:



http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1



bitbake: 398a1686176c695d103591089a36e25173f9fd6e

meta-arm: 6c3d62c776fc45b4bae47d178899e84b17248b31

meta-gplv2: 1ee1a73070d91e0c727f9d0db11943a61765c8d9

meta-intel: 0937728bcd98dd13d2c6829e1cd604ea2e53e5cd

meta-mingw: bfd22a248c0db4c57d5a72d675979d8341a7e9c1

oecore: 3b2903ccc791d5dedd84c75227f38ae4c8d29251

poky: 59d93693bf24e02ca0f05fe06d96a46f4f0f1bf8



Full Test Report:



http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1/testreport.txt



Thank you.



Vineela Tummalapalli,

Yocto Project Build and Release

vineela.tummalapa...@intel.com


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

[yocto] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

2021-06-22 Thread Vineela

Hello,



We are pleased to announce the first milestone release for Yocto Project 3.4 
(yocto-3.4_M1) is now available for download.



Download:



http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1



bitbake: 398a1686176c695d103591089a36e25173f9fd6e

meta-arm: 6c3d62c776fc45b4bae47d178899e84b17248b31

meta-gplv2: 1ee1a73070d91e0c727f9d0db11943a61765c8d9

meta-intel: 0937728bcd98dd13d2c6829e1cd604ea2e53e5cd

meta-mingw: bfd22a248c0db4c57d5a72d675979d8341a7e9c1

oecore: 3b2903ccc791d5dedd84c75227f38ae4c8d29251

poky: 59d93693bf24e02ca0f05fe06d96a46f4f0f1bf8



Full Test Report:



http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1/testreport.txt



Thank you.



Vineela Tummalapalli,

Yocto Project Build and Release

vineela.tummalapa...@intel.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53940): https://lists.yoctoproject.org/g/yocto/message/53940
Mute This Topic: https://lists.yoctoproject.org/mt/83727016/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.1.9.rc1)

2021-06-22 Thread Pokybuild User


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


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


Build hash information: 

bitbake: 0e0af15b84e07e6763300dcd092b980086b9b9c4
meta-arm: 59974ccd5f1368b2a1c621ba3efd6d2c44c126dd
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: d8bf86ae6288ae520b8ddd7209a0b448b9693f48
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: ac8181d9b9ad8360f7dba03aba8b00f008c6ebb4
poky: 43060f59ba60a0257864f1f7b25b51fac3f2d2cf



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 (#53939): https://lists.yoctoproject.org/g/yocto/message/53939
Mute This Topic: https://lists.yoctoproject.org/mt/83717688/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW25`21

2021-06-22 Thread Stephen Jolley

Current Dev Position: YP 3.4 M2

Next Deadline: 12th July 2021 YP 3.4 M2 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 24th at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday July 13th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday June 22nd at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.4 M1 has been through QA pending release approval with two QA
issues highlighted.
*   YP 3.1.9 is being built ready for QA.
*   Big thanks to Paul Gortmaker for tracking down the cause of an LTP
null pointer dereference (and other errors) within the cgroups mount code
which was responsible for several of our LTP hangs. The issue was introduced
in new code between 5.0 and 5.1 in the kernel and had been present for a
while. The fix is now making its way through various kernel trees upstream.
*   Sadly, the above fix did not resolve the "rcu" autobuilder VM hangs
we are seeing occasionally. These are odd in that they affect kvm and
non-kvm builds (x86 and arm seen on x86-64 hosts), they pin the VM at
300-400% CPU usage and the VM will respond to pings but no ssh or console
output. The rcu dumps from the kernel are likely a symptom that something is
wrong rather than the cause and often look incomplete. It is as if some
instantaneous host load breaks timers in a way the guest cannot recover or
continue execution from. We're continuing to try and narrow this down but it
is proving elusive and progress is slow, any insight anyone may have would
be welcome.
*   There are new manual sections that have recently been added on

Reproducible Builds and

Yocto Project Compatible.
*   We continue to deal with an issue with centos8 kernels having what
looks like bad bounds checking on the utimensat_time64 32 bit syscalls where
the syscall was backported into a kernel point release. We're working on
reporting it upstream.
*   We have a 10th anniversary T-shirt and some other Yocto Project
items (hoody, stickers, mugs etc.) now available at
 https://yoctoproject.org/shop (EU and
Americas sources)
*   The multiconfig changes in bitbake continue to cause problems, we
still need simpler test cases to reproduce issues rather than huge builds.
The existing patches seem to fix some workloads and break others. Richard is
trying to fix but trying to fix autobuilder issues and other problems and
these are slow builds to debug.
*   Intermittent autobuilder issues continue to occur and continue to be
at record high levels. You can see the list of failures we're continuing to
see by searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

We are working to identify the load pattern on the infrastructure that seems
to trigger these.

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.4. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.4 Milestone Dates:

*   YP 3.4 M1 is in review by the TSC
*   YP 3.4 M2 build date 2021/07/12
*   YP 3.4 M2 Release date 2021/07/23
*   YP 3.4 M3 build date 2021/08/23 (Feature Freeze)
*   YP 3.4 M3 Release date 2021/09/03
*   YP 3.4 M4 build date 2021/10/04
*   YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

*   YP 3.1.9 is being built
*   YP 3.1.9 release date 2021/07/02
*   YP 3.3.2 build date 2021/07/19
*   YP 3.3.2 release date 2021/07/30
*   YP 3.1.10 build date 2021/07/26
*   YP 3.1.10 release date 2021/08/06
*

[linux-yocto] [PATCH 2/3] nxp-imx8: Enable the depended kernel options

2021-06-22 Thread Xiaolei Wang

Some kernel options have dependency on other options, we
should also enable them otherwise we would observe the following warnings:
'CONFIG_ARM_CPUIDLE' last val (y) and .config val (n) do not match
'CONFIG_LEDS_TRIGGER_DISK' last val (y) and .config val (n) do not match
'CONFIG_VIDEO_MXC_CAPTURE' last val (y) and .config val (n) do not match

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx8/nxp-imx8.cfg | 5 +
 1 file changed, 5 insertions(+)

diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
index c13b91fe..cbce7d2f 100644
--- a/bsp/nxp-imx8/nxp-imx8.cfg
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -13,6 +13,7 @@ CONFIG_TRANSPARENT_HUGEPAGE=y
 
 #
 # CPU idle
+CONFIG_CPU_IDLE=y
 CONFIG_ARM_CPUIDLE=y
 CONFIG_ARM_PSCI_CPUIDLE=y
 
@@ -26,6 +27,7 @@ CONFIG_MFD_SYSCON=y
 CONFIG_AHCI_IMX=y
 CONFIG_SATA_AHCI=y
 CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_LEDS_TRIGGERS=y
 
 #
 ## PCI
@@ -284,6 +286,7 @@ CONFIG_IMX_SC_WDT=y
 #
 ## Multimedia core support
 #
+CONFIG_MEDIA_PLATFORM_SUPPORT=y
 CONFIG_MEDIA_SUPPORT=y
 CONFIG_MEDIA_CAMERA_SUPPORT=y
 CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
@@ -309,6 +312,7 @@ CONFIG_V4L_MEM2MEM_DRIVERS=y
 #
 ## Graphics support
 #
+CONFIG_ARCH_RENESAS=y
 CONFIG_VGA_ARB=y
 CONFIG_VGA_ARB_MAX_GPUS=16
 CONFIG_IMX8_PRG=y
@@ -400,6 +404,7 @@ CONFIG_SND=y
 CONFIG_SND_DYNAMIC_MINORS=y
 CONFIG_SND_USB_AUDIO=m
 CONFIG_SND_SOC=y
+CONFIG_SND_SOC_FSL_ASRC=y
 CONFIG_SND_SOC_FSL_EASRC=y
 CONFIG_SND_IMX_SOC=y
 CONFIG_SND_SOC_IMX_AK4458=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9996): 
https://lists.yoctoproject.org/g/linux-yocto/message/9996
Mute This Topic: https://lists.yoctoproject.org/mt/83709973/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 3/3] nxp-imx8: Delete the obsolete kernel options

2021-06-22 Thread Xiaolei Wang

Delete some kernel configurations of DPAA2, ACPI and GPIO, these
configurations are not used, so there is no need to open them

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx8/nxp-imx8.cfg | 26 --
 1 file changed, 26 deletions(-)

diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
index cbce7d2f..d9ea3caf 100644
--- a/bsp/nxp-imx8/nxp-imx8.cfg
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -99,20 +99,15 @@ CONFIG_CRYPTO_DEV_FSL_CAAM=y
 CONFIG_CRYPTO_DEV_FSL_CAAM_SM=y
 CONFIG_CRYPTO_DEV_FSL_CAAM_SM_TEST=m
 CONFIG_CRYPTO_DEV_FSL_CAAM_SECVIO=y
-CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y
 CONFIG_CRYPTO_PCBC=m
 CONFIG_CRYPTO_XCBC=m
 CONFIG_CRYPTO_VMAC=m
 CONFIG_CRYPTO_SM3=m
 CONFIG_CRYPTO_STREEBOG=m
-CONFIG_CRYPTO_ANUBIS=m
 CONFIG_CRYPTO_DES=m
 CONFIG_CRYPTO_FCRYPT=m
-CONFIG_CRYPTO_KHAZAD=m
 CONFIG_CRYPTO_SALSA20=m
-CONFIG_CRYPTO_SEED=m
 CONFIG_CRYPTO_SM4=m
-CONFIG_CRYPTO_TEA=m
 
 #
 ## Input device support
@@ -121,7 +116,6 @@ CONFIG_MMC=y
 CONFIG_MMC_BLOCK_MINORS=32
 CONFIG_MMC_ARMMMCI=y
 CONFIG_MMC_SDHCI=y
-CONFIG_MMC_SDHCI_ACPI=y
 CONFIG_MMC_SDHCI_PLTFM=y
 CONFIG_MMC_SDHCI_OF_ARASAN=y
 CONFIG_MMC_SDHCI_OF_ESDHC=y
@@ -136,7 +130,6 @@ CONFIG_KEYBOARD_ADC=m
 CONFIG_KEYBOARD_GPIO=y
 CONFIG_KEYBOARD_SNVS_PWRKEY=y
 CONFIG_KEYBOARD_IMX_SC_PWRKEY=y
-CONFIG_KEYBOARD_CROS_EC=y
 CONFIG_INPUT_TOUCHSCREEN=y
 CONFIG_TOUCHSCREEN_ATMEL_MXT=m
 CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C=m
@@ -153,26 +146,19 @@ CONFIG_GPIOLIB=y
 CONFIG_GPIO_SYSFS=y
 CONFIG_GPIO_DWAPB=y
 CONFIG_GPIO_MB86S7X=y
-CONFIG_GPIO_MPC8XXX=y
 CONFIG_GPIO_PL061=y
 CONFIG_GPIO_XGENE=y
 CONFIG_GPIO_MAX732X=y
 CONFIG_GPIO_PCA953X=y
 CONFIG_GPIO_PCA953X_IRQ=y
-CONFIG_GPIO_MAX77620=y
 
 #
 ## Regulator Driver
 #
 CONFIG_REGULATOR=y
 CONFIG_REGULATOR_FIXED_VOLTAGE=y
-CONFIG_REGULATOR_AXP20X=y
-CONFIG_REGULATOR_BD718XX=y
-CONFIG_REGULATOR_BD9571MWV=y
 CONFIG_REGULATOR_FAN53555=y
 CONFIG_REGULATOR_GPIO=y
-CONFIG_REGULATOR_HI6421V530=y
-CONFIG_REGULATOR_MAX77620=y
 CONFIG_REGULATOR_MAX8973=y
 CONFIG_REGULATOR_PCA9450=y
 CONFIG_REGULATOR_PFUZE100=y
@@ -201,8 +187,6 @@ CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
 ## CPU frequency scaling drivers
 #
 CONFIG_CPUFREQ_DT=y
-CONFIG_ACPI_CPPC_CPUFREQ=m
-CONFIG_ARM_SCPI_CPUFREQ=y
 CONFIG_ARM_IMX_CPUFREQ_DT=y
 
 #
@@ -222,8 +206,6 @@ CONFIG_MTD_DATAFLASH=y
 CONFIG_MTD_SST25L=y
 CONFIG_MTD_RAW_NAND=y
 CONFIG_MTD_NAND_DENALI_DT=y
-CONFIG_MTD_NAND_GPMI_NAND=y
-CONFIG_MTD_NAND_FSL_IFC=y
 CONFIG_MTD_SPI_NOR=y
 
 #
@@ -266,7 +248,6 @@ CONFIG_I2C_SLAVE=y
 #
 CONFIG_THERMAL=y
 CONFIG_THERMAL_WRITABLE_TRIPS=y
-CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
 CONFIG_CPU_THERMAL=y
 CONFIG_THERMAL_EMULATION=y
 CONFIG_IMX_SC_THERMAL=y
@@ -339,8 +320,6 @@ CONFIG_DRM_MALI_DISPLAY=m
 CONFIG_DRM_NOUVEAU=m
 CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=y
 CONFIG_DRM_NOUVEAU_BACKLIGHT=y
-CONFIG_DRM_RCAR_LVDS=m
-CONFIG_DRM_RCAR_WRITEBACK=y
 CONFIG_DRM_PANEL=y
 CONFIG_DRM_PANEL_SIMPLE=y
 CONFIG_DRM_PANEL_RAYDIUM_RM67191=y
@@ -410,12 +389,8 @@ CONFIG_SND_IMX_SOC=y
 CONFIG_SND_SOC_IMX_AK4458=y
 CONFIG_SND_SOC_IMX_AK5558=y
 CONFIG_SND_SOC_IMX_AK4497=y
-CONFIG_SND_SOC_IMX_WM8960=y
-CONFIG_SND_SOC_IMX_WM8524=y
-CONFIG_SND_SOC_IMX_CS42888=y
 CONFIG_SND_SOC_IMX_MICFIL=y
 CONFIG_SND_SOC_IMX_RPMSG=y
-CONFIG_SND_SOC_IMX_MQS=y
 CONFIG_SND_SOC_IMX_SPDIF=y
 CONFIG_SND_SOC_IMX_AUDMIX=y
 
@@ -500,7 +475,6 @@ CONFIG_OF_OVERLAY=y
 CONFIG_MAILBOX=y
 CONFIG_IMX_MBOX=y
 CONFIG_IMX_SCU=y
-CONFIG_IMX_SCU_SOC=y
 CONFIG_IMX_DSP=y
 CONFIG_IMX_SCU_PD=y
 CONFIG_IIO=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9997): 
https://lists.yoctoproject.org/g/linux-yocto/message/9997
Mute This Topic: https://lists.yoctoproject.org/mt/83709974/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 1/3] nxp-imx8: Drop the redundant kernel options

2021-06-22 Thread Xiaolei Wang

CRYPTO_CBC has been selected as Y by XFRM_ESP, CRYPTO_CTS and
CRYPTO_XTS have been selected as Y by FS_ENCRYPTION_ALGS,
CONFIG_CRYPTO_MD4, CONFIG_CRYPTO_MD5 and CONFIG_CRYPTO_SHA512
have been selected as Y by CIFS. Therefore, these configurations
do not need to be enabled in the kernel config

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx8/nxp-imx8.cfg | 6 --
 1 file changed, 6 deletions(-)

diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
index ae985f5c..c13b91fe 100644
--- a/bsp/nxp-imx8/nxp-imx8.cfg
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -77,19 +77,13 @@ CONFIG_CRYPTO_TEST=m
 CONFIG_CRYPTO_CHACHA20POLY1305=m
 CONFIG_CRYPTO_ECHAINIV=y
 CONFIG_CRYPTO_TLS=m
-CONFIG_CRYPTO_CBC=m
 CONFIG_CRYPTO_CFB=m
-CONFIG_CRYPTO_CTS=m
 CONFIG_CRYPTO_LRW=m
 CONFIG_CRYPTO_OFB=m
-CONFIG_CRYPTO_XTS=m
-CONFIG_CRYPTO_MD4=m
-CONFIG_CRYPTO_MD5=m
 CONFIG_CRYPTO_RMD128=m
 CONFIG_CRYPTO_RMD160=m
 CONFIG_CRYPTO_RMD256=m
 CONFIG_CRYPTO_RMD320=m
-CONFIG_CRYPTO_SHA512=m
 CONFIG_CRYPTO_TGR192=m
 CONFIG_CRYPTO_WP512=m
 CONFIG_CRYPTO_BLOWFISH=m
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9995): 
https://lists.yoctoproject.org/g/linux-yocto/message/9995
Mute This Topic: https://lists.yoctoproject.org/mt/83709971/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][master yocto-5.13][PATCH] kfence: Initial enablement

2021-06-22 Thread He Zhe

Kernel Electric-Fence (KFENCE) is a low-overhead sampling-based memory safety
error detector. KFENCE detects heap out-of-bounds access, use-after-free, and
invalid-free errors.

KFENCE is designed to be enabled in production kernels, and has near zero
performance overhead. Compared to KASAN, KFENCE trades precision for
performance.

Signed-off-by: He Zhe 
---
 features/kfence/kfence.cfg | 2 ++
 features/kfence/kfence.scc | 5 +
 2 files changed, 7 insertions(+)
 create mode 100644 features/kfence/kfence.cfg
 create mode 100644 features/kfence/kfence.scc

diff --git a/features/kfence/kfence.cfg b/features/kfence/kfence.cfg
new file mode 100644
index ..6f4875c3
--- /dev/null
+++ b/features/kfence/kfence.cfg
@@ -0,0 +1,2 @@
+# SPDX-License-Identifier: MIT
+CONFIG_KFENCE=y
diff --git a/features/kfence/kfence.scc b/features/kfence/kfence.scc
new file mode 100644
index ..741bca26
--- /dev/null
+++ b/features/kfence/kfence.scc
@@ -0,0 +1,5 @@
+# SPDX-License-Identifier: MIT
+define KFEATURE_DESCRIPTION "a low-overhead sampling-based memory safety error 
detector"
+define KFEATURE_COMPATIBILITY arch
+
+kconf non-hardware kfence.cfg
-- 
2.17.1


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

[yocto] Update APTCONF_TARGET manually

2021-06-22 Thread Mauro Ziliani

Hi all
I move all TMPDIR in another folder
The EXTRA_DISTRO_FETAURES += "package_managent"
PACKAGE_CLASS := " package_deb "

When I build the image the package_manager try to find the debs in the older 
folder.
I see that this problem is in apt/apt.conf of image working dir.
How can I change manually the value of APTCONF_TARGET?
Where the APTCONF_TARGET value is stored?
Best regards,
MZ

Sent from Mailspring (https://getmailspring.com/), the best free email app for 
work

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

Re: [yocto] Empty source package when using devtool

2021-06-22 Thread Frederic Martinsons

Hello, I dug further into yocto classes and I think I found what is going on.

All seems to come from the fact that gcc debug-prefix-map and macro-prefix-map 
options are statically defined in bitbake.conf to

> 
> DEBUG_PREFIX_MAP ?=
> "-fmacro-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}
> \
> -fdebug-prefix-map=${WORKDIR}=/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}
> \
> -fdebug-prefix-map=${STAGING_DIR_HOST}= \
> -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \
> "
> 
> 
> 

I'll took an example to try to be clearer. Let's say that I devtool modify the 
glib-2.0 package. Without any configuration, sources will be extracted in 
${BDIR}/workspace/sources/glib-2.0.
Build directory is set by externalsrc.bbclass to 
${BDIR}/tmp/work/${arch}-${distro}/glib-2.0/${PN}/${EXTENDPE}${PV}-${PR}/${BPN}/${BPN}-${PV}
 (the real path doesn't matter, what is matter is that B is not under devtool 
spaces).

This lead to have pretty long relative path in gcc compilation line (sotheming 
like  -c ../../../../../../../../worspace/sources/glib-2.0/glib/gmain.c for 
example). Hence the debug-prefix-map could not be appplied.
After the compilation stage, package.bbclass (via splitdebuginfo), there is an 
extraction of sources path via dwarf format parsing. We ended up parsing 
something like

- /workspace/sources/glib-2.0/glib/gmain.c

instead of

- /usr/src/debug/glib-2.0/1_2.58.3-r0.2/glib-2.58.3/glib/gmain.c

I patch externalsrc.bbclass to dynamically caculate correct debug-prefix-map 
and prepend to DEBUG_PREFIX_MAP variable, I also patch the package.bbclass to 
add a condition when EXTERNALSRC is defined to change the way the sources are 
found and copied to packages-split/${pkg}-src.

I would greatly appreciate if there is a yocto guru around there to tell me 
what he thinks about all of this (bug or wrong configuration ?) and if my 
assumptions are correct (I assume this was a compiling/packaging problem 
instead of a pure devtool one)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53936): https://lists.yoctoproject.org/g/yocto/message/53936
Mute This Topic: https://lists.yoctoproject.org/mt/83622035/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.1.9.rc1)

[yocto] Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021

[yocto-announce] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

[yocto] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

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

[yocto] Yocto Project Status WW25`21

[linux-yocto] [PATCH 2/3] nxp-imx8: Enable the depended kernel options

[linux-yocto] [PATCH 3/3] nxp-imx8: Delete the obsolete kernel options

[linux-yocto] [PATCH 1/3] nxp-imx8: Drop the redundant kernel options

[linux-yocto][yocto-kernel-cache][master yocto-5.13][PATCH] kfence: Initial enablement

[yocto] Update APTCONF_TARGET manually

Re: [yocto] Empty source package when using devtool

12 matches

Site Navigation

Mail list logo

Footer information