daedalus-v4l2 + daedalus-v4l2-dkms: bump to 872eec5 — PROTO_MAX_PAYLOAD 1 MiB (#20) #89
Reference in New Issue
Block a user
Delete Branch "claude-noether/marfrit-packages:noether/daedalus-bump-872eec5-1mib-payload"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Picks up reauktion/daedalus-v4l2 PR #20 (closes #19): wire-protocol cap
DAEDALUS_PROTO_MAX_PAYLOADraised from 64 KiB to 1 MiB.DAEDALUS_MAX_BITSTREAMfollows;daedalus_fill_output_fmtnow reports OUTPUT_MPLANEsizeimage = ~1 MiB.Bug fixed
Firefox YouTube
avc1SW-fallback observed on higgs when any H.264 slice exceeded 64 KiB (routine on 720p+ streams). libva-v4l2-request-fourier's S_FMT-driven OUTPUT-pool resize was clamping back to 65484 and Firefox lost the slice:What
Both packages bumped to 0.1.0+r45+g872eec5-1:
daedalus-v4l2(daemon): r43 → r45. Daemon-side allocations are dynamic, so the only growth is one ~1 MiB read buffer per daemon process at startup.daedalus-v4l2-dkms(kernel module): r33 → r45. Skips the daemon-only bumps r37/r39/r41/r43 (nokernel/orinclude/change in that range) and lands the PROTO_MAX_PAYLOAD bump.⚠ Lock-step install
Effective wire cap is
min(kernel, daemon). A stale kernel with a new daemon (or vice versa) still rejects >64 KiB payloads. apt / pacman should pick both up in one transaction since they share the same upstream pin and the changelog warns explicitly.Wire protocol
Value-only change in
include/daedalus_v4l2_proto.h; struct layout unchanged.DAEDALUS_PROTO_VERSIONstays at 0.Verify post-merge
Then open YouTube avc1 720p in Firefox; confirm no
kernel returned sizeimage 65484in libva trace and continuousdecoder: OKlines in the daemon journal across pause/resume cycles.Refs