Historical record. The dates, candidate identity, "current" claims, next steps and permissions below belong to this recorded boundary. See current state for the latest physically observed result.
Current hardware result: owner-observed M1 runtime success confirms Linux 6.18, native PID1, increasing BEAT/uptime, working sleep, proc/sysfs mounts, CPU0, D08 RAM visibility, framebuffer diagnostics and stopped-watchdog status. M1 core achieved. Exact flashed hash and unreported diagnostic fields remain unverified. Earlier dated statements below are historical.
Y2B-240 hardware result: the owner reports solid green, which the implemented state machine reaches through initramfs
/initrunning as PID1. M1's Linux 6.18 plus PID1 boot objective is achieved. No heartbeat/checkerboard success is claimed. Y2B-245 / D14 is the offline follow-up for readable runtime diagnostics.
Date: 2026-09-08. Related research: Y2E-101/105/110/115/120. Scope: one current device plus explicitly identified historical captures. CONFIRMED always means confirmed in the cited input/session, not every Y2 revision.
| Status | Fact | Evidence | Implication |
|---|---|---|---|
| CONFIRMED, current | MT6582, ARMv7, Cortex-A7 part 0xc07 with NEON/VFPv4 | 20260908-stock/cpuinfo.stdout |
Linux target family supported by evidence; complete Linux board support not established. |
| CONFIRMED, current | Kernel reports version 3.4.67; Android 4.4.2/API 19 | version.stdout, selected getprop in baseline |
Stock-family system only; exact installed image is UNKNOWN. |
| CONFIRMED, current | 7,784,103,936-byte internal eMMC user region and separate SD | partition map, capture 20260908-partitions |
Respect hardware regions and vendor metadata differences. |
| CONFIRMED, historical | CS43131 and AW87559 driver bindings on I2C bus 1 | Verified snapshot 2026-07-29_004935/hardware/i2c-identities.txt |
Separate headphone and speaker dependencies; wiring and analog behavior remain open. |
| CONFIRMED, historical | APT32F and UPDATE driver names on I2C bus 0 | Same snapshot | Name/binding does not establish controller function or firmware protocol. |
| CONFIRMED, historical | pmic_mt6323, input/controller nodes |
Verified snapshot platform/input inventories | Useful discovery anchors for fresh passive subsystem research. |
| UNKNOWN | Physical PCB/FM revision, exact installed boot/system lineage, trusted battery readings | recovery assessment, current conflicting battery service output | Required before selecting a recovery baseline. |
The archive contains engineering reports rather than electrical verification of all routes. The current session did not re-run audio/FM experiments or scan hardware buses. See evidence provenance for hash validation and superseded claims, open unknowns for blockers, and subsystem documents for next proof requirements.
2026-09-08: installed console core selects ttyMT0; sysfs and /proc/iomem map it to UART0 at 0x11002000. The FM driver was remapped to rule out index swapping. Observation-path evidence supersedes UART3 as the first-artifact candidate. Native UART logic is expected to be 1.8 V from the manufacturer pin-domain table; no Y2 pad voltage or TX/GND test point is confirmed. Physical UART and actual LK/kernel wire capture remain a launch prerequisite.