linux/poky.git/scripts, branch dunfell-23.0.4

update_udev_hwdb: clean hwdb.bin

2020-11-12T13:07:52+00:00

Steps to reproduce: echo "IMAGE_INSTALL_append = \" udev-hwdb lib32-udev-hwdb\"" >> conf/local.conf When install both udev-hwdb and lib32-udev-hwdb as above, there comes below do_populate_sdk error: $ bitbake core-image-sato -c populate_sdk ERROR: Task (/path/core-image-sato.bb:do_populate_sdk) failed with exit code '134' NOTE: Tasks Summary: Attempted 5554 tasks of which 0 didn't need to be rerun and 1 failed. $ cat /path/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r5/pseudo/pseudo.log [snip] inode mismatch: '/path/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r5/sdk/image/usr/local/oecore-x86_64/sysroots/core2-64-poky-linux/lib/udev/hwdb.bin' ino 427383040 in db, 427383042 in request. [snip] It is because both udev-hwdb and lib32-udev-hwdb will generate ${SDK_OUTPUT}/${SDKTARGETSYSROOT}/lib/udev/hwdb.bin during do_populate_sdk and it triggers pseudo error. So clean hwdb.bin before generate hwdb.bin to avoid conflict to fix the above do_populate_sdk error. (From OE-Core rev: 10413cf013ae5a92ef12f33dab8e67f0bfb0ae25) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie (cherry picked from commit c7472925feb53ce92c1799feba2b7a9104e3f38f) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oe-build-perf-report: Ensure correct data is shown for multiple branch options

2020-10-22T11:16:42+00:00

If --branch and --branch2 are the same, there is extra confusing data plotted onto the graph. Only do that if the branches are actually different. (From OE-Core rev: e2240d0a93a9a2932506a356315ad6702ecee9b6) Signed-off-by: Richard Purdie (cherry picked from commit c263d810b7eb47ee90f2adeb5ab6decf7332bec2) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

scripts/oe-build-perf-report: Allow operation with no buildstats

2020-10-22T11:16:41+00:00

If buildstats is missing, avoid a backtrace. (From OE-Core rev: a518443e6799d56b899536d853282182eff4822a) Signed-off-by: Richard Purdie (cherry picked from commit 23c4b21f947c7aae1303ca6526fc5aaaa9fc7bb8) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

wic: Add 512 Byte alignment to --offset

2020-10-06T13:15:22+00:00

Allows the --offset argument to use the "s" or "S" suffix to specify that it is reporting the number of 512 byte sectors. This is required for some SoCs where the mask ROM looks for an item at a sector that isn't aligned to a 1KB boundary. (From OE-Core rev: b9296bdeaacc1dce97aac9c9bf0d70555bb36646) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie (cherry picked from commit 938595d1dc4abaf5f7f3a7900add3f0492b805d0) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

wic: Fix error message when reporting invalid offset

2020-10-06T13:15:22+00:00

The error message was reporting the calculated offset instead of the current offset, which made it confusing. (From OE-Core rev: 0ff25797126772f40e357a2f3cf81eccf659adaf) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie (cherry picked from commit 2be775cfe1b49ce3889b5dc326e2b67a9667f18a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

wic: Fix --extra-space argument handling

2020-10-06T13:15:22+00:00

467f84e12b ("wic: Add --offset argument for partitions") broke the --extra-space argument handling in wic. Fix the option and add a unit test for the argument. (From OE-Core rev: 62a7a10c31bcf133cbd99d4de928f15a30e45ab1) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie (cherry picked from commit 87722a92c18f94917c8f70afc8cd0763462a5c25) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

wic: Add --offset argument for partitions

2020-10-06T13:15:22+00:00

Add support for an --offset argument when defining a partition. Many SoCs require that boot partitions be located at specific offsets. Prior to this argument, most WKS files were using the --align attribute to specify the location of these fixed partitions but this is not ideal because in the event that the partition couldn't be placed in the specified location, wic would move it to the next sector with that alignment, often preventing the device from booting. Unlike the --align argument, wic will fail if a partition cannot be placed at the exact offset specified with --offset. Changes in V2: * Fixed a small typo that prevented test_fixed_size_error from passing (From OE-Core rev: 897aaff8961f7fe83634a3b0b94e19b43aea5857) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie (cherry picked from commit 467f84e12b96bc977d57575023517dd6f8ef7f29) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

scripts/oe-build-perf-report: Use python3 from the environment

2020-09-23T11:47:59+00:00

This means ot matches the rest of the system rather than causing confusing errors where multiple python versions are mixed. (From OE-Core rev: 95d5005828b0d32d610874986fcc298b12347079) Signed-off-by: Richard Purdie

oe-publish-sdk: fix layers init via ssh

2020-09-17T11:51:24+00:00

Escaping does not work in my use case. It must be escaped for python, ssh and shell as well as for different versions of echo. Let's try it a little less elegant, but hopefully more reliable. (From OE-Core rev: cdbc9bf63b3e1354800032d0dd530949bafb7032) Signed-off-by: Adrian Freihofer Signed-off-by: Richard Purdie (cherry picked from commit 5cc1ae332eb6b05d83802c8d64ab2767c7079412) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

runqemu: Add a hook to allow it to renice

2020-09-17T11:51:24+00:00

We have an issue where qemu is being starved of resources on our autobuilders. We can't raise its priority without special capacilties, therefore add a hook which if present can allow this to happen using an executable "~/runqemu-renice". (From OE-Core rev: 829443b3fafa000e330c06ebb144641bd2d20ad1) Signed-off-by: Richard Purdie (cherry picked from commit 141a3c9ce93bc3d526303021ecf0460c6e9fea8a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie