#12613: app_server handles overlay hooks incorrectly.
----------------------------------+-----------------------------
Reporter: rudolfc | Owner: axeld
Type: bug | Status: in-progress
Priority: normal | Milestone: Unscheduled
Component: Servers/app_server | Version: R1/Development
Resolution: | Keywords: overlay setmode
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------------+-----------------------------
Comment (by rudolfc):
Oh,
from the via.acccelerant.0.log after a system start:
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_OVERLAY_COUNT.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_OVERLAY_SUPPORTED_SPACES.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_OVERLAY_SUPPORTED_FEATURES.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_ALLOCATE_OVERLAY_BUFFER.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_RELEASE_OVERLAY_BUFFER.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_GET_OVERLAY_CONSTRAINTS.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_ALLOCATE_OVERLAY.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_RELEASE_OVERLAY.
Overlay: Invalid colour depth 0x00000000
Overlay: Not exporting hook B_CONFIGURE_OVERLAY.
SETMODE: (ENTER) initial modeflags: $8000001f
SETMODE: requested target pixelclock 64996kHz
SETMODE: requested virtual_width 1024, virtual_height 768
This setmode command at the end is the first mode set by the app_server
using the driver. After this particular boot I could start VLC 0.86D and
enjoy overlay..
Of course I could prevent that by just extra blocking the overlay
functions if not officially 'released', but these should not have been
called in the first place.
Rudolf.
--
Ticket URL: <https://dev.haiku-os.org/ticket/12613#comment:7>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
