Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.101 and 1.103

version 1.101, 2018/11/06 22:12:42 version 1.103, 2018/11/06 22:29:26
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)
   
 We use .e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.  
   
   
 \todo Add information  on Pi Zero and Pi Zero W.  
   
 ## NetBSD 7 and NetBSD 8  ## NetBSD 7 and NetBSD 8
   
  - RPI1, RPI2, 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 (as RPI3, no WiFi, but one needs fdt files \todo where from?)   - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?)
  - multiple processors on RPI2/RPI3   - 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
Line 42  We use .e.g. "RPI2" to refer to "Raspber Line 37  We use .e.g. "RPI2" to refer to "Raspber
  - RPI3 builtin bluetooth   - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver   - 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.
Line 61  In theory the code compiled for earmv7hf Line 62  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 with 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 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 105  An example URL, arguably the standard ap Line 106  An example URL, arguably the standard ap
 Once you get to the releasedir, self-built and autobuild releases have the same structure.  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.   - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that uses the armv7 instruction set, and thus can run only on the RPI2 and RPI3 (and perhaps the CM3).  It also supports systems other than the RPI family.
   
 \todo Explain why there is no armv7_inst.gz.  \todo Explain why there is no armv7_inst.gz.
   

Removed from v.1.101  
changed lines
  Added in v.1.103


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