Updating to the latest korg -stable release that comprises
the following commits:
d235c2b1f470 Linux 5.19.16
279116cb0bc5 misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic
d472808756b3 misc: pci_endpoint_test: Aggregate params checking for xfer
d0ecbd70f080 Input: xpad - fix wireless 360 controller breaking after suspend
d1a1dbe71f73 Input: xpad - add supported devices as contributed on github
ac719db96b23 mctp: prevent double key removal and unref
3aecb0895aac wifi: cfg80211: update hidden BSSes to avoid WARN_ON
fa63b5f6f885 wifi: mac80211: fix crash in beacon protection for P2P-device
2bee6f75e3c6 wifi: mac80211_hwsim: avoid mac80211 warning on bad rate
1d73c990e9ba wifi: cfg80211: avoid nontransmitted BSS list corruption
46b23a955958 wifi: cfg80211: fix BSS refcounting bugs
867184200c05 wifi: cfg80211: ensure length byte is present before access
e6d77ac0132d wifi: mac80211: fix MBSSID parsing use-after-free
74abb1952a03 wifi: cfg80211/mac80211: reject bad MBSSID elements
42ea11a81ac8 wifi: cfg80211: fix u8 overflow in cfg80211_update_notlisted_nontrans()
848bb8517e41 random: use expired timer rather than wq for mixing fast pool
111824744645 random: avoid reading two cache lines on irq randomness
ee42204c1cd5 Revert "crypto: qat - reduce size of mapped region"
3a8f93f3779e Revert "powerpc/rtas: Implement reentrant rtas call"
bd9c917efcf8 Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"
d42228fc2cad Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> peripheral if extcon is present""
5857b9cd9b91 USB: serial: qcserial: add new usb-id for Dell branded EM7455
6ae8aa5dcf0d scsi: stex: Properly zero out the passthrough command structure
55e19a4c111e efi: Correct Macmini DMI match in uefi cert quirk
a0d53923bf91 ALSA: hda/realtek: Add quirk for HP Zbook Firefly 14 G9 model
59ac9fa0e33f ALSA: hda: Fix position reporting on Poulsbo
b42a64428abe random: clamp credited irq bits to maximum mixed
e1f8820bf83f random: restore O_NONBLOCK support
ae2e80078145 nvme-pci: set min_align_mask before calculating max_hw_sectors
6c58865f1acd ceph: don't truncate file in atomic_open
090fcfb6edeb nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
4755fcd84424 nilfs2: fix leak of nilfs_root in case of writer thread creation failure
394b2571e9a7 nilfs2: fix use-after-free bug of struct nilfs_root
caf2c6b58043 nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
51dd976781da Linux 5.19.15
04bd2a779511 Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
c4635cf3d845 Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
6954cee88268 bpf: Fix resetting logic for unreferenced kptrs
292b46c49675 net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
9783292253fd bpf: Gate dynptr API behind CAP_BPF
7d3f5d0353b4 rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
165ae42fc1cf mmc: core: Terminate infinite loop in SD-UHS voltage switch
b2afdaddaa8c mmc: core: Replace with already defined values for readability
0b0f40745ab4 gpiolib: acpi: Add a quirk for Asus UM325UAZ
aa476c7b6375 gpiolib: acpi: Add support to ignore programming an interrupt
a9d2ce58126c USB: serial: ftdi_sio: fix 300 bps rate for SIO
9de74019cd44 usb: mon: make mmapped memory read only
c2423912d5c9 i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe
71c41e04d9d8 don't use __kernel_write() on kmap_local_page()
5dac20360a7b perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
3682460b9327 drm/amd/display: increase dcn315 pstate change latency
94d49c380b9a drm/amd/display: Fix DP MST timeslot issue when fallback happened
4fb0b18590c6 drm/amd/display: skip audio setup when audio stream is enabled
3c15b295ae2f drm/amd/display: update gamut remap if plane has changed
89d387065803 drm/amd/display: Assume an LTTPR is always present on fixed_vs links
d1137c3c03d8 drm/amd/display: Fix double cursor on non-video RGB MPO
32c1dde16f0a KVM: s390: Pass initialized arg even if unused
5b4e1c1ffba3 net: atlantic: fix potential memory leak in aq_ndev_close()
cfaf7f090a40 arch: um: Mark the stack non-executable to fix a binutils warning
a460f846d580 gpio: ftgpio010: Make irqchip immutable
d71f03dbcc17 um: Cleanup compiler warning in arch/x86/um/tls_32.c
c7105d2a77a6 um: Cleanup syscall_handler_t cast in syscalls_32.h
9cdbc61abaa0 ALSA: hda/hdmi: Fix the converter reuse for the silent stream
7480deff597a net: marvell: prestera: add support for for Aldrin2
be248292a483 net/ieee802154: fix uninit value bug in dgram_sendmsg
ce57f7b2e614 scsi: qedf: Fix a UAF bug in __qedf_probe()
5f2f00509496 drm/amdgpu/mes: zero the sdma_hqd_mask of 2nd SDMA engine for SDMA 6.0.1
f8895cfb48b0 ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
7e834ee927a5 wifi: iwlwifi: don't spam logs with NSS>2 messages
229769759ef8 dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API failure
e38f67582567 dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
92f8963831f1 dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
666f5be3593c arm64: dts: rockchip: fix upper usb port on BPI-R2-Pro
edc5c66d15f9 firmware: arm_scmi: Add SCMI PM driver remove routine
8e880f30946f firmware: arm_scmi: Harden accesses to the sensor domains
41bf1b0ad953 firmware: arm_scmi: Improve checks in the info_get operations
81de80330fa6 fs: fix UAF/GPF bug in nilfs_mdt_destroy
8529dfb5ef72 xsk: Inherit need_wakeup flag for shared sockets
7ebe331054cf docs: update mediator information in CoC docs
3b760c94de19 hardening: Remove Clang's enable flag for -ftrivial-auto-var-init=zero
19a4cb1c4eb8 Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
8dc610c9478c sparc: Unbreak the build
(From OE-Core rev: a99d8002ff7b8f4d73d03abd75a05921d0587815)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Introducing the 6.0+ development kernel branches. These
have been sanity tested on all supported architectures.
(From OE-Core rev: 04c9125197783b0c72552b213c8a248eedc83a93)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
liburi-perl in oe-core now RDEPENDS on libtest-warnings-perl for ptest
* Update HOMEPAGE; fix syntax
* Add SUMMARY
* Add BUGTRACKER
* Use CPAN_MIRROR for SRC_URI
* Use actual LICENCE file for LIC_FILES_CHKSUM
* Add RDEPENDS
* Add RDEPENDS on perl-modules for ptest
- Too many hidden dependencies that fail silently, but pass
with full perl-modules
* Add self as maintainer
* Add to ptest-packagelists (fast)
(From OE-Core rev: b1582fb0ec6620312b9a26c6afc48a63984617a0)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, dhcpcd does not work well with systemd. When using dhcpcd
to configure network, the /etc/resolv.conf contents are not correct.
This issue could easily be reproduced by using 'qemu + slirp' to
start a systemd based image and using dhcpcd to configure network.
The expected 'nameserver 10.0.2.3' is not in /etc/resolv.conf.
The root cause of this problem is that dhcpcd assumes the resolvconf
should recognize .protocol suffix[1]. But systemd's resolvconf (which
is a symlink to resolvectl) has a limited support for traditional
resolvconf interface[2], and "may not work with all clients"[3]. This
of cource includes the clients that use the .protocol suffix.
The current situation is:
1. systemd is not going to support the .protocol suffix in the foreseeable
near future[4].
2. dhcpcd does not want to merge systemd specific patch and insists
systemd needs to consider the .protocol suffix[5][6].
It's a normal thing that people have different opinions. As a build system
that supports such combination, however, we do need to come up with a
solution to fix this typical integration problem, making dhcpcd and systemd
work together.
This patch solves this integration problem by relying on dhcpcd's ability
to manage its own resolv.conf contents. But instead of letting it to write
to /etc/resolv.conf directly, we supply the generated contents to resolvconf.
In this way, the resolvconf still stands in the central place and dhcpcd remains
a supplier to it. And the /etc/resolv.conf can get the correct contents.
With this patch, dhcpcd could work with both sysvinit and systemd.
[1] https://man.archlinux.org/man/resolvconf.8.en
[2] https://man.archlinux.org/man/resolvectl.1#COMPATIBILITY_WITH_RESOLVCONF(8)
[3] https://wiki.archlinux.org/title/systemd-resolved
[4] https://github.com/systemd/systemd/issues/25032
[5] https://github.com/NetworkConfiguration/dhcpcd/pull/152
[6] https://github.com/NetworkConfiguration/dhcpcd/issues/146
(From OE-Core rev: 935ae419f51d911c73f5dc7b4a2e5e9a7b206985)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Qemurunner should not pass rootfs to runqemu in case
rootfs is not a filesystem itself. Some images could
be built into some disk format like vmdk and this
commit makes qemurunner handle such images properly.
(From OE-Core rev: 5aea74046cf4c1aa7fa9e2402788d662268ccf53)
Signed-off-by: Sergei Zhmylev <s.zhmylev@yadro.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't test not using the cache and I'm not aware of anyone using this, it
would be hard to with modern bitbake.
Drop the conditional code and simply error if CACHE isn't set.
(Bitbake rev: 063ffe699bc5fc23174643dfedb66864cacfcff8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When setting up the worker we were transfering large amounts of data
which aren't needed until task execution time.
Defer the fakeroot and taskdeps data until they're needed for a specific
task. This will duplicate some information when executing different tasks
for a given recipe but as is is spread over the build run, it shouldn't
be an issue overall.
Also take the opportunity to clean up the silly length argument lists
that were being passed around at the expense of extra dictionary keys.
(Bitbake rev: 3a82acdcf40bdccd933c4dcef3d7e480f0d7ad3a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The previous cleanups meant that when the cooker was started, profiling
was always disabled as configuration was sent to the server later and this
was too late to profile the main loop.
Pass the "profile" option over the server commandline so that we can
profile cooker itself again, the setting can now take effect early enough.
(Bitbake rev: c97c1f1c127ef3f8fbbd1b4e187ab58bfb0a73e5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
At this point users appear to all call add_info directly. Failing
to do that means the file dependency tracking code isn't active
so would cause problems. Therefore drop the unused function.
(Bitbake rev: 6b24efc0f4d19738d96754280e70bc493005167d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some parts of functions in Cache() were broken and unused, there was
also a totally unused function. This was historical as a result of the
cooker parsing process needing to handle cached entries in the main
thread but parsing actions in seperate processes.
Document the way it works, update the function name to be clear about
what it now does and drop the old code which was unused.
(Bitbake rev: af83ee32df85c8e4144f022a1f58493eb72cb18e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When 'NoCache' was written, databuilder/cookerdata didn't exist. It does
now and the recipe parsing functionality contained in NoCache clearly
belongs there, it isn't a cache function. Move those functions, renaming
to match the style in databuilder but otherwise not changing functionality
for now. Fix up the callers to match (which make it clear this is the right
move).
(Bitbake rev: 783879319c6a4cf3639fcbf763b964e42f602eca)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Both atk and at-spi2-atk are now merged into this project.
- drop atk_2.38.0.bb
- drop at-spi2-atk_2.38.0.bb
- PROVIDES += "atk at-spi2-atk"
- RPROVIDES:${PN} += "atk at-spi2-atk"
* DEPENDS on libxml2
* Ships:
${libdir}/gnome-settings-daemon-3.0/gtk-modules/at-spi2-atk.desktop
${libdir}/gtk-2.0/modules/libatk-bridge.so
What's new in at-spi2-core 2.46.0:
* Fix GetInterfaces documentation on org.a11y.atspi.Accessible
interface.
What's new in at-spi2-core 2.45.91:
* Send device event controller events using the same signature as other
events.
* Document the Accessible, Action, and Cache dbus interfaces.
* Fix license of atspi-gmain.c (#87).
What's new in at-spi2-core 2.45.90:
* xml: Add some documentation.
* xml: Fix event arguments.
* xml: Add some missing DeviceEventController methods.
* Bind the AT-SPI bus to the graphical session.
* Mark bus service as belonging to the session slice.
* Add ATSPI_ROLE_PUSH_BUTTON_MENU.
* Add an "announcement" event/signal to allow objects to send
notifications (!63).
* Various code clean-ups and test improvements.
What's new in at-spi2-core 2.45.1:
* Atk and at-spi2-atk are now merged into this project.
* Now requires meson 0.56.2 and glib 2.67.4.
* at-spi2-atk: Expose the accessible hierarchy via dbus introspection.
* Properly escape the AT-SPI bus address; fixes warnings about the
address not containing a colon (!55).
* Add a text value to AtspiValue, so that a value can expose a textual
description, as in the new Atk value API.
* Add atspi_event_listener_register_with_app, to allow an event listener
to be registered only for a given application (!52).
https://gitlab.gnome.org/GNOME/at-spi2-core/-/blob/main/NEWS
(From OE-Core rev: ad605662f1bc1a0d446f59362aedb74d22d12980)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The prepended code with the i and j variables clash with similar code in uboot.inc, so they need to be unset once we are done using them.
This commit fixes the issue that was introduced in d6858c9 "u-boot: Rework signing to remove interdependencies".
(From OE-Core rev: 6f668f85d7e5b0a9d36198db865cf1e1a012b2e1)
Signed-off-by: David Bagonyi <david.bagonyi@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current resolvconf does not work. Make it work with the
following changes.
1. Install normalize-resolvconf, which is used by resolvconf.
2. Add dependencies: sed, util-linux-flock.
util-linux-flock is needed by our busybox does not support '-w'
by default. sed is needed because we want to avoid package
QA issue complaining sed is needed by no one provides it.
3. Add a patch to replace 'readlink -m' with 'readlink -l'.
This could avoid the runtime dependency on coreutils. The replacement
is safe as /etc always exits in OE's system.
4. Remove allarch inheritage. This is because the above RDEPENDS
change does not allow this any more. test_sstate_allarch_samesigs
would fail if we don't do this.
(From OE-Core rev: 1b0581fd241cc9de2feda896aefbf055dc0099dc)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, the KERNEL_DEBUG_TIMESTAMPS is not working as expected
at rebuild. That is, even if we set it to "1", the kernel build time
is not changed. The problem could be reproduced by the following steps.
1. bitbake core-image-minimal; start image and check `uname -a` output.
2. set in local.conf: KERNEL_DEBUG_TIMESTAMPS = "1"
3. bitbake core-image-minimal; start image and check `uname -a` output.
It's expected that after enabling KERNEL_DEBUG_TIMESTAMPS, the kernel
build time will be set to current date. But it's not. This is because
the compile.h was not re-generated when do_compile task was re-executed.
In mkcompile_h, we have:
"""
# Only replace the real compile.h if the new one is different,
# in order to preserve the timestamp and avoid unnecessary
# recompilations.
# We don't consider the file changed if only the date/time changed,
# unless KBUILD_BUILD_TIMESTAMP was explicitly set (e.g. for
# reproducible builds with that value referring to a commit timestamp).
# A kernel config change will increase the generation number, thus
# causing compile.h to be updated (including date/time) due to the
# changed comment in the
# first line.
"""
It has made it very clear that it will not be re-generated unless
we have KBUILD_BUILD_TIMESTAMP set explicitly. So we set this variable
explicitly in do_compile to fix this issue.
(From OE-Core rev: 1b68c2d2d385013a1c535ef81172494302a36d74)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The previous version of this wasn't correctly passing the program name
as argv[0], and was also over-complicated anyway because argv[] is
guaranteed to be terminated with a NULL pointer, so it can be passed
directly to the execv'd process without needing to be copied.
(From OE-Core rev: 6edf38add3c20c44efe0588e2815bb280d22e0c4)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since oe-core commit 64b89f3c8fc31842256c482a3039d90d3f12c1cc
("sstatesig.py: make it fatal error when sstate manifest isn't found")
errors like:
| Manifest [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot not found in imx8mm_dummy cortexa53-mx8mm cortexa53 armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant '')?
are fatal now and cannot be ignored but must be debugged.
Unfortunately, the currently emitted error message is a bit imprecise
with telling the reader what has actually gone wrong.
This commit:
* adds the word 'sstate' to the error message to clarify the scope we
are dealing with ('sstate manifests', since there are other manifests,
too)
* does not randomly print the last manifest file searched for as THE
manifest file that could not be found
Instead, we print the name of the task the sstate was searched for
* adds the word 'multilib' to variant to make clear which variant we are
talking about
* adds a separate line noting the searched pkgarchs and adds explicitly
mentions this word ('pkgarchs')
* prints a list of ALL manifest file locations attempted
* removes the '?' at the end of the message since such errors indeed
leave the question of what is the cause but the error message itself
is more like a statement.
The result for the exact same issue as noted above then looks as
follows:
| The sstate manifest for task 'dbus:populate_sysroot' (multilib variant '') could not be found.
| The pkgarchs considered were: imx8mm_dummy, cortexa53-mx8mm, cortexa53, armv8a-crc, armv8a, aarch64, allarch, x86_64_x86_64-nativesdk.
| But none of these manifests exists:
| [..]/tmp/sstate-control/manifest-imx8mm_dummy-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-cortexa53-mx8mm-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-cortexa53-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-armv8a-crc-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-armv8a-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-aarch64-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-allarch-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot
(From OE-Core rev: 735ec126ec219c7cb89cb05b0e433201bb7f59eb)
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
============
* Add notes to libpipeline(3) of when functions were added.
* Transferred Git repository to https://gitlab.com/libpipeline/libpipeline.
* Make `socketpair` tests used by `./configure --enable-socketpair-pipe`
compatible with C23.
(From OE-Core rev: a2369129b5abe9a12a25f120ce1438eb6fff39ae)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
* send: minor speed up for v2 due to increased buffer size
* resize: invalid command line options fail with error code
* quota rescan:
* add long options --status and --wait
* new option to wait but don't start rescan
* qgroup show: print path by default, updated format
* qgroup: new subcommand clear-stale, remove qgroups without their subvolumes
* experimental:
* add warnings to commands that have it enabled (mkfs, image, btrfstune)
* other:
* documentation, help text, error message updates
(From OE-Core rev: b638d61ccc9596b4c432792d3e3a45b989937144)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6.57.1 - 2022-11-14
This patch updates some internal type annotations and fixes a formatting bug
in the explain phase reporting.
6.57.0 - 2022-11-14
Hypothesis now raises an error if you passed a strategy as the alphabet=
argument to text(), and it generated something which was not a length-one
string. This has never been supported, we’re just adding explicit validation
to catch cases like this StackOverflow question.
https://hypothesis.readthedocs.io/en/latest/changes.html#v6-57-1
(From OE-Core rev: 8a4a1fbc7c882a5768d9d5c48edcd92867f7fab4)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With default slirp port forwarding config qemu listens on TCP ports
2222 and 2323 on all IP addresses available on the build host. Most
use cases with runqemu only need it for localhost and it is not
safe to run qemu images with root login without password enabled
and listening on all available, possibly Internet reachable network
interfaces. Limit qemu port forwarding to localhost 127.0.0.1 IP
address. Now qemu machine SSH and telnet ports are only
reachable from the build host machine, not full Internet.
If qemu machine needs to be reachable from network, then it can
be enabled via local.conf or machine config variable QB_SLIRP_OPT:
QB_SLIRP_OPT = "-netdev user,id=net0,hostfwd=tcp::2222-:22"
(From OE-Core rev: c6b1e3d50bf2feea80b70a42c6fad868fa9e6042)
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default host side IP address is not set and qemu listens
on all IP addresses on the host machine which is not a good
idea when images have root login enabled without password.
It make sense to listen only on localhost IP address 127.0.0.1 using
config change like:
QB_SLIRP_OPT = "-netdev user,id=net0,hostfwd=tcp:127.0.0.1:2222-:22"
This config works for qemu itself, but breaks runqemu which tries to
parse the host side port number from qemu process command line arguments.
So change the runqemu side hostfwd parsing for port number to ignore
the host IP address field.
Reviewed-by: Quentin Schulz <foss+yocto@0leil.net>
(From OE-Core rev: bdbd52082eb26f418000eb4e424baae9babc272c)
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sadly the magic is not perfect: llvm-config contains a hardcoded
value for the libdir from the native configuration, and things will
break if the target build installs libraries somewhere else (e.g. lib64).
llvm-config in target bindir also needs a rpath adjustment,
otherwise it simply won't even run when e.g. building for arm on x86.
To avoid patching llvm-source let's simply add more cases to the
llvm-config wrapper script, so that falling through to llvm-config binary
is avoided. Fortunately those cases are all static in what they return,
even though llvm-config binary does poke around the file tree to arrive
at them (which is where breakage happens if native and target don't match
exactly wrt libdir).
I verified that this works by building mesa with llvm enabled for
qemuarm64 and with baselib set to 'lib64' - so that both the target
architecture and target libdir differ from native ones.
Upstream tickets:
https://github.com/llvm/llvm-project/issues/58984https://github.com/mesonbuild/meson/issues/11043
(From OE-Core rev: 056431883e94296b767a479d029b914392e4fd7c)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
* Various HTTP/2 Fixes:
* Fix `content-sniffed` not being emitted for resources without content
* Fix leak of SoupServerConnection when stolen
(From OE-Core rev: 65d287feb713a21cefdf4cb56f80c9f1deaa2e60)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
=========
- ISO 3166-1: Update name for TR. Fixes#38
- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-2. Closes: #1020633
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924
(From OE-Core rev: 99917b4b7d5642b292cb95c770871b95e411dfc5)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
From NEWS for v236:
* The "uaccess" udev tag has been dropped from /dev/kvm and
/dev/dri/renderD*. These devices now have the 0666 permissions by
default (but this may be changed at build-time). /dev/dri/renderD*
will now be owned by the "render" group along with /dev/kfd.
Without the group systemd-udevd startup logs:
/lib/udev/rules.d/50-udev-default.rules:39 Unknown group 'render', ignoring
/lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring
(From OE-Core rev: 84efd72d48616405dbe4d73ec95917077144ed09)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After updating gen_fixtures.py, run ./gen_fixtures.py --all
This includes the latest stable/supported releases.
Currently excludes 'dunfell' as it seems to crash.
(Bitbake rev: 58e29fb15cd65795d6cf65a4db2b87f34649cb1f)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop Honister and Hardknott as they are both EOL
Add Langdale as it is the latest stable release
Add comment about Dunfell (currently crashing)
(Bitbake rev: e060daae28529c25968cacc5536a1034e1e1c030)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We should reference the docs for the current LTS version we are using.
(Bitbake rev: 0dca22a184240d464bbd4ef276a6b13e44e29725)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Just like download_submodule() does, fixed warings when run
bb.fetch2.Fetch([url], d) in process_submodules' function:
WARNING: grpc-native-1.50.0-r0 do_fetch: URL: gitsm://github.com/abseil/abseil-cpp.git;protocol=https;name=third_party/abseil-cpp;subpath=third_party/abseil-cpp does not set any branch parameter. The future default branch used by tools and repositories is uncertain and we will therefore soon require this is set in all git urls.
(Bitbake rev: 0ed7c75eb0508a1f699f47d7f22d559501865f61)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit 0361ecf7eb82c386a9842cf1f3cb706c0a112e77 introduced regression
in submodules path parsing. As the result gitsm fetcher fails on each
submodule which name begins from the name of the parent repo which is
totally valid usecase [Yocto #14045] [1]
Fix the code to error out only if submodule's name is equal to parent
name but not if it's part of it.
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=14045#c4
(Bitbake rev: 3ad27272c18f2bb9edd441f840167a3dabd5407b)
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
