Fix MMCE VCD reliability, HDD probing, and device defaults - #236
Fix MMCE VCD reliability, HDD probing, and device defaults#236NathanNeurotic wants to merge 6 commits into
Conversation
|
Important Review skippedNo new commits to review since the last review. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughHDD probing now supports silent failure reporting, configuration defaults use unified SMB/manual networking, MMCE launch ordering quiesces art loads before VCD handoff, and BDMA installation validates, backs up, and restores live driver files. ChangesLaunch and device probing robustness
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant Launch
participant vcdEnsureBdmaForLaunch
participant vcdBdmaLivePairPresent
participant vcdEquipBdma
participant MemoryCard
Launch->>vcdEnsureBdmaForLaunch: ensure BDMA for launch
vcdEnsureBdmaForLaunch->>vcdBdmaLivePairPresent: validate live module pair
vcdBdmaLivePairPresent->>MemoryCard: read both driver files
vcdEnsureBdmaForLaunch->>vcdEquipBdma: install when marker or pair is invalid
vcdEquipBdma->>MemoryCard: back up existing pair and marker
vcdEquipBdma->>MemoryCard: write new pair and marker
vcdEquipBdma->>MemoryCard: restore backup or clean up failed installation
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
8f272d1 to
ff80416
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
155f406 to
615d404
Compare
There was a problem hiding this comment.
Code Review
This pull request introduces a silent HDD module loading mechanism to prevent false-positive connection errors on HDD-less consoles during speculative legacy config discovery. It also moves the MMCE art-loading abort check before the VCD launch path to avoid card IO contention, improves safety in tryAlternateDevice by checking getcwd and increasing buffer size, and implements a robust backup-and-rollback mechanism for BDMA driver installation on memory cards. Feedback points out that the backup allocation function fails on empty files, which could block driver installation if a previous install was corrupted or left an empty marker file.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
23d61cf to
f3bcd6d
Compare
f3bcd6d to
b981b86
Compare
5579055 to
c5f13a8
Compare
b30e56e to
83f1917
Compare
83f1917 to
311c92a
Compare
7ba180d to
4b8dac0
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
Overview
Four functional commits keep each requested change reviewable:
Silence speculative HDD config probes
getcwdbuffer handling.Fix MMCE VCD art-quiesce ordering
Make BDMA replacement transactional
Default Device Settings entries to Manual or Off
A fifth formatting-only commit applies the repository's required clang-format 12 configuration to the single pre-existing line flagged by the repository-wide CI check. The final empty bookkeeping commit records that formatter-generated tree through a normal push so GitHub can execute CI without Actions-token approval gating.
Validation
Do not treat this PR as test-ready until the complete compile matrix and CI format check are green. Hardware tests should cover HDD-less startup, legacy HDD config discovery, repeated MMCE VCD launches during artwork browsing, interrupted BDMA replacement, corrupted marker recovery, and fresh Device Settings defaults.