Conversation
gly11
force-pushed
the
pr/controller-bringup-recovery
branch
from
May 27, 2026 14:06
9959fde to
b5eaa71
Compare
gly11
force-pushed
the
pr/sbp2-session-core
branch
from
May 27, 2026 14:28
87a50ed to
eff2132
Compare
gly11
force-pushed
the
pr/controller-bringup-recovery
branch
from
May 27, 2026 14:28
b5eaa71 to
c122677
Compare
gly11
force-pushed
the
pr/sbp2-session-core
branch
from
May 27, 2026 14:44
eff2132 to
76a8f1d
Compare
gly11
force-pushed
the
pr/controller-bringup-recovery
branch
from
May 27, 2026 14:44
c122677 to
478117c
Compare
gly11
force-pushed
the
pr/controller-bringup-recovery
branch
from
May 27, 2026 14:58
478117c to
9453b4c
Compare
gly11
force-pushed
the
pr/sbp2-session-core
branch
from
May 27, 2026 14:59
76a8f1d to
166b8a7
Compare
gly11
pushed a commit
that referenced
this pull request
Jul 25, 2026
…ation 44100.md: - §12: reverse-engineer RME FirefaceAudioDriver's 44.1 cadence — DCL-branch Bresenham (increment = rate/8000), closed-loop RX clock recovery via the +276 per-group target table and a 1/16 IIR estimate, and per-rate startup latency anchors. Behavioral/algorithm observations only (proprietary binary). - Extend the IDA evidence index and add RME-specific open questions. - Mark all open questions with status: #6 RESOLVED (Linux cross-check), #8 RESOLVED-by-decision (resync branch not needed under replay), mrmidi#12 RESOLVED design / capture-gated value; flag #1–#5 as legacy-DCL archaeology, not blockers. SAMPLE_RATE_EXPANSION.md: - §3: minimal TX cadence contract ({data/no-data, SYT}; DBC free; SYT = delta replay + per-rate phase re-anchor; payload separate; RX carries none) and what "device-as-master" does and does not remove. - §8: consolidate the capture-gated items into one measurement (per-rate presentation lead + startup-prefix tolerance) in one gated session, partly self-instrumented via [TxSyt]/[Zts] traces; #9/#10 moot under replay. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
This PR is stacked on
pr/sbp2-session-coreand tightens controller bring-up behavior on top of the SBP-2 session core work.Controller Bring-Up
Why this PR
The controller changes are useful independently of the higher-level Swift connector and UI work. Keeping them in their own slice lets reviewers focus on hardware bring-up policy and DriverKit configuration without mixing in app-side SBP-2 surfaces.
This PR intentionally does not include debug UI, diagnostic handlers, local scripts, install helpers, or documentation-only planning notes.
Verification
Local verification completed for this slice: