Diff for /wikisrc/ports/evbarm.mdwn between versions 1.53 and 1.72

version 1.53, 2018/11/07 14:41:31 version 1.72, 2019/06/12 08:29:41
Line 7  port_var3="earmv6hf" Line 7  port_var3="earmv6hf"
 port_var4="earmv7hf"  port_var4="earmv7hf"
 port_var5="earmv7hfeb"  port_var5="earmv7hfeb"
 port_var_install_notes="evbarm-earm"  port_var_install_notes="evbarm-earm"
 cur_rel="8.0"  cur_rel="8.1"
 future_rel="9.0"  future_rel="9.0"
 changes_cur="8.0"  changes_cur="8.1"
 changes_future="9.0"  changes_future="9.0"
 thumbnail="http://www.netbsd.org/images/ports/evbarm/adi_brh.gif"  thumbnail="//www.netbsd.org/images/ports/evbarm/adi_brh.gif"
 about="""  about="""
 NetBSD/evbarm is the port of NetBSD to various evaluation and prototyping  NetBSD/evbarm is the port of NetBSD to various evaluation and prototyping
 boards based on CPUs implementing the ARM architecture. NetBSD/evbarm also  boards based on CPUs implementing the ARM architecture. NetBSD/evbarm also
Line 22  Matt Thomas is the maintainer of NetBSD/ Line 22  Matt Thomas is the maintainer of NetBSD/
   
 ### CPU types  ### CPU types
   
 The evbarm port can be built with a variety of CPU options.  There are  The evbarm port can be built with a variety of CPU options, corresponding to the
 three main variables: the instruction set, the endianness, and whether  [large array of ARM CPU architectures](https://en.wikipedia.org/wiki/ARM_architecture#Cores).
 there is hardware floating point.  By default the CPU type is "earm",  There are
 and this implies little endian (el when explicitly stated), and soft  four main variables: the word size, the instruction set, the
 (emulated) floating point.  Another example, suitable for Raspberry PI  endianness, and whether there is hardware floating point.  By default
 2, is earmv7hf, which is the v7 instruction set, little endian,  the CPU type is "earm", and this implies aarch32 (32-bit), earmv5 cpu
 and hardware floating point.  architecture, little endian (el when explicitly stated), and soft
   (Emulated) floating point.  Another example, suitable for Raspberry PI
   2, is earmv7hf, which is aarch32, the v7 instruction set, little
   endian, and hardware floating point.
   
 Typically, various boards are best compiled with a CPU type that  Typically, various boards are best compiled with a CPU type that
 matches the board's CPU and floating point support, but generally a  matches the board's CPU and floating point support, but generally a
 lower CPU instruction set version is workable on a newer board.  See  lower CPU instruction set version is workable on a newer board.  See
 build.sh and look for aliases for the evbarm port.  build.sh and look for aliases for the evbarm port.
   
 Some processors can operate as arm or the 64-bit ARM variant, aarch64, which is supported by  Through NetBSD 8, the evbarm port has supported exclusively the
 [[NetBSD/aarch64|aarch64]].  aarch32 (32-bit CPU) sub-family of the ARM architecture.  Some
   processors, such as many supporting the armv8 CPU architecture, also
   support a 64-bit instruction set, referred to as aarch64.  This is
   sometimes referred to as a distinct port, [[NetBSD/aarch64|aarch64]],
   with code in src/sys/arch/aarch64, but it is built as the evbarm port
   with aarch64 cpu type, and available as the alias evbarm64.
   
   Note that MACHINE_ARCH=aarch64 currently refers to the A64 instruction
   set and the aarch64 architecture, built for the armv8 architecture.
   (Note also that armv8 is the first architecture to support aarch64, so
   this will not be an issue until at least armv9.)
   
 ### Kernels and userland  ### Kernels and userland
   
Line 47  kernel for that board. Line 60  kernel for that board.
 ### anita and qemu  ### anita and qemu
   
 anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.  anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
  - evbarm-earmv7hf uses "qemu -M vexpress-a15"  
  - evbarm-aarch64 uses "qemu -M virt"   - evbarm-earmv7hf uses "qemu-system-arm -M vexpress-a15"
    - evbarm-aarch64 uses "qemu-system-aarch64 -M virt"
  - Information on how to test emulated versions of other specific hardware is welcome.   - Information on how to test emulated versions of other specific hardware is welcome.
   
 ### Board specific information  ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]   - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone and BeagleBone Black|BeagleBone]]   - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]]
  - [[NVIDIA Tegra|Tegra]]   - [[NVIDIA Tegra|Tegra]]
  - [[ODROID C1 and C1+|ODROID-C1]]   - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]   - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]

Removed from v.1.53  
changed lines
  Added in v.1.72


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