[linux-yocto][v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc][PATCH] arm64: zynqmp: add "xlnx,nr-outputs" property for clk_wiz_0 node

[quanyang.wang via lists.yoctoproject.org]

From: Quanyang Wang 

In clk-xlnx-clock-wizard.c, the function clk_wzrd_probe will check if
there is "xlnx,nr-outputs" property, if not, the probe will return
error. Add "xlnx,nr-outputs" property for clk_wiz_0 node to avoid probe
failure.

Signed-off-by: Quanyang Wang 
---
Hi Bruce,
Would you please help merge this patch to the branches:
v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
v6.1/standard/sdkv6.1/xlnx-soc
Thanks,
Quanyang
---
 arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0-canfd.dts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0-canfd.dts 
b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0-canfd.dts
index 73ba3abd7aa89..d5b54d4a98d12 100644
--- a/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0-canfd.dts
+++ b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0-canfd.dts
@@ -69,6 +69,7 @@ clk_wiz_0: clk_wiz@8001 {
compatible = "xlnx,clk-wiz-6.0", "xlnx,clocking-wizard";
reg = <0x0 0x8001 0x0 0x1>;
speed-grade = <2>;
+   xlnx,nr-outputs = <7>;
};
psu_ctrl_ipi: PERIPHERAL@ff38 {
compatible = "xlnx,PERIPHERAL-1.0";
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12744): 
https://lists.yoctoproject.org/g/linux-yocto/message/12744
Mute This Topic: https://lists.yoctoproject.org/mt/99499864/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][yocto-kernel-cache yocto-6.1][PATCH 4/4] nxp-imx8: Enable USB_CHIPIDEA related config

[Bruce Ashfield]

I haven't done any merging yet.

You sent this on a Friday, and it is now only the end of day Monday
for me, so a ping is a bit premature.

Bruce

On Mon, Jun 12, 2023 at 10:22 PM Wang, Xiaolei
 wrote:
>
> Hi bruce
>
> please help merge this patch
>
> thanks
> xiaolei
> 
> From: linux-yocto@lists.yoctoproject.org  
> on behalf of Xiaolei Wang via lists.yoctoproject.org 
> 
> Sent: Friday, June 9, 2023 5:42 PM
> To: bruce.ashfi...@gmail.com 
> Cc: linux-yocto@lists.yoctoproject.org 
> Subject: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 4/4] nxp-imx8: 
> Enable USB_CHIPIDEA related config
>
> Enable USB_CHIPIDEA related config for nxp-imx8.
>
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx8/nxp-imx8.cfg | 7 +++
>  1 file changed, 7 insertions(+)
>
> diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
> index 1581cdc6..b116ae2d 100644
> --- a/bsp/nxp-imx8/nxp-imx8.cfg
> +++ b/bsp/nxp-imx8/nxp-imx8.cfg
> @@ -416,6 +416,13 @@ CONFIG_USB_HCD_TEST_MODE=y
>  CONFIG_USB_ACM=m
>  CONFIG_USB_STORAGE=y
>  CONFIG_USB_UAS=y
> +CONFIG_USB_CHIPIDEA=y
> +CONFIG_USB_CHIPIDEA_UDC=y
> +CONFIG_USB_CHIPIDEA_HOST=y
> +CONFIG_USB_CONFIGFS=m
> +CONFIG_USB_G_NCM=m
> +CONFIG_USB_G_ACM_MS=m
> +CONFIG_USB_MASS_STORAGE=m
>
>  #
>  # Typec driver
> --
> 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

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

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

[Jing Hui Tham]

Hi All,
 
QA for yocto-4.3_M1.rc1 is completed. This is the full report for this release: 
 
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
 
=== Summary 
No high milestone defects.
 
No new issue found. 
 
Thanks,
Jing Hui


> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Thursday, June 8, 2023 11:39 AM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.3_M1.rc1)
> 
> 
> A build flagged for QA (yocto-4.3_M1.rc1) was completed on the
> autobuilder and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.3_M1.rc1
> 
> 
> Build hash information:
> 
> bitbake: 6abdc81dec06a362bfbcc06d69b90b96bd9bef01
> meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0
> meta-arm: c1a7dd5eda419109b179af6cbf93cb0dac2f7ae3
> meta-aws: 03dbd44a850b13c581f4335254f915ce50bc13c3
> meta-intel: eb696e99ff8c5be4f9b181da9f134499d96760e4
> meta-mingw: 6badedaa3e4df5b00b5aa992c5c174e315b09972
> meta-openembedded: 1955d0f140a9610346021d42fa45cb186eb6f042
> meta-virtualization: d9dc99282fa4a7dfce861f64e792b1a8307a4a8c
> oecore: f7ed7ae854e49276750d1895593e0a2033714235
> poky: cc97d775cb402df0d4122bf54eab1a5198c98471
> 
> 
> 
> 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 (#60268): https://lists.yoctoproject.org/g/yocto/message/60268
Mute This Topic: https://lists.yoctoproject.org/mt/99498219/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 4/4] nxp-imx8: Enable USB_CHIPIDEA related config

[Xiaolei Wang via lists.yoctoproject.org]

Hi bruce

please help merge this patch

thanks
xiaolei

From: linux-yocto@lists.yoctoproject.org  
on behalf of Xiaolei Wang via lists.yoctoproject.org 

Sent: Friday, June 9, 2023 5:42 PM
To: bruce.ashfi...@gmail.com 
Cc: linux-yocto@lists.yoctoproject.org 
Subject: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 4/4] nxp-imx8: 
Enable USB_CHIPIDEA related config

Enable USB_CHIPIDEA related config for nxp-imx8.

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

diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg
index 1581cdc6..b116ae2d 100644
--- a/bsp/nxp-imx8/nxp-imx8.cfg
+++ b/bsp/nxp-imx8/nxp-imx8.cfg
@@ -416,6 +416,13 @@ CONFIG_USB_HCD_TEST_MODE=y
 CONFIG_USB_ACM=m
 CONFIG_USB_STORAGE=y
 CONFIG_USB_UAS=y
+CONFIG_USB_CHIPIDEA=y
+CONFIG_USB_CHIPIDEA_UDC=y
+CONFIG_USB_CHIPIDEA_HOST=y
+CONFIG_USB_CONFIGFS=m
+CONFIG_USB_G_NCM=m
+CONFIG_USB_G_ACM_MS=m
+CONFIG_USB_MASS_STORAGE=m

 #
 # Typec driver
--
2.25.1


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

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

[Stephen Jolley]

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

14901  

lttng: collect TAP output

randy.macl...@windriver.com

alexis.loth...@bootlin.com

4.3 M1

4.3 M2


Medium+

14125  

busybox wget ssl is exposed to MitM attack due to CVE-2018-1000500

randy.macl...@windriver.com

randy.macl...@windriver.com

4.3 M1

4.3 M2


14903  

SDK relocation can't be done for alternative SDK packaging

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.3

4.3 M2


15130  

bitbake should warn if a function is defined only for specific cases

randy.macl...@windriver.com

richard.pur...@linuxfoundation.org

4.3

4.3 M3


15134  

systemd-networkd will remove unmanaged wlan configs on carrier loss

randy.macl...@windriver.com

c...@myfastmail.com

0.0.0

4.3 M2


15138  

AB-INT: qemux86/x86-64 hangs intermittently

randy.macl...@windriver.com

unassig...@yoctoproject.org

0.0.0

4.3 M2

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

[yocto] Enhancements/Bugs closed WW23!

[Stephen Jolley]

All,

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


Who

Count


richard.pur...@linuxfoundation.org

4


ross.bur...@arm.com

2


randy.macl...@windriver.com

2


michael.opdenac...@bootlin.com

1


Grand Total

9

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 (#60266): https://lists.yoctoproject.org/g/yocto/message/60266
Mute This Topic: https://lists.yoctoproject.org/mt/99496135/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 4.3

[Stephen Jolley]

All,

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




Who

Count


ross.bur...@arm.com

32


michael.opdenac...@bootlin.com

32


richard.pur...@linuxfoundation.org

25


david.re...@windriver.com

25


bruce.ashfi...@gmail.com

25


randy.macl...@windriver.com

24


jpewhac...@gmail.com

11


pa...@zhukoff.net

7


sakib.sa...@windriver.com

6


sundeep.kokko...@windriver.com

5


pi...@pidge.org

4


yash.shi...@windriver.com

3


tim.orl...@konsulko.com

3


p.lob...@welotec.com

2


jon.ma...@arm.com

2


alexis.loth...@bootlin.com

2


yoann.con...@smile.fr

1


tvgamb...@gmail.com

1


thr...@amazon.de

1


thomas.per...@bootlin.com

1


mathew.pro...@gmail.com

1


martin.ja...@gmail.com

1


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

1


mark.asselst...@windriver.com

1


louis.ran...@syslinbit.com

1


johannes.schri...@blueye.no

1


jens.ge...@desy.de

1


geissona...@yahoo.com

1


frederic.martins...@gmail.com

1


fathi.bou...@linaro.org

1


alexandre.bell...@bootlin.com

1


Grand Total

223

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 (#60265): https://lists.yoctoproject.org/g/yocto/message/60265
Mute This Topic: https://lists.yoctoproject.org/mt/99495941/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

[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 439
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,  "4.3", "4.4", "4.99" and "Future", the more pressing/urgent
issues being in "4.3" and then "4.4".

 

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

[yocto] [patchtest-oe][PATCH] test_mbox_signed_off_by: fix test

[Trevor Gamblin]

This fixes a consistent issue with false failures being reported when
testing for authors' signed-off-bys in mboxes. Instead of manually
compiling a regex pattern, use pyparsing's AtLineStart to check for the
signature's presence at the beginning of the line.

Signed-off-by: Trevor Gamblin 
---
 tests/pyparsing/parse_signed_off_by.py | 4 ++--
 tests/test_mbox_signed_off_by.py   | 5 ++---
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/tests/pyparsing/parse_signed_off_by.py 
b/tests/pyparsing/parse_signed_off_by.py
index fc39a6c..9338c49 100644
--- a/tests/pyparsing/parse_signed_off_by.py
+++ b/tests/pyparsing/parse_signed_off_by.py
@@ -30,5 +30,5 @@ email = 
pyparsing.Regex(r"(?P[A-Za-z0-9._%+-]+)@(?P[A-Za-z0-9.-]
 
 email_enclosed = common.lessthan + email + common.greaterthan
 
-signed_off_by_mark = pyparsing.Literal("Signed-off-by")
-signed_off_by = common.start + signed_off_by_mark + common.colon + name + 
email_enclosed + common.end
+signed_off_by_mark = pyparsing.Literal("Signed-off-by:")
+signed_off_by = pyparsing.AtLineStart(signed_off_by_mark + name + 
email_enclosed)
diff --git a/tests/test_mbox_signed_off_by.py b/tests/test_mbox_signed_off_by.py
index e50bb8e..eae2816 100644
--- a/tests/test_mbox_signed_off_by.py
+++ b/tests/test_mbox_signed_off_by.py
@@ -28,15 +28,14 @@ class SignedOffBy(base.Base):
 @classmethod
 def setUpClassLocal(cls):
 # match self.mark with no '+' preceding it
-cls.mark = str(parse_signed_off_by.signed_off_by_mark).strip('"')
-cls.prog = re.compile("(?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60263): https://lists.yoctoproject.org/g/yocto/message/60263
Mute This Topic: https://lists.yoctoproject.org/mt/99488426/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [patchtest][PATCH] requirements.txt: Add pylint, pyparsing, unidiff

[Trevor Gamblin]

Add some dependencies that patchtest now relies on to requirements.txt.

Signed-off-by: Trevor Gamblin 
---
 requirements.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/requirements.txt b/requirements.txt
index 7f7afbf..47f2157 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1 +1,4 @@
 jinja2
+pylint
+pyparsing
+unidiff
-- 
2.40.1


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

Re: [yocto] Approach for generating two WIC files at once

[Konstantin Kletschke]

Meanwhile I tested my proposed approach and it works well...

On Mon, Jun 12, 2023 at 11:35:59AM +0200, Alexander Kanavin wrote:
> sdcard-base.inc is better, because sdcard-base.bb is a recipe in
> itself, but you don't want to build that (or others to get confused
> about its purpose).

... but this is a nice hint! Thank you very much!

I was bothered colleagues trying to build the base
"image" indeed :-)



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

Re: [yocto] Snort 3 rules - Antivirus

[Rostanin Gleb SBR DIRCS]

Ok thank you for your fast answer, I was wondering why this is not the case for 
the most Snort 2 rules.

I computed the same MD5 hash sum as on the website:

·“9bf94aa54566829c35a9aa64e89f3345” for snortrules-snapshot-31470.tar.gz



Kind regards



G. Rostanin

Von: Jayesh Patel 
Gesendet: Montag, 12. Juni 2023 15:41
An: Rostanin Gleb SBR DIRCS ; snort-s...@lists.snort.org
Betreff: Re: Snort 3 rules - Antivirus

I believe this is normal, since AV detections based on signatures can trigger 
alert when they see pattern in Snort Rules. I had this alert earlier, it would 
help to create a folder and exclude that from defender scans. Also, verify the 
checksum of the file downloaded from Snort, just to be on safe side.

Thanks,
Jayesh

Get Outlook for Android

From: Snort-sigs 
mailto:snort-sigs-boun...@lists.snort.org>> 
on behalf of Rostanin Gleb SBR DIRCS via Snort-sigs 
mailto:snort-s...@lists.snort.org>>
Sent: Monday, June 12, 2023 6:30:16 AM
To: snort-s...@lists.snort.org 
mailto:snort-s...@lists.snort.org>>
Subject: [Snort-sigs] Snort 3 rules - Antivirus


Dear Snort community,



I recently registered to be able to download the Snort 3 rules. Unfortunately, 
when downloading, Windows defender started complaining that a Virus was 
detected. Is this normal behavior or am I currently being attacked ?



Kind regards



Gerry

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

Re: [yocto] Kirkstone Rust 1.68 mixin layer

[Scott Murray]

On Fri, 9 Jun 2023, Jose Quaresma wrote:

> Hi Scott,
>
> Can this branch be renamed to just rust?
>
> -kirkstone/rust-1.68
> +kirkstone/rust
>
> rust is now on 1.70 in core and it would be useful in my opinion to
> backport what is in the master and not just the 1.68
> https://git.yoctoproject.org/poky/commit/?id=5035a8588bb27e029661a500215dd4e83f023ac6

No.  As I say in the README in the branch:

- The intent is to just track any further 1.68.x upgrades that occur in
  the mickledore branch of oe-core.  Supporting newer versions of Rust
  or trying to support more than one version of Rust should use a
  different mixin layer.

I see two paths to do what you ask, both of which IMO have issues wrt
my usecase of a hopefully stable mixin layer to use on top of kirkstone:

1. Keep sticking the latest Rust from master into a mixin branch in
   meta-lts-mixins.  This likely will make some folks happy, but my
   issue with doing that in the branch I want to use against kirkstone is
   that while chances are slim that the Rust team go back and do a 1.68.x
   point release, I know 1.68.x works with the combination of kirkstone
   and the target software in Automotive Grade Linx (AGL), and just
   bumping the mixin layer to latest Rust as it comes into master would
   complicate later trying to pick up any fixes for 1.68.x from
   mickledore if they do happen.  I may potentially need to worry about a
   version bump when mickledore goes out of maintenance, but at the
   moment my plan is to stick with 1.68.x until we upgrade AGL to Yocto
   Project 4.4 next spring.  If you want to take the
   kirkstone/rust-1.68.x mixin as the starting point of a plain "rust"
   mixin layer that you will maintain against master's Rust version,
   please go ahead.

2. Supporting more than one version in a mixin layer.  Since the rust
   .inc files are not versioned, this will require some (hopefully minor)
   manual tinkering.  The first drawback is that cherry-picks of updates
   afterwards will then all need to be done in a more manual fashion.
   The second drawback is that since oe-core only carries a single
   version of Rust, extra testing against the two or more versions
   present will need to be done to make they sure they all work, and to
   be certain of compatibility, this likely will take adding the multiple
   versions of cargo, rigging up CARGO_VERSION, etc., and also testing
   that.  I have no desire to expend the effort required for that, and if
   I were to need a newer version of Rust for AGL, I would probably once
   again just submit a mixin with a single version.  It seemed to be the
   consensus on the YP technical calls that this was a reasonable
   approach.

Best regards,

Scott

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

Re: [yocto] Snort 2.9 into Snort 3 recipe

[Trevor Gamblin]

On 2023-06-12 07:33, Rostanin Gleb SBR DIRCS wrote:


Hello,

I did the following steps:

  * Rename recipe file name to snort_3.1.62.0.bb
  * Changed line 9 “SRC_URI = “…/snort/${BP}.tar.gz”” to
https://www.snort.org/downloads/snortplus/snort3-3.1.62.0.tar.gz
  * Added correct snort3 sha256sum in line 17
  * Added correct MD5 checksum of the snort tar ball in line 5

The following error occurs in “0001-libpcap … headers.patch” file:

/ERROR: Applying patch '0001-libpcap-search-sysroot-for-headers.patch' 
on target directory 
'/home/user/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/cortexa53-crypto-fsl-linux/snort/3.1.62.0-r0/snort-3.1.62.0'/


/CmdError('quilt --quiltrc 
/home/user/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/cortexa53-crypto-fsl-linux/snort/3.1.62.0-r0/recipe-sysroot-native/etc/quiltrc 
push', 0, "stdout: Applying patch 
0001-libpcap-search-sysroot-for-headers.patch/


/can't find file to patch at input line 21/

/Perhaps you used the wrong -p or --strip option?/

//

As the patches are not written for snort 3 I tried again but deleted 
the patches from the “.bb” file. Now the following error occurs:


/DEBUG: Executing python function autotools_aclocals
DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 
'common-linux', 'common-glibc', 'aarch64-linux', 'common']

DEBUG: Python function autotools_aclocals finished
DEBUG: Executing shell function do_compile
NOTE: make -j 6
make: *** No targets specified and no makefile found. Stop.
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.///

Now I am not sure where and at which point the make file should be 
created and why it is missing. Could you give some tips on how to 
transfer this recipe to an snort 3 recipe?


It looks like snort 2.x uses Autotools for setup, while 3.x uses CMake 
instead. You would have to adjust the recipe so that it uses the latter 
and passes the correct build flags for the "default" snort configuration 
(I'm not sure what those would be). You may also need to spend some time 
making sure that the changes provided by those deleted patches aren't 
still required somewhere in the new source files.


If you do 'grep -r "inherit cmake"' on openembedded-core/meta, you can 
find many examples of other recipes that use CMake for building that you 
could use as references.



Thank you for reading

G. Rostanin

*Von:*Trevor Gamblin 
*Gesendet:* Freitag, 9. Juni 2023 18:25
*An:* Rostanin Gleb SBR DIRCS ; 
yocto@lists.yoctoproject.org

*Betreff:* Re: [yocto] Snort 2.9 into Snort 3 recipe

On 2023-06-09 10:05, Rostanin Gleb SBR DIRCS wrote:

Hello OpenEmbedded Community,

currently I am working on implementing the Snort IDS on an
embedded system with the Yocto Linux OS. As OpenEmbedded already
provides a recipe for Snort 2.9 it is easy to install snort into
the OS. Unfortunately, it is not easy to change the recipe so that
the new Snort 3 version is installed. I tried to change the git
repo link and the checksum (as a simple solution try), but
unfortunately, I ran into multiple errors, and I am not sure at
which point I need to make further changes. As I could understand,
also a few changes to the source code of Snort must be done to
make it work on the Yocto OS.

Was someone already successful in implementing a recipe to install
the newer Snort 3 version directly on Yocto? What do I have to
change in the Snort 2.9 recipe to install the Snort 3 version?

The errors you're seeing when you try to build Snort 3 should provide 
a clue. If you post those, someone may be able to provide further 
suggestions.


Trevor

Of course, another solution could be cross compiling Snort for the
embedded system, but maybe there is already a solution for this.

I happy about any help or comment on this topic!

Kind regards

G. Rostanin






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

[linux-yocto] [PATCH] Revert 'spi: spi-octeontx2: fix erase sector error by limit spi buswidth'

[Ruiqiang Hao via lists.yoctoproject.org]

From: Ruiqiang Hao 

Revert commit e223229ee63803fc233885f686a7890453be9587

Commit e223229ee638(spi: spi-octeontx2: fix erase sector error by limit
spi buswidth) try to fix erase sector error. After testing, spi-nor can
work normally without this commit now. It is not needed and causes follow
problem: 'spi spi0.0: setup: ignoring unsupported mode bits a00'

Signed-off-by: Ruiqiang Hao 
---
 drivers/spi/spi-octeontx2.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/spi/spi-octeontx2.c b/drivers/spi/spi-octeontx2.c
index 4edda6c1f74b..9ac5a6f37510 100644
--- a/drivers/spi/spi-octeontx2.c
+++ b/drivers/spi/spi-octeontx2.c
@@ -390,7 +390,9 @@ static int octeontx2_spi_probe(struct pci_dev *pdev,
 
master->num_chipselect = 4;
master->mode_bits = SPI_CPHA | SPI_CPOL | SPI_CS_HIGH |
-   SPI_LSB_FIRST | SPI_3WIRE;
+   SPI_LSB_FIRST | SPI_3WIRE |
+   SPI_TX_DUAL | SPI_RX_DUAL |
+   SPI_TX_QUAD | SPI_RX_QUAD;
master->transfer_one_message = octeontx2_spi_transfer_one_message;
master->bits_per_word_mask = SPI_BPW_MASK(8);
master->max_speed_hz = OCTEONTX2_SPI_MAX_CLOCK_HZ;
-- 
2.35.5


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

[linux-yocto][linux-yocto v5.15] kernel code for marvell cn96xx

[Ruiqiang Hao via lists.yoctoproject.org]

Hi Bruce,

Please help to merge this patch into our linux-yocto repo.

repo:
linux-yocto
branch:
v5.15/standard/cn-sdkv5.4/octeon
v5.15/standard/preempt-rt/cn-sdkv5.4/octeon

Thanks,
Ruiqiang

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

Re: [yocto] Snort 2.9 into Snort 3 recipe

[Rostanin Gleb SBR DIRCS]

Hello,

I did the following steps:

  *   Rename recipe file name to snort_3.1.62.0.bb
  *   Changed line 9 “SRC_URI = “…/snort/${BP}.tar.gz”” to 
https://www.snort.org/downloads/snortplus/snort3-3.1.62.0.tar.gz
  *   Added correct snort3 sha256sum in line 17
  *   Added correct MD5 checksum of the snort tar ball in line 5
The following error occurs in “0001-libpcap … headers.patch” file:
ERROR: Applying patch '0001-libpcap-search-sysroot-for-headers.patch' on target 
directory 
'/home/user/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/cortexa53-crypto-fsl-linux/snort/3.1.62.0-r0/snort-3.1.62.0'
CmdError('quilt --quiltrc 
/home/user/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/cortexa53-crypto-fsl-linux/snort/3.1.62.0-r0/recipe-sysroot-native/etc/quiltrc
 push', 0, "stdout: Applying patch 0001-libpcap-search-sysroot-for-headers.patch
can't find file to patch at input line 21
Perhaps you used the wrong -p or --strip option?

As the patches are not written for snort 3 I tried again but deleted the 
patches from the “.bb” file. Now the following error occurs:
DEBUG: Executing python function autotools_aclocals
DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 
'common-linux', 'common-glibc', 'aarch64-linux', 'common']
DEBUG: Python function autotools_aclocals finished
DEBUG: Executing shell function do_compile
NOTE: make -j 6
make: *** No targets specified and no makefile found.  Stop.
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.

Now I am not sure where and at which point the make file should be created and 
why it is missing. Could you give some tips on how to transfer this recipe to 
an snort 3 recipe?

Thank you for reading

G. Rostanin

Von: Trevor Gamblin 
Gesendet: Freitag, 9. Juni 2023 18:25
An: Rostanin Gleb SBR DIRCS ; yocto@lists.yoctoproject.org
Betreff: Re: [yocto] Snort 2.9 into Snort 3 recipe



On 2023-06-09 10:05, Rostanin Gleb SBR DIRCS wrote:
Hello OpenEmbedded Community,

currently I am working on implementing the Snort IDS on an embedded system with 
the Yocto Linux OS. As OpenEmbedded already provides a recipe for Snort 2.9 it 
is easy to install snort into the OS. Unfortunately, it is not easy to change 
the recipe so that the new Snort 3 version is installed. I tried to change the 
git repo link and the checksum (as a simple solution try), but unfortunately, I 
ran into multiple errors, and I am not sure at which point I need to make 
further changes. As I could understand, also a few changes to the source code 
of Snort must be done to make it work on the Yocto OS.
Was someone already successful in implementing a recipe to install the newer 
Snort 3 version directly on Yocto? What do I have to change in the Snort 2.9 
recipe to install the Snort 3 version?

The errors you're seeing when you try to build Snort 3 should provide a clue. 
If you post those, someone may be able to provide further suggestions.

Trevor
Of course, another solution could be cross compiling Snort for the embedded 
system, but maybe there is already a solution for this.
I happy about any help or comment on this topic!

Kind regards

G. Rostanin









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

Re: [yocto] Submit a new layer meta-loongarch to the layer index

[张家岭]

Hi Ross:

    Thank you , I can see it now.

Cheers,
JiaLing Zhang

在 2023/6/12 18:40, Ross Burton 写道:

On 12 Jun 2023, at 10:36, 张家岭  wrote:
>
> Hi Ross:
>
> Thank you , I can edit this layer now , How can I show  this 
layer in http://layers.openembedded.org/layerindex/branch/master/layers/


It’s there now, at least I can see it.



Ross

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

[yocto] [meta-security][PATCH] scap-security-guide: update to tip

[Armin Kuster]

Make default

Signed-off-by: Armin Kuster 
---
 .../scap-security-guide_0.1.67.bb | 37 +--
 1 file changed, 34 insertions(+), 3 deletions(-)

diff --git 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_0.1.67.bb
 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_0.1.67.bb
index af1ddf7..53ee03e 100644
--- 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_0.1.67.bb
+++ 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_0.1.67.bb
@@ -1,8 +1,39 @@
+# Copyright (C) 2017 - 2023 Armin Kuster  
+# Released under the MIT license (see COPYING.MIT for the terms)
+
 SUMARRY = "SCAP content for various platforms, upstream version"
+HOME_URL = "https://www.open-scap.org/security-policies/scap-security-guide/;
+LIC_FILES_CHKSUM = "file://LICENSE;md5=9bfa86579213cb4c6adaffface6b2820"
+LICENSE = "BSD-3-Clause"
 
-SRCREV = "ee688320c4478ccb0d4dbefbfbd2f10df6261e17"
+SRCREV = "dad85502ce8da722a6afc391346c41cee61e90a9"
 SRC_URI = 
"git://github.com/ComplianceAsCode/content.git;branch=master;protocol=https"
 
-DEFAULT_PREFERENCE = "-1"
 
-require scap-security-guide.inc
+DEPENDS = "openscap-native python3-pyyaml-native python3-jinja2-native 
libxml2-native expat-native coreutils-native"
+
+S = "${WORKDIR}/git"
+
+inherit cmake pkgconfig python3native python3targetconfig
+
+STAGING_OSCAP_BUILDDIR = "${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
+export OSCAP_CPE_PATH="${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe"
+export 
OSCAP_SCHEMA_PATH="${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas"
+export 
OSCAP_XSLT_PATH="${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl"
+
+OECMAKE_GENERATOR = "Unix Makefiles"
+
+EXTRA_OECMAKE += "-DENABLE_PYTHON_COVERAGE=OFF -DSSG_PRODUCT_DEFAULT=OFF 
-DSSG_PRODUCT_EXAMPLE=ON"
+
+B = "${S}/build"
+
+do_configure[depends] += "openscap-native:do_install"
+
+do_configure:prepend () {
+sed -i -e 's:NAMES\ sed:NAMES\ ${HOSTTOOLS_DIR}/sed:g' ${S}/CMakeLists.txt
+sed -i -e 's:NAMES\ grep:NAMES\ ${HOSTTOOLS_DIR}/grep:g' 
${S}/CMakeLists.txt
+}
+
+FILES:${PN} += "${datadir}/xml"
+
+RDEPENDS:${PN} = "openscap"
-- 
2.25.1


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

[yocto] [meta-security][PATCH] scap-security-guide_git: drop oe version

[Armin Kuster]

This is un-maintained so dropping this version

Signed-off-by: Armin Kuster 
---
 ...ng-of-the-remediation-functions-file.patch | 39 -
 ...c-file-check-tests-in-installed-OS-d.patch | 46 ---
 ...ated-instance-of-element.getchildren.patch | 43 --
 ...is_openembedded-Update-pattern-match.patch | 30 --
 ...g-openembedded-from-ssg-constants.py.patch | 34 ---
 ...-fix-when-greedy-regex-ate-the-whole.patch | 35 ---
 ...-fix-deprecated-getiterator-function.patch | 58 ---
 ...etchildren-and-getiterator-functions.patch | 57 --
 .../scap-security-guide.inc   | 35 ---
 .../scap-security-guide_git.bb| 18 --
 10 files changed, 395 deletions(-)
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-Fix-XML-parsing-of-the-remediation-functions-file.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-Fix-platform-spec-file-check-tests-in-installed-OS-d.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-fix-deprecated-instance-of-element.getchildren.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-installed_OS_is_openembedded-Update-pattern-match.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0002-Fix-missing-openembedded-from-ssg-constants.py.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0002-Fixed-the-broken-fix-when-greedy-regex-ate-the-whole.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0002-fix-deprecated-getiterator-function.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/files/0003-fix-remaining-getchildren-and-getiterator-functions.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
 delete mode 100644 
meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb

diff --git 
a/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-Fix-XML-parsing-of-the-remediation-functions-file.patch
 
b/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-Fix-XML-parsing-of-the-remediation-functions-file.patch
deleted file mode 100644
index c0b93e4..000
--- 
a/meta-security-compliance/recipes-openscap/scap-security-guide/files/0001-Fix-XML-parsing-of-the-remediation-functions-file.patch
+++ /dev/null
@@ -1,39 +0,0 @@
-From 174293162e5840684d967e36840fc1f9f57c90be Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Thu, 5 Dec 2019 15:02:05 +0100
-Subject: [PATCH] Fix XML "parsing" of the remediation functions file.
-
-A proper fix is not worth the effort, as we aim to kill shared Bash remediation
-with Jinja2 macros.
-
-Upstream-Status: Backport
-[https://github.com/ComplianceAsCode/content/commit/174293162e5840684d967e36840fc1f9f57c90be]
-
-Signed-off-by: Yi Zhao 

- ssg/build_remediations.py | 8 
- 1 file changed, 4 insertions(+), 4 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 7da807bd6..13e90f732 100644
 a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -56,11 +56,11 @@ def get_available_functions(build_dir):
- remediation_functions = []
- with codecs.open(xmlfilepath, "r", encoding="utf-8") as xmlfile:
- filestring = xmlfile.read()
--# This regex looks implementation dependent but we can rely on
--# ElementTree sorting XML attrs alphabetically. Hidden is guaranteed
--# to be the first attr and ID is guaranteed to be second.
-+# This regex looks implementation dependent but we can rely on the 
element attributes
-+# being present on one line.
-+# We can't rely on ElementTree sorting XML attrs in any way since 
Python 3.7.
- remediation_functions = re.findall(
--r'
-Date: Thu, 7 Jan 2021 18:10:01 -0500
-Subject: [PATCH 1/3] Fix platform spec, file check, tests in installed OS
- detect for openembedded
-
-Change platform to multi in openembedded installed check matching others
-and allowing compile of xml into oval

- shared/checks/oval/installed_OS_is_openembedded.xml | 11 ++-
- 1 file changed, 6 insertions(+), 5 deletions(-)
-
-diff --git a/shared/checks/oval/installed_OS_is_openembedded.xml 
b/shared/checks/oval/installed_OS_is_openembedded.xml
-index 763d17bcb..01df16b43 100644
 a/shared/checks/oval/installed_OS_is_openembedded.xml
-+++ b/shared/checks/oval/installed_OS_is_openembedded.xml
-@@ -1,11 +1,9 @@
--
--
- 
-   
- 
-   OpenEmbedded
-   
--OPENEMBEDDED
-+multi_platform_all
-   
-   
-@@ -20,8 +18,11 @@
- 
-   
- 
--  
--

Re: [yocto] [auto-upgrade-helper] Should AUH send patches in-line instead of as attachments?

[Alexander Kanavin]

On Tue, 6 Jun 2023 at 21:17, Konstantin Ryabitsev
 wrote:
>
> On Tue, Jun 06, 2023 at 08:09:40PM +0200, Alexander Kanavin wrote:
> > Thanks, that seems reasonable, but is then it still ok to attach additional
> > build artifacts (logs etc) to the message? Will the tools first discard the
> > attachments, take the message body, then apply the scissors to get the
> > patch out?
>
> Yes, I believe most tools will handle this situation just fine -- at least b4
> does for sure, and so should patchwork.

I added a tweak to AUH that would do the scissors thingy with the patch:
https://lists.yoctoproject.org/g/yocto/message/60252

Alex

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

[yocto] [auh][PATCH] upgrade-helper.py: add patches directly to AUH emails, in addition to attaching them as files

[Alexander Kanavin]

This utilizes the 'scissors' feature as described here

https://git-scm.com/docs/git-mailinfo#Documentation/git-mailinfo.txt---scissors

and allows easy handling of AUH emails with tools like b4, patchwork or
even 'git am' directly, eliminating the need to get the attachment first.

Signed-off-by: Alexander Kanavin 
---
 upgrade-helper.py | 4 
 1 file changed, 4 insertions(+)

diff --git a/upgrade-helper.py b/upgrade-helper.py
index 4393589..4f0b6b7 100755
--- a/upgrade-helper.py
+++ b/upgrade-helper.py
@@ -358,6 +358,10 @@ class Updater(object):
 attachment_fullpath = os.path.join(pkg_ctx['workdir'], attachment)
 if os.path.isfile(attachment_fullpath):
 attachments.append(attachment_fullpath)
+# Also add the patch inline using the 'scissors':
+# 
https://git-scm.com/docs/git-mailinfo#Documentation/git-mailinfo.txt---scissors
+if attachment_fullpath.endswith('.patch'):
+msg_body += "\n\n-- >8 --\n%s" % 
(open(attachment_fullpath).read())
 
 if self.opts['send_email']:
 self.email_handler.send_email(to_addr, subject, msg_body, 
attachments, cc_addr=cc_addr)
-- 
2.30.2


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

Re: [yocto] Submit a new layer meta-loongarch to the layer index

[Ross Burton]

On 12 Jun 2023, at 10:36, 张家岭  wrote:
>
> Hi Ross:
>
> Thank you , I can edit this layer now , How can I show  this layer in 
> http://layers.openembedded.org/layerindex/branch/master/layers/

It’s there now, at least I can see it.

[cid:76b32aeb-b2a5-45af-abff-382eac2a571b@eurprd08.prod.outlook.com]


Ross

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

Re: [yocto] Submit a new layer meta-loongarch to the layer index

[张家岭]

Hi Ross:

    Thank you , I can edit this layer now , How can I show  this layer 
in http://layers.openembedded.org/layerindex/branch/master/layers/



在 2023/6/12 17:24, Ross Burton 写道:

On 12 Jun 2023, at 07:39, 张家岭  wrote:

Hi Ross:

 I can open this web page 
http://layers.openembedded.org/layerindex/branch/master/layer/meta-loongarch/ , 
but there is no maintainer iterm in this web , so I can not edit this layer . 
Can you add this iterm for me ?

Done.  You definitely filled that in correctly when you submitted the layer, 
but because maintainers are associated with branches it got lost when it 
couldn’t find the master branch.

Cheers,
Ross



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

Re: [yocto] Approach for generating two WIC files at once

[Alexander Kanavin]

sdcard-base.inc is better, because sdcard-base.bb is a recipe in
itself, but you don't want to build that (or others to get confused
about its purpose).

Alex

On Wed, 7 Jun 2023 at 16:56, Konstantin Kletschke
 wrote:
>
> On Wed, Jun 07, 2023 at 02:15:30PM +0200, Alexander Kanavin wrote:
> > The easiest is probably to make two image recipes pointing to
> > different wic files, but sharing everything else via .inc.
>
> You mean moving my current meta-insidem2m/recipes-core/images/sdcard.bb
> to something like meta-insidem2m/recipes-core/images/sdcard_base.bb,
> creating two new ones like sdcard_d.bb and sdcard_y.bb among the
> sdcard_base.bb, require the sdcard_base.bb from sdcard_d.bb and sdcard_y.bb
> and having the latter files overwrite the variable WKS_FILE with
> different ones?
>
> According to preliminary tests the search path for wks files also
> include meta-insidem2m/recipes-core/images where the sdcard*.bb are
> located and could ne put right there.
>
> This way? I will test, that sounds convenient.
>
> Kind Regards
> Konstantin

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

Re: [yocto] Submit a new layer meta-loongarch to the layer index

[Ross Burton]

On 12 Jun 2023, at 07:39, 张家岭  wrote:
> 
> Hi Ross:
> 
> I can open this web page 
> http://layers.openembedded.org/layerindex/branch/master/layer/meta-loongarch/ 
> , but there is no maintainer iterm in this web , so I can not edit this layer 
> . Can you add this iterm for me ?

Done.  You definitely filled that in correctly when you submitted the layer, 
but because maintainers are associated with branches it got lost when it 
couldn’t find the master branch.

Cheers,
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60248): https://lists.yoctoproject.org/g/yocto/message/60248
Mute This Topic: https://lists.yoctoproject.org/mt/99403007/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [yocto-kernel-cache][master/yocto-6.1 PATCH 2/2] efi: add ACPI enablement

[Andrei Gherzan]

Hi all,

On Tue, Jun 6, 2023 at 4:33 PM Clément Péron  wrote:

> Hi,
>
> On Tue, 6 Jun 2023 at 17:32, Clément Péron via lists.yoctoproject.org
>  wrote:
> >
> > Hi,
> >
> > On 03/03/2023 17:28, Jon Mason wrote:
> > > /ATA
> > >
> > > On Wed, Mar 1, 2023 at 10:38 AM Bruce Ashfield <
> bruce.ashfi...@gmail.com> wrote:
> > >>
> > >> Patch 1/2 looks fine, but 2/2 reverts the following commit:
> > >>
> > >> ==
> > >> commit 41751659d0650c4effdd598f26febba39aeaf082
> > >> Author: Andrei Gherzan 
> > >> Date:   Mon Aug 22 19:55:10 2022 +0200
> > >>
> > >>  efi.cfg: Drop ACPI dependency
> > >>
> > >>  On X86 this will have no impact as CONFIG_ACPI is enabled by
> default. On
> > >>  the other hand, ARM64 would be affected as they don't have the
> same
> > >>  default. The defconfig for arm64 recommends CONFIG_ACPI and this
> patch
> > >>  follows this recommendation in the qemuarm64 bsp configuration
> to fix
> > >>  ACPI-only EFI boots on this arch.
> > >>
> > >>  arm (32bit) would also be unaffected as there is no ACPI support
> there
> > >>  at all. And this unconditional drop (CONFIG_ACPI) will actually
> fix a
> > >>  configuration warning when enabling EFI on a arm (32bit) machine:
> > >>
> > >>  [INFO]: config 'CONFIG_ACPI' was set, but it wasn't assignable,
> check (parent) dependencies
> > >
> > > What's weird is that I'm not seeing this issue at all, and I'm
> > > compiling with and without efi enabled.  See
> > >
> https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-kernel/linux/linux-yocto_%25.bbappend
> > >
> https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-kernel/linux/files/efi.cfg
> > >
> > > with edk2 (uefi)
> > > https://gitlab.com/jonmason00/meta-arm/-/jobs/3868649253
> > > without edk2 (using u-boot)
> > > https://gitlab.com/jonmason00/meta-arm/-/jobs/3868649241
> > >
> > > For giggles, I added the same efi.cfg to qemuarmv5 to see if it would
> > > cause an issue (as maybe the sstate is hiding the warnings), and I
> > > don't see it there either.  Is there a better way than this to
> > > replicate it?
> > >
> > > Also, if this one is holding the other back, feel free to drop and
> > > I'll mess with it again later.
> >
> > +Andrei Gherzan to this mail,
> Resent with proper email.
>
> >
> > I'm also facing the same issue, with a qemuarm64 board MACHINE_FEATURES
> > have the EFI but it refuses to boot and I needed to manually set
> > CONFIG_ACPI as it was missing to my kernel config.
> >
> > @Andrei could you explain which ACPI-only ARM64 EFI boots would break
> > with this patch?
>

Hard for me to remember the details after so long. I'm pretty sure it was
for one of the QEMU EFI machines part of the Oniro project (
https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/tree/kirkstone/meta-oniro-core/conf/machine).
I am not active on that project anymore so I won't be able to assist more
with logs and reproducible steps. Still, I'll add Stefan to this thread,
who might be able to help.

Andrei

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

Re: [yocto] Submit a new layer meta-loongarch to the layer index

[张家岭]

Hi Ross:

        I can open this web page 
http://layers.openembedded.org/layerindex/branch/master/layer/meta-loongarch/ 
, but there is no maintainer iterm in this web , so I can not edit this 
layer . Can you add this iterm for me ?



在 2023/6/12 10:04, 张家岭 写道:

Hi Ross .

    I have changed the default branch to master, But I stil get this 
error , is there something wrong in self.active_maintainers()?


```

/usr/local/lib/python3.10/dist-packages/django/core/handlers/exception.py, 
line 47, in inner

    response = get_response(request) …
▼ Local vars
Variable    Value
exc
TypeError("'NoneType' object is not iterable")
get_response
>

request

/usr/local/lib/python3.10/dist-packages/django/core/handlers/base.py, 
line 181, in _get_response
    response = wrapped_callback(request, *callback_args, 
**callback_kwargs) …

▼ Local vars
Variable    Value
callback

callback_args
()
callback_kwargs
{'branch': 'master', 'slug': 'meta-loongarch'}
middleware_method
>

request

response
None
self

wrapped_callback

/usr/local/lib/python3.10/dist-packages/django/views/generic/base.py, 
line 70, in view

    return self.dispatch(request, *args, **kwargs) …
▼ Local vars
Variable    Value
args
()
cls

initkwargs
{'template_name': 'layerindex/detail.html'}
kwargs
{'branch': 'master', 'slug': 'meta-loongarch'}
request

self

/opt/layerindex/layerindex/views.py, line 410, in dispatch
    res = super(LayerDetailView, self).dispatch(request, *args, 
**kwargs) …

▼ Local vars
Variable    Value
__class__

args
()
kwargs
{'branch': 'master', 'slug': 'meta-loongarch'}
request

self

/usr/local/lib/python3.10/dist-packages/django/views/generic/base.py, 
line 98, in dispatch

    return handler(request, *args, **kwargs) …
▼ Local vars
Variable    Value
args
()
handler
object at 0x7f437af523b0>>

kwargs
{'branch': 'master', 'slug': 'meta-loongarch'}
request

self

/usr/local/lib/python3.10/dist-packages/django/views/generic/detail.py, 
line 107, in get

    context = self.get_context_data(object=self.object) …
▼ Local vars
Variable    Value
args
()
kwargs
{'branch': 'master', 'slug': 'meta-loongarch'}
request

self

/opt/layerindex/layerindex/views.py, line 424, in get_context_data
    context['useredit'] = layer.user_can_edit(self.user) …
▼ Local vars
Variable    Value
__class__

context
{'layeritem': ,
 'object': ,
 'view': }
kwargs
{'object': }
layer

self

/opt/layerindex/layerindex/models.py, line 178, in user_can_edit
    for maintainer in self.active_maintainers(): …
▼ Local vars
Variable    Value
self

user
>
user_email
'zhangjial...@loongson.cn'

```
在 2023/6/9 19:33, Ross Burton 写道:

Hi,

This would be 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14989, because your 
layer has a ‘main’ branch not a ‘master’ branch.  You can either 
rename main to master, or keep a master branch in sync with main, or 
wait for that to be fixed.


Ross



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

[yocto] [meta-security][PATCH] complicance/isafw: remove oeqa addpylib

[Chen Qi via lists.yoctoproject.org]

From: Chen Qi 

These two layers do not have oeqa lib modules. Remove these two
lines. Otherwise, `bitbake-layers add-layer ' would fail
if either of these two layers are in BBLAYERS.

Signed-off-by: Chen Qi 
---
 meta-security-compliance/conf/layer.conf | 2 --
 meta-security-isafw/conf/layer.conf  | 2 --
 2 files changed, 4 deletions(-)

diff --git a/meta-security-compliance/conf/layer.conf 
b/meta-security-compliance/conf/layer.conf
index cb33c2c..82409a6 100644
--- a/meta-security-compliance/conf/layer.conf
+++ b/meta-security-compliance/conf/layer.conf
@@ -13,5 +13,3 @@ LAYERSERIES_COMPAT_scanners-layer = "mickledore"
 LAYERDEPENDS_scanners-layer = "core openembedded-layer meta-python"
 
 BBLAYERS_LAYERINDEX_NAME_scanners-layer = "meta-security-compliance"
-
-addpylib ${LAYERDIR}/lib oeqa
diff --git a/meta-security-isafw/conf/layer.conf 
b/meta-security-isafw/conf/layer.conf
index fca5868..550cced 100644
--- a/meta-security-isafw/conf/layer.conf
+++ b/meta-security-isafw/conf/layer.conf
@@ -15,5 +15,3 @@ LAYERVERSION_security-isafw = "1"
 LAYERDEPENDS_security-isafw = "core"
 
 LAYERSERIES_COMPAT_security-isafw = "mickledore"
-
-addpylib ${LAYERDIR}/lib oeqa
-- 
2.40.0


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