version 1.80, 2018/10/30 23:20:06
|
version 1.81, 2018/11/06 01:42:03
|
Line 43 Initial, limited, Raspberry Pi support w
|
Line 43 Initial, limited, Raspberry Pi support w
|
# CPU types |
# CPU types |
|
|
- Raspberry Pi 1 uses "earmv6hf". |
- Raspberry Pi 1 uses "earmv6hf". |
|
- Raspberry Pi 0 uses "\todo". |
- Raspberry Pi 2 uses "earmv7hf". |
- Raspberry Pi 2 uses "earmv7hf". |
- Raspberry Pi 3 uses "earmv7hf". |
- Raspberry Pi 3 uses "earmv7hf". |
|
- Raspberry Pi 0W uses "\todo". |
|
|
Note that one can run earmv6hf code on the 2 and 3. See also |
Note that one can run earmv6hf code on the 2 and 3. See also |
[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. |
[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. |
Line 73 Both will provide rpi.img.gz and rpi_ins
|
Line 75 Both will provide rpi.img.gz and rpi_ins
|
|
|
### Building yourself |
### Building yourself |
|
|
Getting sources and building a release with build.sh is not special for evbarm. Pick a CPU type alias and pass it to build.sh with -m. Examples (the first two are equivalent): |
Getting sources and building a release with build.sh is not special for evbarm. However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one. The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH". build.sh supports aliases that can be passed a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line is an example (equal to the second in effect). |
|
|
- ./build.sh -m earmv6hf -u release |
|
- ./build.sh -m evbarm -a earmv6hf -u release |
- ./build.sh -m evbarm -a earmv6hf -u release |
- ./build.sh -m evbarm -a earmv7hf -u release |
- ./build.sh -m evbarm -a earmv7hf -u release |
|
- ./build.sh -m earmv7hf-el -u release |
|
|
|
Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values on the same system; see build.sh. |
|
|
### NetBSD FTP servers |
### NetBSD FTP servers |
|
|