Name the two Orin units by hostname

The hardware table listed mikkeli-orin-nano-2 as the main compute, but
that is the development unit; the car unit is mikkeli-orin-nano. Both
the README and the REPOS units table now say which is which.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mikkeli
2026-10-08 09:58:51 +09:00
parent cbd31cf8fc
commit d8c40eb9ed
2 changed files with 4 additions and 3 deletions
+2 -1
View File
@@ -32,7 +32,8 @@ Planned repositories and the reasoning behind the split are described in
| Part | Role | | Part | Role |
|---|---| |---|---|
| NVIDIA Jetson Orin Nano Super (`mikkeli-orin-nano-2`) | Main compute, JetPack r36.4 / Ubuntu 22.04 | | NVIDIA Jetson Orin Nano Super (`mikkeli-orin-nano`) | Car unit: main compute, JetPack r36.4 / Ubuntu 22.04 |
| NVIDIA Jetson Orin Nano Super (`mikkeli-orin-nano-2`) | Development unit: builds, CI, bench (see [REPOS](docs/REPOS.md)) |
| PEAK PCAN-USB | Car CAN bus access (`can1`, 500 kbps) | | PEAK PCAN-USB | Car CAN bus access (`can1`, 500 kbps) |
| Onboard MTTCan | Second CAN interface (`can0`) | | Onboard MTTCan | Second CAN interface (`can0`) |
| Waveshare SIM7600G-H-M.2 | LTE Cat 4 + GNSS | | Waveshare SIM7600G-H-M.2 | LTE Cat 4 + GNSS |
+2 -2
View File
@@ -153,8 +153,8 @@ Two Orin Nanos, and they have different jobs:
| Unit | Role | | Unit | Role |
|---|---| |---|---|
| Development Orin | Build, CI runner, bench testing. Always powered, on the LAN | | Development Orin (`mikkeli-orin-nano-2`) | Build, CI runner, bench testing. Always powered, on the LAN |
| Car Orin | Deployment target only | | Car Orin (`mikkeli-orin-nano`) | Deployment target only |
⚠ **The guarantee is version parity, not architecture.** An aarch64 binary built ⚠ **The guarantee is version parity, not architecture.** An aarch64 binary built
on a newer userland still fails to load on an older one. A JetPack or Ubuntu on a newer userland still fails to load on an older one. A JetPack or Ubuntu