Fix inherited secondary joystick buttons crossed between CoCo ports
This commit is contained in:
1 parent
961f586d06
commit
bf36c0569a
8 files changed
+285
-131
No files matched your search
@@ -6,6 +6,21 @@ logic from new features and defects found while integrating those features.
|
||||
The checks below establish their stated scopes; they do not turn source
|
||||
inspection into a claim of a reproduced field failure.
|
||||
|
||||
## Inherited secondary joystick-button routing, 2026-11-21
|
||||
|
||||
The MiSTer top-level binding crossed the two joystick secondary buttons while
|
||||
primary buttons and axes stayed with their selected ports. This wiring is
|
||||
already present in upstream first commit f00b53c (2021-12-21), not introduced by
|
||||
Plus. Correct only the P_SWITCH binding and its misleading secondary-row comments.
|
||||
The Tandy 26-3334 service manual, printed page9, assigns PIA0 PA0=right primary,
|
||||
PA1=left primary, PA2=right secondary and PA3=left secondary.
|
||||
|
||||
The extracted actual-RTL regression fails on unchanged wiring and passes524288
|
||||
cases on the correction: both port-swap positions, all16 button combinations,
|
||||
mouse states, keyboard column masks and keyboard-row patterns. It is included in
|
||||
scripts/run_regressions.py. This is a simulation result, not a physical-controller
|
||||
or CocoMan firing pass. Native fit, timing and hardware checks are pending here.
|
||||
|
||||
## Inherited clock, reset and memory paths
|
||||
|
||||
| Area and problem | Change and relevant source | Verification and limits |
|
||||
|
||||
Reference in new issue
Block a user