Skip to content

Commit

Permalink
docs: mention architecture discrepancies (see #4)
Browse files Browse the repository at this point in the history
  • Loading branch information
koehlma committed Dec 3, 2023
1 parent 77567de commit 843ad78
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion www/docs/guide/supported-boards.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ In principle, Rugpi supports all Raspberry Pi models.

| Pi 5 | Pi 4 | Pi 3 | Pi 2 v1.2 | Pi 2 | Pi 1 | Pi Zero 2 | Pi Zero | CM 4 | CM 3 | CM 1 |
| ---- | ---- | ------ | --------- | ----- | ------ | --------- | ------- | ---- | ----- | ------ |
|||[^1] |[^1] | 🤷‍♂️[^1] |[^1] |[^1] | 🤷‍♂️[^1] || 🤷‍♂️[^1] | 🤷‍♂️[^1] |
|||[^1] |[^1] | 🤷‍♂️[^1] |[^1] |[^1] | [^1] || 🤷‍♂️[^1] | 🤷‍♂️[^1] |

✅ fully supported, 🤷‍♂️ in principle supported but untested

Expand All @@ -28,6 +28,9 @@ To build 32-bit images, you also need to enable emulation of `armhf` in Docker:
docker run --privileged --rm tonistiigi/binfmt --install armhf
```

For `armhf`, note that the architecture reported by `uname -m` during the build process is `armv7l`, however, when running the image later on a non-ARMv7 board (e.g., Pi Zero or Pi 1), then the architecture will be `armv6l`.
Make sure that the binaries you install are compatible with the `armv6l` architecture, if you aim to deploy the image to these boards.

### Raspberry Pi 5

If you are using the quick-start template, please remove the option `include_firmware = "pi4"` from `rugpi-bakery.toml`.
Expand Down

0 comments on commit 843ad78

Please sign in to comment.