Repository navigation
device/lynx: clarify historical Wi-Fi source and safety evidence - #822
Open
latentoperator wants to merge 2 commits into
Open
latentoperator wants to merge 2 commits into
latentoperator wants to merge 2 commits into
Conversation
Tie the two historical connection tests to an immutable archival source snapshot, preserve the DHCP-readiness failure and distinguish signed-source preparation from runtime qualification. Clarify the recorded Trusty-storage scope and hardware watchdog disarm, and credit alfikpl for the ordering lead. Assisted-by: LLM
Owner
|
Thank you, Chris. This answers all four things I asked on #751: the tested tree is on your fork under a branch (I checked that Three small things and it can leave draft:
Nothing here needs a phone. Mark it ready when those are in and I'll merge it. |
Record the endpoint and SysMMU configuration in the tested DT, date the draft kernel series and clarify the scope of the revised activation. Assisted-by: LLM
latentoperator
marked this pull request as ready for review
November 19, 2026 02:55
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
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.
The historical Wi-Fi report now links the complete tested MSI source snapshot and records the later post-reboot connection, including the DHCP-readiness failure before the successful bounded activation. It keeps both old-stack successes separate from qualification of the revised signed integration.
This also answers the follow-ups on #751: names alfikpl for the ordering lead, limits the Trusty-storage statement to the recorded lab stages and process checks, and makes clear that the S3C2410 hardware watchdog itself was disabled with WDIOS_DISABLECARD after successful checks. It does not claim a continuous whole-boot storage audit or an unchanged RPMB write counter.
Historical release:
7.3.0-rc6-omamobile-lynx-msi-20261113+. Archival source: latentoperator/linux-omarchy-mobile@3fd82de (provenance only, not proposed for merge). The preserved earlier WMI/TX/USB failure and later DHCP-readiness failure remain part of the evidence. No new hardware operation or runtime pass is claimed by this documentation change.Validation:
tools/pr-check,git diff --checkandtests/allpass.tests/packagesfinishes with onlyomamobile-modemfailing: its pre-existing NV-overlay Broken pipe / “failure at object” test failure also reproduces from pristine upstreamca82fe7. Modem code is unchanged; all other package suites pass. This is disclosed rather than presented as a green full-package gate.