Skip to content

tools: add bounded SP11 research parsers and historical validation notes - #74

Merged
ooaklee merged 17 commits into
sp11/ubuntu-qcom-x1e-7.3.yfrom
x/sp11-windows-driver-parity-20261015
Nov 10, 2026
Merged

ooaklee merged 17 commits into
sp11/ubuntu-qcom-x1e-7.3.yfrom
x/sp11-windows-driver-parity-20261015

Conversation

@ooaklee

@ooaklee ooaklee commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Import the bounded SP11 driver-research parsers and their historical validation notes onto sp11/ubuntu-qcom-x1e-7.3.y.

This port contains tools and documentation only. The overlapping OV13858 driver and binding foundation is carried solely by camera PR #73. No kernel runtime source, board activation, firmware payload, package, or installation is changed here.

The 16 original tools/documentation commits retain their authors, dates and messages. Their 20 file postimages were checked against the original head before adding the current-scope README notice and the fork-only test workflow. The original 7.2 carrier remains preserved at archive/pr74-pre-7.3-20261110, commit a103bf0c07a92b7a16ff43e8f8cf6e0fec879391.

Validation at 67d009fac1c15cb1806c693a5be555d119595780:

  • All 61 existing tests pass natively under Node 25.9 and in an isolated Linux Node 22 container.
  • The parsers cover malformed input, aggregate bounds, duplicate values and command-line failure/read-only behavior.
  • The committed-range whitespace check passes.
  • Independent OpenCode omni-route/zai/glm-5.3 source review approved this tools-only scope with no blocking findings.
  • A path-filtered GitHub workflow runs the same suite using Node 22, pinned actions, read-only repository permission and no persisted credentials.

The validation notes retain their historical 7.2 source identities and limitations. They do not certify a current 7.3 kernel build, sensor operation, USB4 support, or the separately unresolved camera stream-stop ownership contract in #73.

@ooaklee

ooaklee commented Oct 20, 2026

Copy link
Copy Markdown
Owner Author

Two further source-only exports are now available for tracking alongside the existing draft stack:

Actual OpenCode reviewed the bounded publication plan and public text with no publication blocker. This was not a new build or hardware test. Both PRs remain draft; the Surface, accepted kernels, builds and volumes are unchanged. GLINK ownership work remains deferred. The pending fresh native sensor build still needs separate approval.

Add a bounded, independently written Chromatix container reader with synthetic tests. Resolve named register references for private research while keeping default reports limited to identities, offsets and digests.

Recognize the ACPI V1 minimum argument storage and four-byte integers alongside the observed eight-byte form. Record REA-verified sensor probe fields and power-resource delay units without generating hardware configuration or adding Windows dependencies.
Document the native sensor foundation, source-only checks and remaining Denali wiring, module power and capture gates.

Record the verified platform HAL conversion into the native CCI seven-bit address field without guessing firmware controller ordering. Preserve raw sensor metadata and add regression coverage for the converted field.
Retain verified GPIO, voltage-vote and delay fields without inferring sensor pin ownership or generating production policy. Keep unknown resources opaque and bound repeated wrapper output.

Add a strictly selected ARM64 resource-list reader with synthetic tests, and document the saved allocation addresses alongside the independently verified CCI consumer. Identical capture copies remain one observation.

Signed-off-by: Leon Silcott <leon@boasi.io>
Document the actual rear, front and auxiliary PCFG consumers, including the auxiliary address distinction. Keep requested PHY timing separate from sensor PLL and exposure clocks, and retain board, mode and illumination qualification gates.

Describe source-only OV13858 and VD55G0 foundations without introducing Windows production dependencies or hardware enablement.

Signed-off-by: Leon Silcott <leon@boasi.io>
Signed-off-by: Leon Silcott <leon@boasi.io>
Document the focused HDR exposure-limit correction and the replay of all
24 native camera patches against the exact tested carrier tree. Preserve
the distinction between the previous full kernel/module build and the
corrected driver's focused build and synthetic regression tests.

Record the source and artifact identities, retained contribution history,
and remaining board, runtime and illumination qualification boundaries.

Signed-off-by: Leon Silcott <leon@boasi.io>
Describe the format, shared-control-lock and G0 exposure-write corrections
in the third source-only camera bundle. Keep the original full-kernel
build separate from subsequent exact-source tests and focused module links.

Clarify that G0's manual maximum is not a proven automatic-exposure
ceiling, and retain the board, firmware and hardware qualification gates.
Earlier source archives remain independently identified historical records.

Signed-off-by: Leon Silcott <leon@boasi.io>
Describe the separately licensed bounded dtbloader source candidate, its complete native ARM64 COFF link and synthetic reader/adapter coverage. Keep factory-source, partition selection, FDT publication and installed-provider qualification explicitly open.

This does not add a kernel partition reader, enable a device or authorize EFI installation. Source notes contain no private captures, local tool paths or provisioning addresses.

Signed-off-by: Leon Silcott <leon@boasi.io>
Record the completed clean build of the exact 27-patch camera source, independent module mapping and artifact checks, and explicit review of quotation-only warning differences. Preserve the failed checker result and immutable source archive as historical evidence.

Describe the separate native board-priority correction, synthetic regression scope and versioned EFI protocol compatibility gate. Keep sized-input validation, staged FDT publication, factory ownership and hardware qualification explicitly outstanding.

Signed-off-by: Leon Silcott <leon@boasi.io>
Identify the complete four-patch native provisioning source bundle and its immutable archive digest, exact-base replay and public test coverage. Retain the previous archive and distinguish source-only evidence from installed-provider or hardware support.

Record direct checks for the two camera binding snapshots, generated examples and nine positive/negative schema controls. Inspect JSON diagnostics rather than treating make or validator exit status as sufficient. Keep unrelated carrier diagnostics and physical qualification gates explicit.

Signed-off-by: Leon Silcott <leon@boasi.io>
Document the separate staged-publication source commit, portable host test targets, full native link and independent evidence audit. Keep the immutable revision-2 archive distinct and retain explicit opening-error, factory-data, protocol and hardware qualification gates.

Signed-off-by: Leon Silcott <leon@boasi.io>
Document the immutable five-patch source archive, exact Linux replay and fresh extraction checks. Separate historical reader and matcher evidence from the current staged-publication source, retain deployment limitations and qualify the pre-commit native build inputs.

Signed-off-by: Leon Silcott <leon@boasi.io>
Document the separate unarchived opening-status follow-up, portable actual-source loader tests, full native link and supplied-source review. Preserve the immutable revision-three artifact, historical ADR context and explicit firmware and hardware qualification gates.

Signed-off-by: Leon Silcott <leon@boasi.io>
Signed-off-by: Leon Silcott <leon@boasi.io>
Document the source-only companion correction, host boundary tests and
fresh ARM64 object evidence without extending the earlier module proof
or claiming hardware readiness. Keep the older source archive and dated
validation history intact.

Signed-off-by: Leon Silcott <leon@boasi.io>
@ooaklee ooaklee changed the title [TRACKING] Native driver research and camera source foundations tools: add bounded SP11 research parsers and historical validation notes Nov 10, 2026
@ooaklee
ooaklee changed the base branch from sp11/integration-7.2.x to sp11/ubuntu-qcom-x1e-7.3.y November 10, 2026 14:32
@ooaklee
ooaklee force-pushed the x/sp11-windows-driver-parity-20261015 branch from a103bf0 to 67d009f Compare November 10, 2026 14:32
@ooaklee
ooaklee marked this pull request as ready for review November 10, 2026 14:33
@ooaklee
ooaklee merged commit 26c7245 into sp11/ubuntu-qcom-x1e-7.3.y Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant