linux/poky.git/scripts, branch 5.1_M3

runqemu: add sd card device

2024-08-30T20:59:38+00:00

runqemu currently only supports scsi, ide and virtio drive types. Implement QB_DRIVE_TYPE=/dev/mmcblk which adds an sdhci-pci device and mounts the rootfs file as an sd card. (From OE-Core rev: 0740896afbe13f37058e990a0a13b2b51bba70fd) Signed-off-by: Alessandro Pecugi Signed-off-by: Richard Purdie

runqemu: Fix detection of -serial parameter

2024-08-30T20:59:38+00:00

The pattern `-serial` matches also `-device usb-serial` and `virtio-serial` which are not the desired parameter. This causes the serial console ttyS1 is missing and Systemd's getty@ttyS1 fails constantly. (From OE-Core rev: b6d035894120b45b42f146ab5b3110522c58d178) Signed-off-by: Jörg Sommer Signed-off-by: Richard Purdie

resulttool: Add support to create test report in JUnit XML format

2024-08-29T20:58:19+00:00

This adds the functionality to convert the results of the testresults.json file to a unit test report in JUnit XML format. The unit test report can be used in the CI/CD pipeline to display the test results. To use the resulttool scripts, first source oe environment, then run the entry point script to look for help. $ resulttool To generate the unit test report, execute the below $ resulttool junit By default the unit test report is stored as /tmp/log/oeqa/junit.xml. (From OE-Core rev: 3f9be03946243feaa09b908d7010899769091fe6) Signed-off-by: Clara Kowalsky Signed-off-by: Richard Purdie

cve-json-to-text: add script

2024-08-25T14:36:30+00:00

Add a script that converts the cve-check result from the JSON format to the TEXT format. (From OE-Core rev: da4e01dfa538578936e565413871a7496b8752df) Signed-off-by: Marta Rybczynska Signed-off-by: Richard Purdie

recipetool: create_npm: reuse license utils

2024-08-23T08:51:36+00:00

create_npm.py duplicated the logic for matching licenses from files and also finding them. This patch refactors the code to reuse the license utils. This will make the code more maintainable and also align both behaviors. For instance, some licenses weren't matched properly because the duplicate logic did not support the difference in format in the md5 tables for COMMON_LICENSE_DIR and licenses.csv. This is also faster since the license files were being read twice. The result is slightly more accurate since the utils have better implementations, and I was able to reuse the logic for the root PN package, as well as the base LICENSE variable. I chose to extract generate_common_licenses_chksums into create.py since it can be considered a general utility function to allow other recipetool creators to refer to COMMON_LICENSE_DIR files. I updated the wording in the code when appropriate. v3: - added commit - this replaces the commit that added all the COMMON_LICENSE_DIR md5 to licenses.csv (From OE-Core rev: 7bc18bed63b94689890bcde63402d7cc1cedffa9) Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

recipetool: create: split guess_license function

2024-08-23T08:51:36+00:00

The npm recipetool handler redefines the license code the could be unified. In order to do this refactoring, extract the bits we'll need into separate functions. guess_license() is renamed to find_licenses() and is split into find_license_files() and match_licenses(). (From OE-Core rev: f1ec28feaea8ea6a2df894dd4ddba561c8a04ed2) Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

recipetool: create_npm: resolve licenses defined in package.json

2024-08-23T08:51:36+00:00

Some npm packages do not copy the LICENSE or COPY file into their git repository. They'll instead simply use SPDX identifiers in their package.json. A fallback for those repositories attempted to match the README file to a license file instead, which had a very low probability of success. This commit replaces this fallback with parsing the package.json and looking for the license in COMMON_LICENSE_DIR. If the license is not found, "Unknown" will still be produced. This also generates "Unknown" for packages which had no README file, which could silently not appear in the generated recipe. The user was more likely to miss them. Co-authored-by: Tanguy Raufflet (From OE-Core rev: 445604cfc4a5813ea635f18053cd1f673bf0b830) Signed-off-by: Tanguy Raufflet Signed-off-by: Enguerrand de Ribaucourt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

scripts/patchtest.README: cleanup, add selftest notes

2024-08-05T13:31:57+00:00

Make some minor fixes to grammar and layout, and add a short new section describing how to setup and use the patchtest selftests properly. (From OE-Core rev: 264185d2cfa31b1cf2534a8de21e4b17bb5bbf79) Signed-off-by: Trevor Gamblin Signed-off-by: Richard Purdie

devtool/upgrade: rename RECIPE_UPDATE_EXTRA_TASKS -> RECIPE_UPGRADE_EXTRA_TASKS

2024-08-03T06:56:10+00:00

'UPDATE' as a name is somewhat unfortunate as the variable is intended only for the 'devtool upgrade' operation and devtool also has an 'update-recipe' operation. (From OE-Core rev: 4467aa0661e233f44c4ce029428c67d88fccfc07) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bootimg-partition: break out code to a common library.

2024-07-23T10:17:11+00:00

Break out the code that parse IMAGE_BOOT_FILES to a common library. (From OE-Core rev: 1e07fe51bdb24070308c85e83df0b80ab9f83cea) Signed-off-by: Marcus Folkesson Reviewed-by: Quentin Schulz Reviewed-by: Konrad Weihmann Signed-off-by: Richard Purdie