|
version 1.131, 2020/10/15 19:27:27
|
version 1.133, 2020/10/15 19:50:42
|
|
Line 18 The HOWTO is written for what works on f
|
Line 18 The HOWTO is written for what works on f
|
| |
|
| "Works" is primarily relative to the earmv6hf-el and earmv7hf-el CPU targets (32-bit). |
"Works" is primarily relative to the earmv6hf-el and earmv7hf-el CPU targets (32-bit). |
| |
|
| ## NetBSD 7 and NetBSD 8 |
## NetBSD 8 |
| |
|
| - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth) |
- RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth) |
| - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?) |
- RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?) |
|
Line 51 The HOWTO is written for what works on f
|
Line 51 The HOWTO is written for what works on f
|
| These items do not work in the sense that they simply function after a standard install. Being listed here implies only that there has been list traffic that implies that after taking a bunch of steps (e.g. new firmware, new dtbs, enabling drivers, applying patches), one can end up with the feature working. The HOWTO explicitly refrains from describing these steps because they are ephemeral. However, the fact that list traffic indicates success is possible is a clue that proper support is on the horizon, and that is notable. |
These items do not work in the sense that they simply function after a standard install. Being listed here implies only that there has been list traffic that implies that after taking a bunch of steps (e.g. new firmware, new dtbs, enabling drivers, applying patches), one can end up with the feature working. The HOWTO explicitly refrains from describing these steps because they are ephemeral. However, the fact that list traffic indicates success is possible is a clue that proper support is on the horizon, and that is notable. |
| |
|
| - RPI3 and RPI0W builtin WiFi |
- RPI3 and RPI0W builtin WiFi |
| |
- RPI4 |
| |
|
| ## What needs documenting if it works |
## What needs documenting if it works |
| |
|
| |
- (Everything listed in the previous section.) |
| - CM1 |
- CM1 |
| - CM3 |
- CM3 |
| - CM3lite |
- CM3lite |
| |
|
| ## What needs work |
## What needs work |
| |
|
| - RPI4 (as of 2020-01, still does not work in current) |
|
| - USB (host); isochronous transfers. |
- USB (host); isochronous transfers. |
| - RPI0W Bluetooth Low Energy (probably) |
- RPI0W Bluetooth Low Energy (probably) |
| |
|
|
Line 80 In theory the code compiled for earmv7hf
|
Line 81 In theory the code compiled for earmv7hf
|
| |
|
| While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work. Systems built for older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI. |
While the evbarm port has "eb" variants (for big-endian mode), the RPI systems do not support eb and these variants will not work. Systems built for older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI. |
| |
|
| The RPI2-1.2 and RPI3 have an armv8 CPU that supports aarch64 (64-bit |
The RPI2-1.2, RPI3 and RPI4 have an armv8 CPU that supports aarch64 (64-bit mode) in addition to aarch32 (regular 32-bit ARM). This is supported, from 9 onwards, by the "aarch64" MACHINE_ARCH of evbarm, also available in build.sh via the alias evbarm64. This is also referred to as [[NetBSD/aarch64|aarch64]]. |
| mode) in addition to aarch32 (regular 32-bit ARM). This is supported, |
|
| from 9 onwards, by the "aarch64" MACHINE_ARCH of evbarm, also |
|
| available in build.sh via the alias evbarm64. This is also |
|
| referred to as [[NetBSD/aarch64|aarch64]]. |
|
| |
|
| # Installation |
# Installation |
| |
|
|
Line 119 Consider setting RELEASEMACHINEDIR if yo
|
Line 116 Consider setting RELEASEMACHINEDIR if yo
|
| |
|
| ### NetBSD autobuild HTTPS/FTP servers |
### NetBSD autobuild HTTPS/FTP servers |
| |
|
| NetBSD provides nightly builds on [nycdn.netbsd.org](https://nycdn.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. |
NetBSD provides nightly builds on [nycdn.netbsd.org](https://nycdn.netbsd.org/pub/NetBSD-daily/). The next directory level is the branch being built (netbsd-8, netbsd-9, 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 first-time NetBSD/RPI users, is <https://nycdn.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://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-8/latest/evbarm-earmv7hf/binary/gzimg/> |
| |
|
|
Line 270 The aarch64 kernel can run aarch32 binar
|
Line 267 The aarch64 kernel can run aarch32 binar
|
| |
|
| ## Video playback |
## Video playback |
| |
|
| Accelerated video playback is supported in NetBSD 7 with the [OMXPlayer](http://pkgsrc.se/multimedia/omxplayer) application and through GStreamer with the [omx](http://pkgsrc.se/multimedia/gst-plugins1-omx) plugin. |
Accelerated video playback is supported with the [OMXPlayer](http://pkgsrc.se/multimedia/omxplayer) application and through GStreamer with the [omx](http://pkgsrc.se/multimedia/gst-plugins1-omx) plugin. |
| |
|
| ## OpenGL ES |
## OpenGL ES |
| |
|
| Accelerated OpenGL ES is supported in NetBSD 7. The GL ES client libraries are included with the [misc/raspberrypi-userland](http://pkgsrc.se/misc/raspberrypi-userland) package. |
Accelerated OpenGL ES is supported. The GL ES client libraries are included with the [misc/raspberrypi-userland](http://pkgsrc.se/misc/raspberrypi-userland) package. |
| |
|
| ## Quake 3 |
## Quake 3 |
| |
|
![[BACK]](/icons/back.gif){kind=icon}
Return to raspberry_pi.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc / ports / evbarm