docs: draft Bigscreen DisplayID parser proof packet#72
Draft
Jesssullivan wants to merge 1 commit into
Draft
Conversation
Open
3 tasks
📝 Blog Post ReviewFound 1 blog post(s) in this PR:
Schema Validation✅ All posts pass schema validation. Slash Commands
|
6 tasks
Owner
Author
|
2026-04-28 truth pass: this remains the current Bigscreen DisplayID/parser proof-packet surface. It is draft and CI-green. Linear mapping: TIN-622 owns the proof-packet coordination and TIN-612 owns the linux-xr upstream route decision. Keep this draft until the 2026-04-30 decision is made; it is evidence/supporting material, not a publish-ready post yet. |
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.
Summary
Validation
just validate-frontmatterpassed 167/167git diff --checkpassedNotes
The kernel quirk-only route is held. Current
drm-misc-nextparser behavior is proven by KUnit onhoney; remaining decision is regression-test-only patch vs downstream carry cleanup.