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
This commit removes the aged Block::Driver interface that has already
been superseded by the Block::Request_stream API for some time now.
It is solely used by components whose existence is made redundant,
like 'lx_block', or old drivers, like the SD-Card driver for PL180
and old i.MX53/6 systems or the RPi 1, that have not seen active use
other than in the nightly CI runs.
Fixes#5522.
The 'lx_block' component uses the aged Block::Driver framework
internally and most if not all use-cases where it could be employed
can be addressed by using the 'vfs_block' component instead.
This commit also removes some run-scripts that make use of 'lx_block'
whose components are already excercised otherwise.
Issue #5522.
Extend the remote cpu call to destroy a thread to be able to
destroy a vcpu as well. Change the vcpu_destroy syscall to
remotely destroy it when the scheduler of the other core has
chosen it at that same point in time.
Fix#5511
Eliminate the assertion as it lets the kernel stall by any smp component
that calls thread's pause syscall, as long as the GENODE_RELEASE flag
isn't set.
Fix#5510
* Remove afiinity artefact from Cpu class
* Scheduler::need_to_schedule => Scheduler::ned_to_update (consistency)
* Don't re-use last scheduler context after new scheduling
decision, might have been deleted (potential use-after-free)
* Move Timer::process_update into timer's interrupt handling routine
* Move execution time of Cpu_context into Scheduler::Context
* Re-order scheduler and idle context initialization (ref before initialized)
Ref #5509
When invoking mkimage with '-f auto' the tool uses heuristics to
decide what kind of image to produce. It seems to be related to
the version of mkimage and/or its input data, whether this decision
is done right. Therefore, clearly state the target architecture.
Fix#5519
Solely consider sessions with valid bounding boxes for the decision
to use the fallback bounding box or not. New started capture clients may
require some time between capture session creation and actually capture
screen creation at which the bounding box becomes valid.
Issue #5521
By giving the client a way to specify the origin of the viewport in
addition to the size, we can solve transformed (rotated, flipped)
output to screen buffers where the line length is larger than the
number of visible pixels.
Issue #5518
