date:20221024

[linux-yocto][linux-yocto v5.15/standard/sdkv5.10/axxia & v5.15/standard/preempt-rt/sdkv5.10/axxia ][PATCH 1/1] usb: ehci: adjust to use platform_drivers to register/unregister driver

2022-10-24 Thread LiweiSong

Since upstream commit aad06846a230 ("usb: ehci: Simplify platform driver
registration"), PLATFORM_DRIVER was replace by platform_drivers,
adjust the old implement to use platform_drivers to register or
unregister platform.

This is use to fix a compile warning that import by axxia SDK
commit 7048bd2a0f58 ("usb: xhci: Add CI13612A USB driver for
Axxia AXM55xx"):

In file included from drivers/usb/host/ehci-hcd.c:1325:0:
drivers/usb/host/ehci-ci13612.c:223:31: warning: ‘ci13612_ehci_driver’ defined 
but not used [-Wunused-variable]
 static struct platform_driver ci13612_ehci_driver = {
   ^~~

Signed-off-by: Liwei Song 
---
 drivers/usb/host/ehci-hcd.c | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
index 8e0414e8438e..9b9dca484237 100644
--- a/drivers/usb/host/ehci-hcd.c
+++ b/drivers/usb/host/ehci-hcd.c
@@ -1306,6 +1306,10 @@ MODULE_LICENSE ("GPL");
 #include "ehci-grlib.c"
 #endif
 
+#ifdef CONFIG_USB_CI13612_HCD
+#include "ehci-ci13612.c"
+#endif
+
 static struct platform_driver * const platform_drivers[] = {
 #ifdef CONFIG_USB_EHCI_SH
_hcd_sh_driver,
@@ -1319,12 +1323,10 @@ static struct platform_driver * const 
platform_drivers[] = {
 #ifdef CONFIG_SPARC_LEON
_grlib_driver,
 #endif
-};
-
 #ifdef CONFIG_USB_CI13612_HCD
-#include "ehci-ci13612.c"
-#define PLATFORM_DRIVERci13612_ehci_driver
+   _ehci_driver,
 #endif
+};
 
 static int __init ehci_hcd_init(void)
 {
-- 
2.32.0


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

2022-10-24 Thread Stephen Jolley

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  14311

AB-INT PTEST: valgrind drd/tests ptest intermittent failure

randy.macl...@windriver.com

randy.macl...@windriver.com

4.1 M4

4.2 M1


 

  14564

AB-INT: udev worker vda timeout

randy.macl...@windriver.com

randy.macl...@windriver.com

4.1 M1

4.2 M2


 

  14907

packaging debugsrc breaks for recipes with externalsrc and debug-with-srcpkg

ola.x.nils...@axis.com

pa...@zhukoff.net

4.1 M4

4.0.5

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

[yocto] Enhancements/Bugs closed WW43!

2022-10-24 Thread Stephen Jolley

All,

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


Who

Count


mark.asselst...@windriver.com

2


randy.macl...@windriver.com

1


Grand Total

3

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

2022-10-24 Thread Stephen Jolley

All,

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


Who

Count


michael.opdenac...@bootlin.com

35


ross.bur...@arm.com

32


randy.macl...@windriver.com

28


bruce.ashfi...@gmail.com

24


david.re...@windriver.com

23


richard.pur...@linuxfoundation.org

16


sakib.sa...@windriver.com

11


jpewhac...@gmail.com

10


pa...@zhukoff.net

9


saul.w...@windriver.com

9


tim.orl...@konsulko.com

7


sundeep.kokko...@gmail.com

3


jon.ma...@arm.com

3


akuster...@gmail.com

3


aryaman.gu...@windriver.com

2


s...@bigsur.com

2


hongxu@windriver.com

2


raj.k...@gmail.com

2


martin.ja...@gmail.com

2


pgowda@gmail.com

2


alexandre.bell...@bootlin.com

2


zheng@windriver.com

2


st...@sakoman.com

2


mhalst...@linuxfoundation.org

1


thomas.per...@bootlin.com

1


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

1


ptsne...@gmail.com

1


tvgamb...@gmail.com

1


nicolas.deche...@linaro.org

1


qi.c...@windriver.com

1


aeh...@gmail.com

1


rybczyn...@gmail.com

1


martin.bee...@online.de

1


mostthings...@gmail.com

1


Grand Total

242

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

2022-10-24 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 414
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.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.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 (#58402): https://lists.yoctoproject.org/g/yocto/message/58402
Mute This Topic: https://lists.yoctoproject.org/mt/94546181/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH] Update PARSEC recipe to latest v1.1.0 release

2022-10-24 Thread Armin Kuster




On 10/20/22 8:39 AM, Gowtham Suresh Kumar wrote:

This commit updates the parsec-service to v1.1.0 and the parsec-tool
to v0.5.4.


merged.

thanks



The buildpaths QA check has been disabled and relevant
issue links have been added to address this.

Signed-off-by: Gowtham Suresh Kumar 
---
  meta-parsec/README.md |   1 +
  ...rvice_1.0.0.bb => parsec-service_1.1.0.bb} |   5 +
  ...ice_1.0.0.inc => parsec-service_1.1.0.inc} | 207 +-
  .../parsec-tool/parsec-tool_0.5.2.inc | 196 -
  ...sec-tool_0.5.2.bb => parsec-tool_0.5.4.bb} |   5 +
  .../parsec-tool/parsec-tool_0.5.4.inc | 176 +++
  6 files changed, 286 insertions(+), 304 deletions(-)
  rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.0.0.bb => 
parsec-service_1.1.0.bb} (95%)
  rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.0.0.inc => 
parsec-service_1.1.0.inc} (52%)
  delete mode 100644 
meta-parsec/recipes-parsec/parsec-tool/parsec-tool_0.5.2.inc
  rename meta-parsec/recipes-parsec/parsec-tool/{parsec-tool_0.5.2.bb => 
parsec-tool_0.5.4.bb} (71%)
  create mode 100644 
meta-parsec/recipes-parsec/parsec-tool/parsec-tool_0.5.4.inc

diff --git a/meta-parsec/README.md b/meta-parsec/README.md
index 99935bc..9b231f6 100644
--- a/meta-parsec/README.md
+++ b/meta-parsec/README.md
@@ -48,6 +48,7 @@ PKCS11 and MBED-CRYPTO providers build-in.
  - DISTRO_FEATURES contains "tmp2" and
  - "tpm-layer" (meta-tpm) is included in BBLAYERS
  
+The trusted service provider depends on libts recipe from meta-arm layer.
  
  You can use PACKAGECONFIG for Parsec servic recipe to define

  what providers should be built in. For example:
diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.bb 
b/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.bb
similarity index 95%
rename from meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.bb
rename to meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.bb
index 931abee..218b776 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.bb
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.bb
@@ -83,3 +83,8 @@ FILES:${PN} += " \
  "
  
  require parsec-service_${PV}.inc

+
+# The QA check has been temporarily disabled. An issue has been created
+# upstream to fix this.
+# https://github.com/parallaxsecond/parsec/issues/645
+INSANE_SKIP:${PN}-dbg += "buildpaths"
diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.inc 
b/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
similarity index 52%
rename from meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.inc
rename to meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
index b6934f8..c04bcbd 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.0.0.inc
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service_1.1.0.inc
@@ -2,61 +2,59 @@
  
  SRC_URI += " \

  crate://crates.io/ahash/0.7.6 \
-crate://crates.io/aho-corasick/0.7.18 \
+crate://crates.io/aho-corasick/0.7.19 \
  crate://crates.io/ansi_term/0.12.1 \
-crate://crates.io/anyhow/1.0.56 \
-crate://crates.io/arrayvec/0.5.2 \
+crate://crates.io/anyhow/1.0.64 \
+crate://crates.io/asn1-rs-derive/0.1.0 \
+crate://crates.io/asn1-rs-impl/0.1.0 \
+crate://crates.io/asn1-rs/0.3.1 \
  crate://crates.io/atty/0.2.14 \
  crate://crates.io/autocfg/1.1.0 \
-crate://crates.io/base64/0.12.3 \
  crate://crates.io/base64/0.13.0 \
  crate://crates.io/bincode/1.3.3 \
  crate://crates.io/bindgen/0.57.0 \
  crate://crates.io/bindgen/0.59.2 \
  crate://crates.io/bitfield/0.13.2 \
  crate://crates.io/bitflags/1.3.2 \
-crate://crates.io/bitvec/0.19.6 \
-crate://crates.io/bumpalo/3.9.1 \
-crate://crates.io/bytes/1.1.0 \
+crate://crates.io/bumpalo/3.11.0 \
+crate://crates.io/bytes/1.2.1 \
  crate://crates.io/cc/1.0.73 \
  crate://crates.io/cexpr/0.4.0 \
  crate://crates.io/cexpr/0.6.0 \
  crate://crates.io/cfg-if/1.0.0 \
-crate://crates.io/chrono/0.4.19 \
-crate://crates.io/clang-sys/1.3.1 \
+crate://crates.io/clang-sys/1.3.3 \
  crate://crates.io/clap/2.34.0 \
  crate://crates.io/cmake/0.1.45 \
-crate://crates.io/const-oid/0.6.2 \
+crate://crates.io/const-oid/0.7.1 \
  crate://crates.io/cryptoauthlib-sys/0.2.2 \
-crate://crates.io/cryptoki-sys/0.1.3 \
-crate://crates.io/cryptoki/0.2.1 \
+crate://crates.io/cryptoki-sys/0.1.4 \
+crate://crates.io/cryptoki/0.3.0 \
  crate://crates.io/data-encoding/2.3.2 \
-crate://crates.io/der-oid-macro/0.4.0 \
-crate://crates.io/der-parser/5.1.2 \
-crate://crates.io/der/0.4.5 \
+crate://crates.io/der-parser/7.0.0 \
+crate://crates.io/der/0.5.1 \
  crate://crates.io/derivative/2.2.0 \
-crate://crates.io/either/1.6.1 \
-

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

2022-10-24 Thread Michael Opdenacker via lists.yoctoproject.org



On 10/24/22 14:27, Alexander Kanavin wrote:

On Mon, 24 Oct 2022 at 13:58, Peter via lists.yoctoproject.org
 wrote:

However, the documentation recommends the global ban and does not mention the 
per-image variant?
https://docs.yoctoproject.org/ref-manual/images.html
https://docs.yoctoproject.org/ref-manual/variables.html#term-INCOMPATIBLE_LICENSE

Yes, someone should go over the documentation and change every mention
of this to recommend per-image variant, as a global one is basically
impossible to use without pulling in meta-gpl2. Patches welcome :)


Out of curiosity, why does the per image variant work, but not the global ban?

Global ban works at the task dependency creation stage, and if bash
needs to be built, it will throw an error, even if the actual bash
binary will not end up in the image, and is only used as a runtime
dependency for a package that won't be installed.
Per-image ban performs a 'late' check when the image is actually put together.

You should now know everything to fix the docs ;-)


Thanks! I should be able to send a patch this week.

Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


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

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

2022-10-24 Thread Alexander Kanavin

On Mon, 24 Oct 2022 at 13:58, Peter via lists.yoctoproject.org
 wrote:
> However, the documentation recommends the global ban and does not mention the 
> per-image variant?
> https://docs.yoctoproject.org/ref-manual/images.html
> https://docs.yoctoproject.org/ref-manual/variables.html#term-INCOMPATIBLE_LICENSE

Yes, someone should go over the documentation and change every mention
of this to recommend per-image variant, as a global one is basically
impossible to use without pulling in meta-gpl2. Patches welcome :)

> Out of curiosity, why does the per image variant work, but not the global ban?

Global ban works at the task dependency creation stage, and if bash
needs to be built, it will throw an error, even if the actual bash
binary will not end up in the image, and is only used as a runtime
dependency for a package that won't be installed.
Per-image ban performs a 'late' check when the image is actually put together.

You should now know everything to fix the docs ;-)

> And how should one know to use the pn- prefix? i.e.
> this: INCOMPATIBLE_LICENSE:pn-core-image-minimal
> not this: INCOMPATIBLE_LICENSE:core-image-minimal?

pn- means 'applies only to this recipe'. The package vs recipe
terminology is confusing here for historical reasons.

Alex

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

[yocto-announce] [ANNOUNCEMENT] Yocto Project 4.1 is Released

2022-10-24 Thread Lee Chee Yang

Hi

We are pleased to announce the Yocto Project 4.1 Release is now available for 
download.

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/poky-5200799866b92259e855051112520006e1c0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.1/poky-5200799866b92259e855051112520006e1c0.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/testreport.txt

Thank you for everyone's contributions to this release.

Chee Yang
chee.yang@intel.com
Yocto Project Build and Release


Release notes for 4.1 (langdale)
- -


New Features / Enhancements in 4.1
~

- - Linux kernel 5.19, glibc 2.36 and ~260 other recipe upgrades

- - `make` 4.0 is now the minimum make version required on the build host.
  For host distros that do not provide it, this is included as part of the
  `buildtools-tarball`, and additionally a new `buildtools-make-tarball`
  has been introduced to provide this in particular for host distros with
  a broken make 4.x version. For more details see
  `ref-manual/system-requirements:required git, tar, python, make and gcc 
versions`.

- - New layer setup tooling:

  - New `scripts/oe-setup-layers` standalone script to restore the layer
configuration from a json file
  - New `bitbake-layers create-layers-setup` command to save the
layer configuration to a json file
  - New `bitbake-layers save-build-conf` command to save the active build
configuration as a template into a layer

- - Rust-related enhancements:

  - Support for building rust for the target
  - Significant SDK toolchain build optimisation
  - Support for building native components in the SDK
  - Support `crate://` fetcher with `externalsrc`

- - New core recipes:

  - `buildtools-make-tarball`
  - `icon-naming-utils` (previously removed)
  - `musl-locales`
  - `python3-editables` (originally in meta-python)
  - `python3-hatch-vcs`
  - `python3-hatchling` (originally in meta-oe)
  - `python3-lxml` (originally in meta-python)
  - `python3-pathspec` (originally in meta-python)
  - `python3-picobuild`
  - `sato-icon-theme` (previously removed)

- - CVE checking enhancements:

  - New `CVE_DB_UPDATE_INTERVAL` variable to allow specifying the CVE database 
minimum update interval (and default to once per day)
  - Added JSON format to summary output
  - Added support for Ignored CVEs
  - Enable recursive CVE checking also for `do_populate_sdk`
  - New `CVE_CHECK_SHOW_WARNINGS` variable to disable unpatched CVE warning 
messages
  - The `pypi` class now defaults `CVE_PRODUCT` from `PYPI_PACKAGE`
  - Added current kernel CVEs to ignore list since we stay as close to the 
kernel stable releases as we can
  - Optimisations to avoid dependencies on fetching

- - Complementary package installation (as used in SDKs and images) no longer 
installs recommended packages, in order to avoid conflicts
- - Dependency of -dev package on main package is now an `RRECOMMENDS` and can 
be easily set via new `DEV_PKG_DEPENDENCY` variable

- - Support for CPU, I/O and memory pressure regulation in BitBake
- - Pressure data gathering in `buildstats` and rendering in `pybootchartgui`

- - New Picobuild system for lightweight Python PEP-517 build support in the 
`python_pep517` class

- - Many classes are now split into global and recipe contexts for better
  validation. For more information, see
  `Classes now split by usage context`.

- -  Architecture-specific enhancements:

   - arch-armv8-4a.inc: add tune include for armv8.4a
   - tune-neoversen2: support tune-neoversen2 base on armv9a
   - riscv: Add tunes for rv64 without compressed instructions
   - gnu-efi: enable for riscv64
   - shadow-securetty: allow ttyS4 for amd-snowyowl-64

- -  Kernel-related enhancements:

   - linux-yocto/5.15: cfg/xen: Move x86 configs to separate file
   - linux-yocto/5.15: Enabled MDIO bus config
   - linux-yocto: Enable mdio for qemu
   - linux-yocto/5.15: base: enable kernel crypto userspace API
   - kern-tools: allow 'y' or 'm' to avoid config audit warnings
   - kernel-yocto.bbclass: say what SRC_URI entry is being dropped
   - kernel.bbclass: Do not overwrite recipe's custom postinst
   - kmod: Enable xz support by default
   - Run depmod(wrapper) against each compiled kernel when multiple kernels are 
enabled
   - linux-yocto-tiny: enable qemuarmv5/qemuarm64

- -  wic Image Creator enhancements:

   - Added dependencies to support erofs
   - Added `fspassno` parameter to partition to allow specifying the value of 
the last column (`fs_passno`) in `/etc/fstab`.
   - bootimg-efi: added support for loading devicetree files
   - Added `none` fstype for custom image (for use in conjunction with 
`rawcopy`)

- -  SDK-related enhancements:

   - `Support for using the regular build system as

[yocto] [ANNOUNCEMENT] Yocto Project 4.1 is Released

2022-10-24 Thread Lee Chee Yang

Hi

We are pleased to announce the Yocto Project 4.1 Release is now available for 
download.

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/poky-5200799866b92259e855051112520006e1c0.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.1/poky-5200799866b92259e855051112520006e1c0.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-4.1/testreport.txt

Thank you for everyone's contributions to this release.

Chee Yang
chee.yang@intel.com
Yocto Project Build and Release


Release notes for 4.1 (langdale)
- -


New Features / Enhancements in 4.1
~

- - Linux kernel 5.19, glibc 2.36 and ~260 other recipe upgrades

- - `make` 4.0 is now the minimum make version required on the build host.
  For host distros that do not provide it, this is included as part of the
  `buildtools-tarball`, and additionally a new `buildtools-make-tarball`
  has been introduced to provide this in particular for host distros with
  a broken make 4.x version. For more details see
  `ref-manual/system-requirements:required git, tar, python, make and gcc 
versions`.

- - New layer setup tooling:

  - New `scripts/oe-setup-layers` standalone script to restore the layer
configuration from a json file
  - New `bitbake-layers create-layers-setup` command to save the
layer configuration to a json file
  - New `bitbake-layers save-build-conf` command to save the active build
configuration as a template into a layer

- - Rust-related enhancements:

  - Support for building rust for the target
  - Significant SDK toolchain build optimisation
  - Support for building native components in the SDK
  - Support `crate://` fetcher with `externalsrc`

- - New core recipes:

  - `buildtools-make-tarball`
  - `icon-naming-utils` (previously removed)
  - `musl-locales`
  - `python3-editables` (originally in meta-python)
  - `python3-hatch-vcs`
  - `python3-hatchling` (originally in meta-oe)
  - `python3-lxml` (originally in meta-python)
  - `python3-pathspec` (originally in meta-python)
  - `python3-picobuild`
  - `sato-icon-theme` (previously removed)

- - CVE checking enhancements:

  - New `CVE_DB_UPDATE_INTERVAL` variable to allow specifying the CVE database 
minimum update interval (and default to once per day)
  - Added JSON format to summary output
  - Added support for Ignored CVEs
  - Enable recursive CVE checking also for `do_populate_sdk`
  - New `CVE_CHECK_SHOW_WARNINGS` variable to disable unpatched CVE warning 
messages
  - The `pypi` class now defaults `CVE_PRODUCT` from `PYPI_PACKAGE`
  - Added current kernel CVEs to ignore list since we stay as close to the 
kernel stable releases as we can
  - Optimisations to avoid dependencies on fetching

- - Complementary package installation (as used in SDKs and images) no longer 
installs recommended packages, in order to avoid conflicts
- - Dependency of -dev package on main package is now an `RRECOMMENDS` and can 
be easily set via new `DEV_PKG_DEPENDENCY` variable

- - Support for CPU, I/O and memory pressure regulation in BitBake
- - Pressure data gathering in `buildstats` and rendering in `pybootchartgui`

- - New Picobuild system for lightweight Python PEP-517 build support in the 
`python_pep517` class

- - Many classes are now split into global and recipe contexts for better
  validation. For more information, see
  `Classes now split by usage context`.

- -  Architecture-specific enhancements:

   - arch-armv8-4a.inc: add tune include for armv8.4a
   - tune-neoversen2: support tune-neoversen2 base on armv9a
   - riscv: Add tunes for rv64 without compressed instructions
   - gnu-efi: enable for riscv64
   - shadow-securetty: allow ttyS4 for amd-snowyowl-64

- -  Kernel-related enhancements:

   - linux-yocto/5.15: cfg/xen: Move x86 configs to separate file
   - linux-yocto/5.15: Enabled MDIO bus config
   - linux-yocto: Enable mdio for qemu
   - linux-yocto/5.15: base: enable kernel crypto userspace API
   - kern-tools: allow 'y' or 'm' to avoid config audit warnings
   - kernel-yocto.bbclass: say what SRC_URI entry is being dropped
   - kernel.bbclass: Do not overwrite recipe's custom postinst
   - kmod: Enable xz support by default
   - Run depmod(wrapper) against each compiled kernel when multiple kernels are 
enabled
   - linux-yocto-tiny: enable qemuarmv5/qemuarm64

- -  wic Image Creator enhancements:

   - Added dependencies to support erofs
   - Added `fspassno` parameter to partition to allow specifying the value of 
the last column (`fs_passno`) in `/etc/fstab`.
   - bootimg-efi: added support for loading devicetree files
   - Added `none` fstype for custom image (for use in conjunction with 
`rawcopy`)

- -  SDK-related enhancements:

   - `Support for using the regular build system as

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

2022-10-24 Thread Peter via lists.yoctoproject.org

Hi Alex and Michael

Thank you very much, that worked for core-image-minimal and core-image-weston, 
with kirkstone-4.0.4

For core-image-weston, copying the "Settings for weston" from 
incompatible_lic.py#n149 ( 
https://git.yoctoproject.org/poky/tree/meta/lib/oeqa/selftest/cases/incompatible_lic.py#n149
 ) works.
And core-image-minimal works automatically with just 
INCOMPATIBLE_LICENSE:pn-core-image-minimal = "GPL-3.0* LGPL-3.0* AGPL-3.0*"

Whereas, the global ban produced errors e.g.:
INCOMPATIBLE_LICENSE = "GPL-3.0* LGPL-3.0* AGPL-3.0*"
...
ERROR: Nothing RPROVIDES 'bash' (but 
/workdir/poky/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.5.0.bb, 
/workdir/poky/poky/meta/recipes-devtools/python/python3_3.10.4.bb RDEPENDS on 
or otherwise requires it)
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'packagegroup-core-boot', 'update-alternatives-opkg', 'bash']

However, the documentation recommends the global ban and does not mention the 
per-image variant?
https://docs.yoctoproject.org/ref-manual/images.html
https://docs.yoctoproject.org/ref-manual/variables.html#term-INCOMPATIBLE_LICENSE

Out of curiosity, why does the per image variant work, but not the global ban?
And how should one know to use the pn- prefix? i.e.
this: INCOMPATIBLE_LICENSE:pn-core-image-minimal
not this: INCOMPATIBLE_LICENSE:core-image-minimal?

Thank you
-- Peter

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

[yocto] [meta-mingw][kirkstone][PATCH] toolchain-scripts-mingw32.bbclass: Remove trailing slash in SDKROOT

2022-10-24 Thread Muhammad Hamza

Modify toolchain-scripts-mingw32.bbclass to add a check in
environment-setup script which removes trailing slash in
path of SDKROOT.
This is needed to avoid multiple adjacent slashes in paths
which are produced by appending to SDKROOT.
In reference to 
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN
naming convention used for paths and disk drives in windows
should use a single backslash. Even though in some cases windows
ignores double slashes in paths and it might work but it isn't
documented as a right naming convention and does fail in some
cases eg. dir command cannot interpret double slashes and fails.

For example if my SDK is located in D: drive, the environment
setup scripts sets "SDKROOT=D:\" and hence SDKTARGETSYSROOT
gets set as "SDKTARGETSYSROOT=D:\\sysroots\armv8a-oe-linux"
The introduced check removes additional slash in SDKROOT to
set it as "SDKROOT=D:" so all other variables using SDKROOT
get set without additional slash.

Signed-off-by: Muhammad Hamza 
---
 classes/toolchain-scripts-mingw32.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/classes/toolchain-scripts-mingw32.bbclass 
b/classes/toolchain-scripts-mingw32.bbclass
index d96cb40..8cb426a 100644
--- a/classes/toolchain-scripts-mingw32.bbclass
+++ b/classes/toolchain-scripts-mingw32.bbclass
@@ -12,6 +12,7 @@ toolchain_create_sdk_env_script:sdkmingw32 () {
touch $script
# Be sure to use the 'short' path, so we can have deeper directories.
echo 'set SDKROOT=%~sdp0%' >> $script
+   echo 'IF %SDKROOT:~-1%==\ set SDKROOT=%SDKROOT:~0,-1%' >> $script
 
# Convert to mingw32 subpaths
sysroot='%SDKROOT%'${sysroot##${SDKPATH}}
-- 
2.25.1


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

[linux-yocto][linux-yocto v5.15/standard/sdkv5.10/axxia & v5.15/standard/preempt-rt/sdkv5.10/axxia ][PATCH 1/1] usb: ehci: adjust to use platform_drivers to register/unregister driver

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

[yocto] Enhancements/Bugs closed WW43!

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

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

Re: [yocto] [meta-security][PATCH] Update PARSEC recipe to latest v1.1.0 release

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

[yocto-announce] [ANNOUNCEMENT] Yocto Project 4.1 is Released

[yocto] [ANNOUNCEMENT] Yocto Project 4.1 is Released

Re: [yocto] other ways of removing GPLv3 components (than meta-gplv2) #gplv3

[yocto] [meta-mingw][kirkstone][PATCH] toolchain-scripts-mingw32.bbclass: Remove trailing slash in SDKROOT

12 matches

Site Navigation

Mail list logo

Footer information