[yocto] Can't parse unset of variables with override

2021-08-16 Thread Zhenfei Tai via lists.yoctoproject.org 
Hi,

I'm not sure if this has been brought up already. After the syntax change
from underscore to colon, I noticed the error when using unset on variables
with override. Could someone confirm if this is expected?

# in bbappend
unset SRCREV:xyz

# in build log
ERROR: ParseError at /../abc%.bbappend:3: unparsed line: 'unset SRCREV:xyz

Thanks,
Zhenfei

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

Re: [yocto] Hardknott systemd-journald issue

2021-08-16 Thread Zoran 
Hello Jupiter,

This might provide you a great help:
https://askubuntu.com/questions/864722/where-is-journalctl-data-stored

Namely:





*Usually the storage directory is /var/log/journal or /run/log/journal, but
it doesn't have to necessarily exist in your system.If you just want to
check the amount of space that the journal is currently occupying on your
disk, simply type:$ journalctl --disk-usage*

You also can combine the df command (look into man df).

Zee
___


On Tue, Aug 17, 2021 at 4:18 AM JH  wrote:

> Hi,
>
> I've just upgraded from Zeus to Hardknott with the kernel 5.10.59, the
> /run/log/journal was running out of space and crashed, is it a kernel
> issue or Hardknott build issue?
>
> I never seen that issue in Zeus, I thought that systemd-journald
> should be capable of detecting the space, if it is no log space, stop
> writing rather crashing the tmpfs
>
> [13749.397288] systemd-journald[97]: Failed to open runtime journal:
> No space left on device
> [13749.439047] systemd-journald[97]: File
> /run/log/journal/4ba2cd613d004916863e30730800bb69/system.journal
> corrupted or uncleanly shut down, renaming and replacing.
>
> Thank you.
>
> Kind regards,
>
> - jh
>
> 
>
>

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

Re: [yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

2021-08-16 Thread Khem Raj 
On Mon, Aug 16, 2021 at 6:36 PM Sinan Kaya  wrote:

> Dynamically linked protoc.exe is failing as follows:
>
> [libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
> File already exists in database: google/protobuf/descriptor.proto
> [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
> GeneratedDatabase()->Add(encoded_file_descriptor, size):
>
> Switch to static linkage per upstream recommendation.
>
> Signed-off-by: Sinan Kaya 
> ---
>  recipes-devtools/protobuf/protobuf_%.bbappend | 1 +
>  1 file changed, 1 insertion(+)
>  create mode 100644 recipes-devtools/protobuf/protobuf_%.bbappend
>
> diff --git a/recipes-devtools/protobuf/protobuf_%.bbappend
> b/recipes-devtools/protobuf/protobuf_%.bbappend
> new file mode 100644
> index 000..7e62ff6
> --- /dev/null
> +++ b/recipes-devtools/protobuf/protobuf_%.bbappend
> @@ -0,0 +1 @@
> +EXTRA_OECONF:append:class-nativesdk = " --disable-shared"


This is not an inert change can it use some mingw specific override as well

>
> --
> 2.17.1
>
>
> 
>
>

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

[yocto] M+ & H bugs with Milestone Movements WW33

2021-08-16 Thread Stephen Jolley 
All,

YP M+ or high bugs which moved to a new milestone in WW33 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13975

cve-checker: save to alternate file format like JSON

randy.macl...@windriver.com

unassig...@yoctoproject.org

3.4 M2

3.4 M3


 

  14127

cve-check falsely indicates a vulnerabily to be patched

randy.macl...@windriver.com

unassig...@yoctoproject.org

3.4 M2

3.4 M3

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


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

[yocto] Enhancements/Bugs closed WW33!

2021-08-16 Thread Stephen Jolley 
All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

2


mhalst...@linuxfoundation.org

2


r...@burtonini.com

2


Grand Total

6

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

[yocto] Current high bug count owners for Yocto Project 3.4

2021-08-16 Thread Stephen Jolley 
All,

Below is the list as of top 50 bug owners as of the end of WW33 of who have
open medium or higher bugs and enhancements against YP 3.4.   There are 52
possible work days left until the final release candidates for YP 3.4 needs
to be released.


Who

Count


r...@burtonini.com

32


michael.opdenac...@bootlin.com

29


david.re...@windriver.com

22


richard.pur...@linuxfoundation.org

20


bruce.ashfi...@gmail.com

18


trevor.gamb...@windriver.com

12


timothy.t.orl...@intel.com

12


bluelightn...@bluelightning.org

10


randy.macl...@windriver.com

10


jpewhac...@gmail.com

10


sakib.sa...@windriver.com

10


tony.tascio...@windriver.com

8


kai.k...@windriver.com

7


hongxu@windriver.com

4


qi.c...@windriver.com

4


chee.yang@intel.com

3


alexandre.bell...@bootlin.com

3


mostthings...@gmail.com

3


mingli...@windriver.com

3


akuster...@gmail.com

3


yf...@uwaterloo.ca

2


yi.z...@windriver.com

2


raj.k...@gmail.com

2


alejan...@enedino.org

2


jae...@xilinx.com

2


ms...@mvista.com

2


john.kaldas.e...@gmail.com

1


shac...@vdoo.com

1


diego.sue...@arm.com

1


ydir...@free.fr

1


mister...@web.de

1


dl...@gmx.de

1


devendra.tew...@gmail.com

1


open.sou...@oleksandr-kravchuk.com

1


sangeeta.j...@intel.com

1


pokyli...@reliableembeddedsystems.com

1


stacygaikov...@gmail.com

1


nicolas.deche...@linaro.org

1


yoctoproj...@cookiesoft.de

1


mark.ha...@kernel.crashing.org

1


jon.ma...@arm.com

1


thomas.per...@bootlin.com

1


martin.ja...@gmail.com

1


douglas.ro...@taitradio.com

1


kerg...@gmail.com

1


p...@pbarker.dev

1


naveen.kumar.sa...@intel.com

1


jeanmarie.lemeta...@gmail.com

1


to...@cybernetics.com

1


aeh...@gmail.com

1


vinay.m.e...@gmail.com

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2021-08-16 Thread Stephen Jolley 
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 379
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

[yocto] Hardknott systemd-journald issue

2021-08-16 Thread JH 
Hi,

I've just upgraded from Zeus to Hardknott with the kernel 5.10.59, the
/run/log/journal was running out of space and crashed, is it a kernel
issue or Hardknott build issue?

I never seen that issue in Zeus, I thought that systemd-journald
should be capable of detecting the space, if it is no log space, stop
writing rather crashing the tmpfs

[13749.397288] systemd-journald[97]: Failed to open runtime journal:
No space left on device
[13749.439047] systemd-journald[97]: File
/run/log/journal/4ba2cd613d004916863e30730800bb69/system.journal
corrupted or uncleanly shut down, renaming and replacing.

Thank you.

Kind regards,

- jh

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

[yocto] [meta-mingw] [PATCH 2/3] protobuf-c: static link when generating sdk

2021-08-16 Thread Sinan Kaya 
[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya 
---
 recipes-devtools/protobuf-c/protobuf-c_%.bbappend | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 recipes-devtools/protobuf-c/protobuf-c_%.bbappend

diff --git a/recipes-devtools/protobuf-c/protobuf-c_%.bbappend 
b/recipes-devtools/protobuf-c/protobuf-c_%.bbappend
new file mode 100644
index 000..7e62ff6
--- /dev/null
+++ b/recipes-devtools/protobuf-c/protobuf-c_%.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF:append:class-nativesdk = " --disable-shared"
-- 
2.17.1


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

[yocto] [meta-mingw] [PATCH 3/3] grpc: static link tools when generating SDK

2021-08-16 Thread Sinan Kaya 
[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya 
---
 recipes-devtools/grpc/grpc_%.bbappend | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 recipes-devtools/grpc/grpc_%.bbappend

diff --git a/recipes-devtools/grpc/grpc_%.bbappend 
b/recipes-devtools/grpc/grpc_%.bbappend
new file mode 100644
index 000..cbccf74
--- /dev/null
+++ b/recipes-devtools/grpc/grpc_%.bbappend
@@ -0,0 +1,2 @@
+EXTRA_OECMAKE:remove:class-nativesdk = "-DBUILD_SHARED_LIBS=ON"
+EXTRA_OECMAKE:append:class-nativesdk = " -DBUILD_SHARED_LIBS=OFF"
-- 
2.17.1


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

[yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

2021-08-16 Thread Sinan Kaya 
Dynamically linked protoc.exe is failing as follows:

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya 
---
 recipes-devtools/protobuf/protobuf_%.bbappend | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 recipes-devtools/protobuf/protobuf_%.bbappend

diff --git a/recipes-devtools/protobuf/protobuf_%.bbappend 
b/recipes-devtools/protobuf/protobuf_%.bbappend
new file mode 100644
index 000..7e62ff6
--- /dev/null
+++ b/recipes-devtools/protobuf/protobuf_%.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF:append:class-nativesdk = " --disable-shared"
-- 
2.17.1


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

[linux-yocto] [yocto-kernel-cache yocto-5.10]: nxp-s32g2xx: change CAN LLCE config to y to fix build warning

2021-08-16 Thread Zhantao Tang 

Hi Bruce,

There is an patch related with CAN LLCE feature to fix a kernel build warning 
for nxp-s32g2xx bsp,
would you please help to merge this patch into yocto-kernel-cache, branch 
yocto-5.10?


Thanks,
Zhantao

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10283): 
https://lists.yoctoproject.org/g/linux-yocto/message/10283
Mute This Topic: https://lists.yoctoproject.org/mt/84920893/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] nxp-s32g2xx: change CAN LLCE config to y to fix build warning

2021-08-16 Thread Zhantao Tang 
Due to the rc5 update of bsp30, the CAN_LLCE kernel config should
change to y to fix the following build warning:

  do_kernel_configcheck: [kernel config]:
specified values did not make it into the kernel's final configuration:
  [NOTE]: 'CONFIG_CAN_LLCE' last val (m) and .config val (n) do not match

This patch will fix it.

Signed-off-by: Zhantao Tang 
---
 bsp/nxp-s32g2xx/nxp-s32g2xx.cfg | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg b/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg
index cf5be935..75895338 100644
--- a/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg
+++ b/bsp/nxp-s32g2xx/nxp-s32g2xx.cfg
@@ -147,7 +147,8 @@ CONFIG_BLK_DEV_NVME=y
 CONFIG_NVME_TARGET=y
 
 #LLCE
-CONFIG_CAN_LLCE=m
+CONFIG_CAN_LLCE=y
+CONFIG_CAN_LLCE_CONTROLLER=m
 
 # Regulator configuration
 CONFIG_REGULATOR=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10284): 
https://lists.yoctoproject.org/g/linux-yocto/message/10284
Mute This Topic: https://lists.yoctoproject.org/mt/84920894/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.10 only][PATCH] bsp: axxia: add new kernel options for axm56xx

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

This patch includes modifications as below:
1. add CONFIG_PROFILING and CONFIG_ARM_CCN_PMU to enable
ccn for axm56xx.
2. add CONFIG_ARM_SP804_WATCHDOG_AXXIA to enable sp804
watchdog for axm56xx.

Signed-off-by: Quanyang Wang 
---
 bsp/axxiaarm/axxia-common.cfg | 1 +
 bsp/axxiaarm64/axxiaarm64.cfg | 6 ++
 2 files changed, 7 insertions(+)

diff --git a/bsp/axxiaarm/axxia-common.cfg b/bsp/axxiaarm/axxia-common.cfg
index 1fe2f96be..24d60fe5b 100644
--- a/bsp/axxiaarm/axxia-common.cfg
+++ b/bsp/axxiaarm/axxia-common.cfg
@@ -2,6 +2,7 @@ CONFIG_ARCH_AXXIA=y
 CONFIG_PHYS_ADDR_T_64BIT=y
 CONFIG_ARCH_DMA_ADDR_T_64BIT=y
 CONFIG_ARM_ARCH_TIMER=y
+CONFIG_PROFILING=y
 
 #
 # Bus support
diff --git a/bsp/axxiaarm64/axxiaarm64.cfg b/bsp/axxiaarm64/axxiaarm64.cfg
index 19bfb4bb4..0104ad766 100644
--- a/bsp/axxiaarm64/axxiaarm64.cfg
+++ b/bsp/axxiaarm64/axxiaarm64.cfg
@@ -31,6 +31,7 @@ CONFIG_CMA=y
 #
 CONFIG_AXXIA_OEM=y
 CONFIG_AXXIA_PEI=y
+CONFIG_ARM_CCN_PMU=y
 
 #
 # Controllers with non-SFF native interface
@@ -79,3 +80,8 @@ CONFIG_RTC_DRV_EFI=y
 # PHY Subsystem
 #
 CONFIG_GENERIC_PHY=y
+
+#
+# Watchdog
+#
+CONFIG_ARM_SP804_WATCHDOG_AXXIA=y
-- 
2.25.1


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

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 6/6] edac: remove dependency MACH_AXXIA for EDAC_AXXIA_L3_5500

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

I add "MACH_AXXIA" dependency for EDAC_AXXIA_L3_5500 to fix
allyesconfig building error. But there is no MACH_AXXIA kernel
option and this will cause warning as below:

Config 'EDAC_AXXIA_L2_CPU_5500' has the following Direct dependencies 
(EDAC_AXXIA_L2_CPU_5500=n):
MACH_AXXIA(undefined/n) && EDAC(=y)
Parent dependencies are:
MACH_AXXIA [MACH_AXXIA] EDAC [y]
[INFO]: config 'CONFIG_EDAC_AXXIA_L2_CPU_5500' was set, but it wasn't 
assignable, check (parent) dependencies

Delete MACH_AXXIA to fix it.

Signed-off-by: Quanyang Wang 
---
 drivers/edac/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
index ff830a62ed19..9212c16efe38 100644
--- a/drivers/edac/Kconfig
+++ b/drivers/edac/Kconfig
@@ -483,7 +483,6 @@ config EDAC_AXXIA_L3_6700
  can use polling mechanism or be interrupt driven.
 
 config EDAC_AXXIA_L2_CPU_5500
-   depends on MACH_AXXIA
tristate "AXXIA EDAC L2/CPU Controller for 5500"
help
  Support for L2 cache and A15 CPU error detection
-- 
2.25.1


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

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 5/6] axxia: use udelay instead of usleep in kexec/kdump routine

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

The kexec/kdump routine is mostly running at a atomic context,
calling usleep will trigger the calltrace as below:

WARNING: CPU: 0 PID: 529 at kernel/sched/core.c:4844 preempt_count_sub+0x74/0xf0
DEBUG_LOCKS_WARN_ON(val > preempt_count())
Modules linked in:
CPU: 0 PID: 529 Comm: kexec Tainted: GW 
5.10.57-rt47-yocto-preempt-rt+ #80
Hardware name: INTEL Axxia
[] (unwind_backtrace) from [] (show_stack+0x18/0x1c)
[] (show_stack) from [] (dump_stack+0x80/0x9c)
[] (dump_stack) from [] (__warn+0xcc/0xf8)
[] (__warn) from [] (warn_slowpath_fmt+0x80/0xc0)
[] (warn_slowpath_fmt) from [] (preempt_count_sub+0x74/0xf0)
[] (preempt_count_sub) from [] 
(axxia_platform_cpu_kill+0x88/0x104)
[] (axxia_platform_cpu_kill) from [] (__cpu_die+0x48/0x6c)
[] (__cpu_die) from [] (takedown_cpu+0xac/0xd4)
[] (takedown_cpu) from [] 
(cpuhp_invoke_callback+0x114/0x318)
[] (cpuhp_invoke_callback) from [] (_cpu_down+0x114/0x1e8)
[] (_cpu_down) from [] (smp_shutdown_nonboot_cpus+0x74/0xc0)
[] (smp_shutdown_nonboot_cpus) from [] 
(kernel_kexec+0x58/0x80)
[] (kernel_kexec) from [] (__do_sys_reboot+0x1c0/0x214)
[] (__do_sys_reboot) from [] (ret_fast_syscall+0x0/0x54)

Use udelay to eliminate this warning.

Signed-off-by: Quanyang Wang 
---
 arch/arm/mach-axxia/axxia.c  | 2 +-
 arch/arm/mach-axxia/axxia_power_management.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-axxia/axxia.c b/arch/arm/mach-axxia/axxia.c
index fdd0793df86f..12556247b5df 100644
--- a/arch/arm/mach-axxia/axxia.c
+++ b/arch/arm/mach-axxia/axxia.c
@@ -65,7 +65,7 @@ static void set_l3_pstate(u32 newstate)
status = readl(dickens + (hnf[i] << 16) + 0x18);
if (((status >> 2) & 3) == newstate)
break;
-   usleep_range(1, 2);
+   udelay(2);
}
WARN_ON(retry == 0);
}
diff --git a/arch/arm/mach-axxia/axxia_power_management.c 
b/arch/arm/mach-axxia/axxia_power_management.c
index 5d85e9b046de..a05213735831 100644
--- a/arch/arm/mach-axxia/axxia_power_management.c
+++ b/arch/arm/mach-axxia/axxia_power_management.c
@@ -673,7 +673,7 @@ static int pm_cpu_physical_isolation_and_power_down(int cpu)
/* Initiate power down of the CPU logic */
pm_clear_bits_syscon_register(NSP_PWRUPCPUSTG2, mask);
 
-   usleep_range(16, 17);
+   udelay(17);
 
/* Continue power down of the CPU logic */
pm_clear_bits_syscon_register(NSP_PWRUPCPUSTG1, mask);
-- 
2.25.1


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

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 4/6] axxia: add sync between cpu_die and cpu_kill

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

Normally, a CPU should run cpu_die first and then the CPUs stand by it
are in charge of killing it by calling cpu_kill. If a CPU doesn't call
cpu_die before other CPUs call cpu_kill, the system will hang. So add
synchronization implement between cpu_die and cpu_kill.

Signed-off-by: Quanyang Wang 
---
 arch/arm/mach-axxia/hotplug.c | 26 ++
 1 file changed, 26 insertions(+)

diff --git a/arch/arm/mach-axxia/hotplug.c b/arch/arm/mach-axxia/hotplug.c
index 5e4d88c83fb7..f1bbc6aeb233 100644
--- a/arch/arm/mach-axxia/hotplug.c
+++ b/arch/arm/mach-axxia/hotplug.c
@@ -14,6 +14,9 @@
 #include "axxia_power_management.h"
 #include "axxia.h"
 
+static int axxia_cpu_die_flag;
+static DEFINE_SPINLOCK(axxia_cpu_die_lock);
+
 static inline void pm_cpu_logical_shutdown(u32 cpu)
 {
u32 val;
@@ -189,9 +192,28 @@ static void __ref platform_do_lowpower(unsigned int cpu, 
int *spurious)
 int axxia_platform_cpu_kill(unsigned int cpu)
 {
 #ifdef CONFIG_HOTPLUG_CPU_COMPLETE_POWER_DOWN
+   int ret, retry;
+
+   retry = 50;
+   while (1) {
+   spin_lock(_cpu_die_lock);
+   ret = axxia_cpu_die_flag & (1<
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10279): 
https://lists.yoctoproject.org/g/linux-yocto/message/10279
Mute This Topic: https://lists.yoctoproject.org/mt/84920418/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 3/6] arm: mach-axxia: kexec_reinit to set L3 CACHE shutdown

2021-08-16 Thread quanyang.wang 
From: Xulin Sun 

Shut down to flush L3 cache for KEXEC to avoid the hung issue for
capture kernel booting, since for ARM capture kernel just one CPU
allowed to boot, and no L3 cache coherency issue existed for SMP
situation, so just shut down the flush to L3 CACHE.

The function calling relationship like below:
kernel_kexec
machine_kexec
kexec_reinit
flush_l3

Signed-off-by: Xulin Sun 
[Quanyang: add a new function shutdown_l3 to shutdown the l3 cache
in the kexec routine.]
Signed-off-by: Quanyang Wang 
---
 arch/arm/mach-axxia/axxia.c | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-axxia/axxia.c b/arch/arm/mach-axxia/axxia.c
index 263dd79af7bf..fdd0793df86f 100644
--- a/arch/arm/mach-axxia/axxia.c
+++ b/arch/arm/mach-axxia/axxia.c
@@ -71,6 +71,13 @@ static void set_l3_pstate(u32 newstate)
}
 }
 
+void
+shutdown_l3(void)
+{
+   /* Shutdown to flush */
+   set_l3_pstate(0);
+}
+
 void
 flush_l3(void)
 {
@@ -180,7 +187,7 @@ void __init axxia_dt_init(void)
if (!of_find_compatible_node(NULL, NULL, "axxia,axm5500-sim")) {
dickens = ioremap(0x20, SZ_16M);
 #ifdef CONFIG_KEXEC
-   kexec_reinit = flush_l3;
+   kexec_reinit = shutdown_l3;
 #endif
flush_l3();
}
-- 
2.25.1


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

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 2/6] arch/arm/mach-axxia: use mpidr_to_hwcpu to retrieve real hardware cpuid

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

In function arm_dt_init_cpu_maps, it will use hwid whose value is "reg" property
in cpu node to compare with mpidr whose value read from MPIDR register. When 
boot
in normal condition, hwid is equal to MPIDR value which is "0" by chance. But in
kdump, the boot cpu will be any of 16 cpus and arm_dt_init_cpu_maps will not be 
able
to get correct hardware cpuid and this will result deviant irq affinity setting.

So at first, change "reg" property to mpidr value, and then use mpidr_to_hwcpu 
to transit
it to get real cpuid. Or else, in kdump, most irq will not be triggered.

Signed-off-by: Quanyang Wang 
---
 arch/arm/boot/dts/axm5516-cpus.dtsi  | 24 +++---
 arch/arm/mach-axxia/axxia-gic.c  | 34 ++--
 arch/arm/mach-axxia/axxia_power_management.c |  4 +--
 arch/arm/mach-axxia/axxia_power_management.h |  1 +
 arch/arm/mach-axxia/hotplug.c|  2 +-
 arch/arm/mach-axxia/platsmp.c| 13 ++--
 6 files changed, 43 insertions(+), 35 deletions(-)

diff --git a/arch/arm/boot/dts/axm5516-cpus.dtsi 
b/arch/arm/boot/dts/axm5516-cpus.dtsi
index d4d2966b58b9..33223bee5814 100644
--- a/arch/arm/boot/dts/axm5516-cpus.dtsi
+++ b/arch/arm/boot/dts/axm5516-cpus.dtsi
@@ -41,7 +41,7 @@ cpu@3 {
cpu@4 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x04>;
+   reg = <0x100>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -49,7 +49,7 @@ cpu@4 {
cpu@5 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x05>;
+   reg = <0x101>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -57,7 +57,7 @@ cpu@5 {
cpu@6 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x06>;
+   reg = <0x102>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -65,7 +65,7 @@ cpu@6 {
cpu@7 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x07>;
+   reg = <0x103>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -73,7 +73,7 @@ cpu@7 {
cpu@8 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x08>;
+   reg = <0x200>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -81,7 +81,7 @@ cpu@8 {
cpu@9 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x09>;
+   reg = <0x201>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -89,7 +89,7 @@ cpu@9 {
cpu@10 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x0a>;
+   reg = <0x202>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -97,7 +97,7 @@ cpu@10 {
cpu@11 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x0b>;
+   reg = <0x203>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -105,7 +105,7 @@ cpu@11 {
cpu@12 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x0c>;
+   reg = <0x300>;
cpu-release-addr = <0>; // Fixed by the boot loader
clock-frequency = <0>;  // Placeholder
};
@@ -113,7 +113,7 @@ cpu@12 {
cpu@13 {
device_type = "cpu";
compatible = "arm,cortex-a15";
-   reg = <0x0d>;
+   reg = <0x301>;

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 0/6]

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

Hi Bruce,

Would you please help merge these patches to the 2 branches?

v5.10/standard/preempt-rt/sdkv5.10/axxia
v5.10/standard/sdkv5.10/axxia

Thanks,
Quanyang

Quanyang Wang (5):
  kexec: adjust dtb_mem address to adapt to axm55xx's weird entry
  arch/arm/mach-axxia: use mpidr_to_hwcpu to retrieve real hardware
cpuid
  axxia: add sync between cpu_die and cpu_kill
  axxia: use udelay instead of usleep in kexec/kdump routine
  edac: remove dependency MACH_AXXIA for EDAC_AXXIA_L3_5500

Xulin Sun (1):
  arm: mach-axxia: kexec_reinit to set L3 CACHE shutdown

 arch/arm/boot/dts/axm5516-cpus.dtsi  | 24 +++---
 arch/arm/kernel/machine_kexec.c  | 14 +++-
 arch/arm/mach-axxia/axxia-gic.c  | 34 ++--
 arch/arm/mach-axxia/axxia.c  | 11 +--
 arch/arm/mach-axxia/axxia_power_management.c |  6 ++--
 arch/arm/mach-axxia/axxia_power_management.h |  1 +
 arch/arm/mach-axxia/hotplug.c| 28 +++-
 arch/arm/mach-axxia/platsmp.c| 13 ++--
 drivers/edac/Kconfig |  1 -
 9 files changed, 92 insertions(+), 40 deletions(-)

-- 
2.25.1


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

[linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 1/6] kexec: adjust dtb_mem address to adapt to axm55xx's weird entry

2021-08-16 Thread quanyang.wang 
From: Quanyang Wang 

When kexec load secondary kernel, it will calculate dtb_mem according to
the formula as below:
dtb_mem = kernel_entry + image_size * 5
But axm55xx's entry is not the default value 0x8000 but 0x408000, this will
result that when zImage as the secondary kernel decompresses,
kernel_entry + kernel_size + zImage_size > dtb_mem, and data of dtb file in
dtb_mem will be overlapped by zImage. So add 4M to dtb_mem to avoid this.

Signed-off-by: Quanyang Wang 
---
 arch/arm/kernel/machine_kexec.c | 14 +-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/arch/arm/kernel/machine_kexec.c b/arch/arm/kernel/machine_kexec.c
index 2b09dad7935e..e1db8806521c 100644
--- a/arch/arm/kernel/machine_kexec.c
+++ b/arch/arm/kernel/machine_kexec.c
@@ -62,9 +62,21 @@ int machine_kexec_prepare(struct kimage *image)
err = get_user(header, (__be32*)current_segment->buf);
if (err)
return err;
-
+#ifdef CONFIG_ARCH_AXXIA
+   if (header == cpu_to_be32(OF_DT_HEADER)) {
+   /*
+* In axm55xx, kernel entry is not 0x8000 but 0x408000, 
this will
+* result that when secondary kernel boot, dtb will 
corrupt because
+* entry + kernel_size + zImage_size > dtb_mem, so add 
4M to dtb_mem
+* to avoid this.
+*/
+   current_segment->mem += 0xF0;
+   image->arch.kernel_r2 = current_segment->mem;
+   }
+#else
if (header == cpu_to_be32(OF_DT_HEADER))
image->arch.kernel_r2 = current_segment->mem;
+#endif
}
return 0;
 }
-- 
2.25.1


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

Re: [yocto] Failed to boot kernel 5 after upgrading to Hardknott

2021-08-16 Thread Khem Raj 



On 8/15/21 10:36 PM, Zoran wrote:

You are using systemd with the wrong defconfig setup, my best guess.

cgroup option in the config must be set to Y while using systemd:
CONFIG_CGROUP=Y .

Zee
___

On Mon, Aug 16, 2021 at 6:24 AM JH  wrote:


Hi,

I upgrade Zeus to Hardknott, the kernel version is 5.10.4
(oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 10.2.0, GNU ld (GNU
Binutils) 2.36.1.20210209), it was failed to boot the kernel :

---

[9.418302] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No
such file or directory
[9.431805] systemd[1]: Failed to mount cgroup at
/sys/fs/cgroup/systemd: No such file or directory
[!!] Failed to mount API filesystems.
[9.463151] systemd[1]: Freezing execution.

What could I be missing?


Look at kernel kconfig options that should be enabled here
https://cgit.freedesktop.org/systemd/systemd/tree/README#n38




Thank you.

Kind regards,

- jh








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