version 1.104, 2018/11/06 22:31:35
|
version 1.105, 2018/11/06 22:34:51
|
Line 33 Initial, limited, Raspberry Pi support w
|
Line 33 Initial, limited, Raspberry Pi support w
|
|
|
## NetBSD current |
## NetBSD current |
|
|
- RPI3B+ |
- RPI3+ |
- RPI3 builtin bluetooth |
- RPI3 builtin bluetooth |
- RPI3 new SD host controller driver |
- RPI3 new SD host controller driver |
|
|
Line 46 Initial, limited, Raspberry Pi support w
|
Line 46 Initial, limited, Raspberry Pi support w
|
## What needs work |
## What needs work |
|
|
- USB (host); isochronous transfers. |
- USB (host); isochronous transfers. |
- RPI3 builtin WiFi |
- RPI3, RPI0W builtin WiFi |
|
- RPI0W Bluetooth Low Energy (probably) |
|
|
# CPU types |
# CPU types |
|
|
Line 194 A section below describes the process of
|
Line 195 A section below describes the process of
|
|
|
\todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec). Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree. Explain any particular cautions. |
\todo Explain where the firmware is in the source tree, and if it is in the installed system image (such as /usr/mdec). Explain how to update a system (presumably /boot) from either an installed system's new firmware files, or the source tree. Explain any particular cautions. |
|
|
Probably, for the RPI3B+, one needs to use -current, or use -8 with firmware from -current. \todo Defuzz. |
Probably, for the RPI3+, one needs to use -current, or use -8 with firmware from -current. \todo Defuzz. |
|
|
\todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe. Explain if pullups are done to release branches with new firmware. |
\todo Explain if using updated firmware from one branch (e.g. netbsd-current) on a system using a different branch (e.g. netbsd-8) is safe. Explain if pullups are done to release branches with new firmware. |
|
|