Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.100 and 1.102

version 1.100, 2018/11/06 18:16:43 version 1.102, 2018/11/06 22:24:59
Line 1 Line 1
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]  [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
   
 This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.  This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are supported.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
   
 Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017.  (This page assumes those using NetBSD 7 are using 7.2, or the netbsd-7 branch after mid 2018.)  Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0. NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017.  (This page assumes those using NetBSD 7 are using 7.2, or the netbsd-7 branch after mid 2018.)
   
Line 12  Initial, limited, Raspberry Pi support w Line 12  Initial, limited, Raspberry Pi support w
   
 # What works (and what doesn't yet)  # What works (and what doesn't yet)
   
 \todo Add information  on Pi Zero and Pi Zero W.  
   
 ## NetBSD 7 and NetBSD 8  ## NetBSD 7 and NetBSD 8
   
  - RaspberryPi 1, 2, 3 (except Pi 3 builtin WiFi and bluetooth)   - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth)
  - multiple processors on 2/3   - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?)
    - multiple processors on RPI2/RPI3
  - boots normally to multiuser, with FAT32 boot partition on uSD   - boots normally to multiuser, with FAT32 boot partition on uSD
  - root filesystem can be uSD or USB-attached mass storage   - root filesystem can be uSD or USB-attached mass storage
  - serial or graphics console (with EDID query / parsing)   - serial or graphics console (with EDID query / parsing)
Line 34  Initial, limited, Raspberry Pi support w Line 33  Initial, limited, Raspberry Pi support w
   
 ## NetBSD current  ## NetBSD current
   
  - Raspberry Pi 3 builtin bluetooth   - RPI3B+ 
  - Raspberry Pi 3 new SD host controller driver   - RPI3 builtin bluetooth
    - RPI3 new SD host controller driver
   
   ## What needs documenting if it works
   
    - CM1
    - CM3
    - CM3lite
   
 ## What needs work  ## What needs work
   
  - USB (host); isochronous transfers.   - USB (host); isochronous transfers.
  - Raspberry Pi 3 builtin WiFi   - RPI3 builtin WiFi
   
 # CPU types  # CPU types
   
  - Raspberry Pi 1 uses "earmv6hf".   - RPI1 uses "earmv6hf".
  - Raspberry Pi Zero uses "\todo".   - RPI0 uses "\todo".
  - Raspberry Pi 2 uses "earmv7hf".   - RPI2 uses "earmv7hf".
  - Raspberry Pi 3 uses "earmv7hf".   - RPI3 uses "earmv7hf".
  - Raspberry Pi Zero W uses "\todo".   - RPI0W uses "\todo".
   
 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.  Note that one can run a build of earmv6hf on the 2 and 3.  There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set.
   
 \todo Explain if one can run "eb" variants.  (However, using eb is likely to find more bugs because almost everyone uses el.  That can either be a reason to run it or not run it.)  In theory the code compiled for earmv7hf will be faster, but anecdotal experience is that it doesn't matter that much.
   
 \todo Explain if systems built with earm or earmv5 will work on RPI or RPI2/3.  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 with older CPU architectures (earm, earmv4, earmv5) are not expected to work on RPI.
   
 See also [[NetBSD/aarch64|aarch64]] for running the Pi 2/3 in 64-bit mode.  See also [[NetBSD/aarch64|aarch64]] for running the RPI2-1.2 and RPI3/RPI3+ in 64-bit mode.
   
 # Installation  # Installation
   
Line 188  A section below describes the process of Line 194  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.
   
 \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.
   
 ## Booting  ## Booting
Line 203  An alternate approach is to have the boo Line 211  An alternate approach is to have the boo
 A third approach, workable on the Pi 3 only, is to configure USB host booting (already enableed on the 3+; see the upstream documentation) and have the boot partition also on the external device.  In this case the external device must have an MBR because the hardware's first-stage boot does not have GPT support. In theory the [procedure to program USB host boot mode](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md) will function on a NetBSD system because the programming is done by bootcode.bin.  A third approach, workable on the Pi 3 only, is to configure USB host booting (already enableed on the 3+; see the upstream documentation) and have the boot partition also on the external device.  In this case the external device must have an MBR because the hardware's first-stage boot does not have GPT support. In theory the [procedure to program USB host boot mode](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md) will function on a NetBSD system because the programming is done by bootcode.bin.
 \todo Confirm that putting program_usb_boot_mode=1 in config.txt and booting works to program the OTP bit.  Confirm that one can then boot NetBSD from external USB.  \todo Confirm that putting program_usb_boot_mode=1 in config.txt and booting works to program the OTP bit.  Confirm that one can then boot NetBSD from external USB.
   
 \todo Explain USB enumeration and how to ensure that the correct boot and root devices are found if one has e.g. a small SSD for the system and a big disk.  There is no well-defined USB enumeration order, so the preferred approach if one has multiple USB mass storage devices is to use named wedges in both fstab and cmdline.txt.
   
 # X11 and GPU  # X11 and GPU
   
 ## Console font  
   
 Some find the default font to be too small.  \todo Give a link to the normal instructions on how to change it.  
   
 ## 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 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.
   

Removed from v.1.100  
changed lines
  Added in v.1.102


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb