Busybox' tc network utility does not compile currently on systems
with kernel >6.8..
Therefore, disable this configuration item as workaround.
Fix#5536
When `intl/plural.y` gets re-build, because its timestamp is newer than
`int/plural.c` when checking out the sources, it happens that the `bison`
host tool might be too new to build this target, leading to compile errors.
We don't need to re-compile that grammar file anyway.
Fix#5535
This patch equips fs_query to deliver a quick overview of the reported
<dir> nodes as counts of directories, files, and symlinks. The feature
can be activated by the new the <query> node attribute 'count="yes"'.
Issue #5534
When `_fb_name()` changes, the connectors Rom_handler must be
reconstructed because the session label changed. This may occur when
booting with `intel_gpu="no"` to force the Sculpt manager to use
vesa_fb: Prior to loading its config, the manager already creates a ROM
connection to intel_fb's connectors ROM.
Issue #5501
This patch changes the access pattern to faclilitate the write-combining
buffer (dst) instread on the cached src data for rotated back2front
blitting.
Issue #5428
This commit limits the support to the formats that are in active
use at the moment:
* tar and raw are required for Sculpt (archives and index)
* zip is used by Genodians
Instructing libarchive to use all supported formats can lead to
unexpected results when the probing mechanism identifies the
wrong format. For example, an empty index file ('<index> </index>')
will be classified as MTREE format.
Fixes#5528.
to reduce overhead going several times over the same cpu array. First
detect the min/max range of Package, Core and Thread and use it. Stop iterating
if supported count of CPUs are reached.
Issue #5524
Since the introduction of the "menu_hover" report, keep alive
information of the Leitzentrale is lost (e.g., dialing pad, activity in
main menu, ...) leading to premature screensaver activation. With this
commit we add support to monitor the "menu_hover" report's sequence
numbers through Watch_rom_seq_number, and thus, avoid triggering the
screensaver even though activity has been performed.
issue #5496
This facilitates the use of SIMD-optimized back2front blitting. Thanks
to the capture viewport, the optimization can be used for arbitrary
window sizes.
Issue #5518
This patch adds the support for a client-specified buffer viewport to
nitpicker. It thereby allows clients to allocate a buffer that is larger
than the visible pixels, in particular, padding the buffer dimensions to
SIMD-friendly boundaries.
Issue #5518
in the same format as the intel/display driver. With this commit vesa_fb
can be configured and used by the sculpt_manager similar to the intel/display
in Sculpt OS.
Issue #5501
Update the popup view whenever a runtime-state change is detected.
Otherwise the toggling of an item in the options tab is not always
reflected at the dialog. Observed when running Sculpt on Linux.
This change prevents the reporting of amibiguous hovering information in
the presence of multiple dialogs by reporting only the hovering
information of the dialog that observed the most recent hover change.
Issue #5496
Issue #5485
By using the clicked report instead of the hover report, we prevent the
misinterpretation of a regular hover update as an overly delayed hover
report matching a previous click (inside the popup). With this patch, the
popup stays open when the pointer leaves the popup after the click.
Issue #5496
Issue #5485
This patch separates the handling of touch input from pointer input in
the logic of closing the popup dialog. For the detection of a touch
outside the popup dialog, nitpicker's new "touch" report is observed
whereas the detection of a click outside the popup is based on
nitpicker's hover report.
Issue #5496
Issue #5485
This patch decouples nitpicker's handling of touch events from the
handling of pointer devices.
The mouse pointer is no longer following touch position but stays
independent.
The existing "hover" report has now a counterpart "touch" that reports
the most recently touched session, including the initial touch point
and last observed sequence number.
Issue #5496
Issue #5485
On the unexpected occasion of an invalidation-queue error, the
invalidator gets stuck in an infinite loop. We therefore need to check
for and recover from invalidation-queue errors while waiting.
genodelabs/genode#5523
Each new entry in the invalidation queue must be zeroed before writing
in order to clear data from old entries. Not doing this can cause
invalidation queue errors after the tail pointer wrapped around.
genodelabs/genode#5501genodelabs/genode#5523
Report 'display_driver_ready' to screensaver depending if <capture> node
is present in Gui::info. The Gui::panorama call does not suffice because
it reports the dimensions of the very last Capture client closed as
fallback.
issue #5496
On some platforms late_ram_regions are initialized to zero which
leads bootstrap to insert zero based/sized ram regions wich later caused
the following warning in core:
! unable to register RAM region base=0x0 size=0x0
! unable to exclude I/O range from RAM: base=0x0 size=0x0
Therefore, omitt adding zero sized regions to the boot info.
issue #5496
In case a play-session client sends data too slow leading to
record-session client depletion after 250ms of inactivity, try to wakeup
depleted clients upon reception of fresh audio data from the
play-session. The _scheduler.consecutive check for triggering a wakeup
doesn't seem to suffice in case of occasionally slow play clients.
(This fixes the osci preset on the PinePhone)
issue #5496
* ignore sequence numbers from nitpicker in _handle_input because it
generates it's own numbers
* send sequence number on single click
issue #5496
issue #5491
Since "wm/decorator/layouter: window clipping" we need to separate
resize and window-layout ROMs while also adding the <boundary> nodes for
wm/decorator/layouter to function correctly.
issue #5496
