version 1.95, 2018/11/06 17:26:24
|
version 1.96, 2018/11/06 17:34:03
|
Line 50 Initial, limited, Raspberry Pi support w
|
Line 50 Initial, limited, Raspberry Pi support w
|
- Raspberry Pi 3 uses "earmv7hf". |
- Raspberry Pi 3 uses "earmv7hf". |
- Raspberry Pi Zero W uses "\todo". |
- Raspberry Pi Zero W uses "\todo". |
|
|
Note that one can run earmv6hf code on the 2 and 3. See also |
Note that one can run earmv6hf userland code on the 2 and 3. In theory the code compiled for earmv7hf will be faster. \todo Benchmark and explain. \todo Explain if one can run the earmv6hf RPI2 kernel on RPI1. \todo Explain if the earmv6hf rpi.img.gz will run on a RPI2/3. |
[[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. |
|
|
\todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3. |
|
|
|
See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode. |
|
|
# Installation |
# Installation |
|
|
Line 72 See also "ebijun's image", below, which
|
Line 75 See also "ebijun's image", below, which
|
|
|
## Getting bits to install |
## Getting bits to install |
|
|
You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers. The bits from both sources should match, except for things like timestamps, or because the sources are slightly different along branches. |
You can either build a release yourself with build.sh, or get a release from the NetBSD HTTPS/FTP servers. The bits from both sources should match, except for things like timestamps, or because the sources are from slightly different points along branches. |
|
|
### Building yourself |
### Building yourself |
|
|
Line 86 Consider setting RELEASEMACHINEDIR if yo
|
Line 89 Consider setting RELEASEMACHINEDIR if yo
|
|
|
### NetBSD autobuild HTTPS/FTP servers |
### NetBSD autobuild HTTPS/FTP servers |
|
|
NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/). These are equivalent to building yourself. The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type. It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it. The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided. |
NetBSD provides nightly builds on [nyftp.netbsd.org](https://nyftp.netbsd.org/pub/NetBSD-daily/). The next directory level is the branch being built (netbsd-7, netbsd-8, HEAD, and more), plus optionally things like compiler type. It is followed by date/time, e.g. "HEAD/201811051650Z"; once a build is complete the symlink "latest" is adjusted to point to it. The next level is "${MACHINE}-${MACHINE_ARCH}", e.g. "evbarm-earmv7hf", and multiple combinations are provided. |
|
|
An example URL, arguably the standard approach for beginners, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/ |
An example URL, arguably the standard approach for first-time NetBSD/RPI users, is https://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/ |
|
|
### release layout |
### release layout |
|
|
|
Once you get to the releasedir, self-built and autobuild releases have the same structure. |
|
|
- The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that will run on any of the RPI boards. |
- The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that will run on any of the RPI boards. |
- The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the Raspberry Pi 2/3, but is also faster than rpi.img. |
- The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the Raspberry Pi 2/3. |
|
|
\todo Explain why there is no armv7_inst.gz. |
\todo Explain why there is no armv7_inst.gz. |
|
|