waybeam: bump to the CV610 parity merge, and ship libbin.so - #6
Merged
Merged
Conversation
WAYBEAM_VERSION moves to 0c660fc5 (OpenIPC/waybeam#120), which brings the CV610 backend to parity: RTP sidecar, sensor orientation, ROI, live output retarget, portable AE ceilings, and PQTools .bin import/export. The .bin features dlopen libbin.so, and nothing put it on the craft -- so every image needed a manual scp or isp.sensorBin and /api/v1/iq/export_bin silently no-opped. The blob is carried in files/ and fed to waybeam's own stage step via CV610_PQ_LIB, so there is one source of truth for the file and the install comes from the staged output like every other artifact. WAYBEAM_LICENSE names it. The waybeam sources are MIT; libbin.so is a third-party HiSilicon PQ library redistributed unmodified, and is neither ours nor MIT. Declaring plain MIT would have quietly extended that licence over a proprietary blob. Also installs iq-profiles/cv610-bin/imx662.bin to /etc/sensors/ as an IQ restore point. Deliberately NOT named by the default config: importing a tune at boot is opt-in, and this one only reproduces the sensor plugin's own cold-boot state. A craft without the blob still boots -- the import warns and no-ops, and since 0.81.0 it also advertises neither isp.sensorBin nor routes.iq_export_bin, so the control surface matches what it can serve. Verified on a CV610 bench by moving the library aside. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GwG8Jmv3daUQgZhMYyz3wB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
WAYBEAM_VERSIONto0c660fc5(OpenIPC/waybeam#120), which brings the CV610 backend to parity: RTP sidecar, sensor orientation, ROI, live output retarget, portable AE ceilings, and PQTools.binimport/export.Why libbin.so is here
The
.binfeaturesdlopen("libbin.so"), and nothing put it on the craft — so every image needed a manualscp, orisp.sensorBinand/api/v1/iq/export_binsilently no-opped.The blob is carried in
files/and fed to waybeam's own stage step viaCV610_PQ_LIB, so there is one source of truth for the file and the install comes from the staged output like every other artifact.WAYBEAM_LICENSEnames it. The waybeam sources are MIT;libbin.sois a third-party HiSilicon PQ library redistributed unmodified, and is neither ours nor MIT. Declaring plain MIT would have quietly extended that licence over a proprietary blob.Also installed
iq-profiles/cv610-bin/imx662.bin→/etc/sensors/imx662.bin, as an IQ restore point. Deliberately not named by the default config: importing a tune at boot is opt-in, and this one only reproduces the sensor plugin's own cold-boot state.Degradation without the blob
A craft without
libbin.sostill boots — the import warns and no-ops, and since waybeam 0.81.0 it also advertises neitherisp.sensorBinnorroutes.iq_export_bin, so the control surface matches what it can actually serve. Verified on a CV610 bench by moving the library aside: both capability signals went false, the endpoint 501'd, and the craft streamed normally.🤖 Generated with Claude Code
https://claude.ai/code/session_01GwG8Jmv3daUQgZhMYyz3wB