Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.130 and 1.135

version 1.130, 2020/09/05 12:54:33 version 1.135, 2020/10/15 19:58:19
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 203  The program vcgencmd, referenced in the  Line 200  The program vcgencmd, referenced in the 
   
 ## Updating the kernel  ## Updating the kernel
   
  - Build a new kernel, e.g. using build.sh. It will tell you where the ELF version of the kernel is, e.g.   - Run uname -a to determine the name of the config of your current kernel.  For NetBSD <= 8, one ran RPI or RPI2.  For NetBSD >=9, one uses GENERIC.
    - Build a new kernel, e.g. using build.sh. Ideally, run "build.sh release" and look in releasedir/binary/kernels.  If building just a kernel, it will tell you where the ELF version of the kernel is, e.g.
          ...           ...
          Kernels built from RPI2:           Kernels built from GENERIC:
           /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/RPI2/netbsd            /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/GENERIC/netbsd
          ...           ...
    - There are multiple kernel formats produced by a release build, for use with different boot loader schemes..  For GENERIC:
  - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.img" (for current) or "netbsd.bin" (for 7 and 8) kernel that is in a format that the Raspberry can boot.     - netbsd-GENERIC: A normal kernel in ELF format.
      - netbsd-GENERIC.img: In NetBSD >= 9, formatted for the RPI bootloader.
      - netbsd-GENERIC.bin: In NetBSD <= 8, formatted for the RPI bootloader.  In NetBSD >= 9, ??????  In NetBSD 9, this kernel WILL NOT boot.
      - netbsd-GENERIC.ub: A kernel in uboot format.
  - Depending on your hardware version, copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware)   - Depending on your hardware version, copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware)
  - reboot   - reboot
   
 \todo Explain if updating firmware is necessary when e.g. moving from 8 to 9, or 9 to current.  \todo Explain if updating firmware is necessary when e.g. moving from 8 to 9, or 9 to current.
   
   ## Updating dtb files
   
   (This is harder than it should be.)
   Build a release.  gunzip the armv7.img, vnconfig it, and mount the MSDOS partition (e) e.g. on /mnt.  Copy the dtb files from /mnt/foo.dtb to /boot, and from /mnt/dtb/foo.dtb to /mnt/dtb.
   
   It seems that some systems, including RPI, require dtb files in /boot, and some expect them in /boot/dtb.
   
   \todo Explain if you only really need the right one for your system type.
   
   \todo Explain how one is supposed to be able to update these from the dtb files in releasedir/binary/kernel, or fix it to have the same structure.
   
 ## Updating the firmware  ## Updating the firmware
   
   It is highly likely that running NetBSD from a given branch X with firmware from a branch Y < X will not go well.  It is unclear if firmware from a branch Y > X will work.  It is standard practice to use firmware from the right branch.
   
 A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.  A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.
   
   (Updating the firmware is harder than it should be.)
   Build a release.  gunzip the armv7.img, vnconfig it, and mount the MSDOS partition (e) e.g. on /mnt.  Copy files from that to /boot that have changes, carefully.
   
   Relevant files include bootcode.bin, start.elf and start_cd.elf.
   
   Compare cmdline.txt, but beware that just overwriting it will lose customizations like using the serial console instead of the framebuffer.
   
 \todo Explain where the firmware is in the source tree, and note that it is not 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 note that it is not 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 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.
Line 249  The aarch64 kernel can run aarch32 binar Line 269  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
   

Removed from v.1.130  
changed lines
  Added in v.1.135


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