[BACK]Return to evbarm.mdwn CVS log [TXT] [DIR] Up to [NetBSD Developer Wiki] / wikisrc / ports

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

version 1.60, 2018/11/22 01:18:49 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 27  The evbarm port can be built with a vari Line 27  The evbarm port can be built with a vari
 There are  There are
 four main variables: the word size, the instruction set, the  four main variables: the word size, the instruction set, the
 endianness, and whether there is hardware floating point.  By default  endianness, and whether there is hardware floating point.  By default
 the CPU type is "earm", and this implies aarch32 (32-bit), \todo cpu  the CPU type is "earm", and this implies aarch32 (32-bit), earmv5 cpu
 architecture, little endian (el when explicitly stated), and soft  architecture, little endian (el when explicitly stated), and soft
 (Emulated) floating point.  Another example, suitable for Raspberry PI  (Emulated) floating point.  Another example, suitable for Raspberry PI
 2, is earmv7hf, which is aarch32, the v7 instruction set, little  2, is earmv7hf, which is aarch32, the v7 instruction set, little
Line 51  set and the aarch64 architecture, built  Line 51  set and the aarch64 architecture, built 
 (Note also that armv8 is the first architecture to support aarch64, so  (Note also that armv8 is the first architecture to support aarch64, so
 this will not be an issue until at least armv9.)  this will not be an issue until at least armv9.)
   
 #### ABI types  
   
 There are two basic ABIs on ARM.  One, called oabi, assumed a  
 particular kind of hardware floating point (FPA).  This results in  
 faulting any floating-point instructions for kernel emulation on a  
 vast number of CPus, which is very slow.  A newer one, called eabi,  
 has two variants.  Both have stricter alignment rules, tending to 8  
 byte rather than 4 bytes for 8-byte types (but actually read the specs  
 if you care).  The one without "hf" emulates floating point without  
 causing traps/emulation, and "hf" uses VFP instructions, which are  
 present on modern CPUs. See the  
 [TS-7200](https://wiki.embeddedarm.com/wiki/EABI_vs_OABI) and  
 [Debian](https://wiki.debian.org/ArmEabiPort) documentation.  
   
 Now, EABI is normal, and OABI is crufty.  The only real reason NetBSD  
 retains OABI support is binary compatibility with older releases.  The  
 "arm" and "armeb" MACHINE_ARCH targets are OABI; the rest of the  
 targets, all having "earm" are EABI.  
   
 \todo CHECK THIS: The "aarch64" MACHINE_ARCH target is an EABI variant.  
   
 ### Relationship of MACHINE_ARCH to official ARM terminology  
   
 Note that these are all little endian, and have big endian variants  
 with a "eb" sufix.     
   
 [[!table data=\"\"\\"  
 MACHINE_ARCH |bits | ARM architecture version            |ABI  
 arm          |32   |?                                    |oabi  
 earm         |32   |armv4 (effectively an alias)         |eabi  
 earmv4       |32   |armv4 (no thumb, so ok on strongarm) | eabi  
 earmv5       |32   |armv5t                               |eabi  
 earmv6       |32   |armv6                                |eabi  
 earmv7       |32   |armv7                                |eabi  
 aarch64      |64   |armv8                                |\todo ? eabi  
 \"\"\"]]  
   
 \todo Explain why, if we have armv4, and this is confusing, we still have earm as a MACHINE_ARCH.  
   
 \todo Explain why aarch64 is a MACHINE_ARCH, when it seems like it  
 should be something like armv8hf_64.  
   
 \todo Explain if MACHINE_ARCH values correspond to a particular  
 argument to some CPU selection command in gcc (and/or clang).  
   
 ### Kernels and userland  ### Kernels and userland
   
 The evbarm userland can be used on any system that can run code of the  The evbarm userland can be used on any system that can run code of the
Line 112  anita can be used to test builds.  (In a Line 67  anita can be used to test builds.  (In a
   
 ### 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.60  
changed lines
  Added in v.1.72

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