wikisrc/ports/evbarm.mdwn - diff

Return to evbarm.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / ports

Diff for /wikisrc/ports/evbarm.mdwn between versions 1.71 and 1.79

-version 1.71, 2019/06/02 13:32:38
+version 1.79, 2019/06/27 17:29:39
  Line 18  boards based on CPUs implementing the AR
  supports some specific embedded system products based on prototype board
  designs.
- Matt Thomas is the maintainer of NetBSD/evbarm.
  ### CPU types
  The evbarm port can be built with a variety of CPU options, corresponding to the
- Line 51  set and the aarch64 architecture, built
+ Line 49  set and the aarch64 architecture, built
  (Note also that armv8 is the first architecture to support aarch64, so
  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" suffix.  Unless otherwise noted, all use the A32 or
- aarch32 instruction set.
- [[!table data=<<EOT
- MACHINE_ARCH |bits | ARM architecture version            |ABI
- arm          |32   |\todo ?                              |oabi
- earm         |32   |alias for earmv5 (\todo why?)        |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 in aarch64 mode                |\todo ? eabi
- EOT]]
- \todo Explain why, if we have armv5, 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
- The evbarm userland can be used on any system that can run code of the
- CPU type used for the build.  Typically, a particular board requires a
- kernel for that board.
  ### 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.
- Line 111  anita can be used to test builds.  (In a
+ Line 57  anita can be used to test builds.  (In a
   - evbarm-aarch64 uses "qemu-system-aarch64 -M virt"
   - Information on how to test emulated versions of other specific hardware is welcome.
+ ### invisible.ca builds
+ NetBSD developer Jared McNeill provides [builds of NetBSD-current for a vast variety of hardware.](https://www.invisible.ca/arm/)   In addition to the standard build, these images have board-specific uboot contents.  See also /usr/pkgsrc/sysutils/u-boot*.
  ### Board specific information
   - [[Allwinner sunxi family SoCs|Allwinner]]
   - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]]
- Line 118  anita can be used to test builds.  (In a
+ Line 68  anita can be used to test builds.  (In a
   - [[ODROID C1 and C1+|ODROID-C1]]
   - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
- """
+ ### SSH configuration for installtion
+ The default configuration will connect to the local network via DHCP and
+ run an SSH server. In order to use the SSH server, we must configure
+ users. This can be done by writing to the SD card's MS-DOS partition.
+ Create a creds.txt file and use:
+            useradd user password
+ <!--TODO: Additional configuration options are available on creds_msdos.8-->
+ """
  supported_hardware="""
- **NOTE**: This list is incomplete. For a full list of configurations, please see the [evbarm kernel configs](http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/evbarm/conf/) directory in CVS.
+ **NOTE**: This list is incomplete. For a full list of boards, please see the [GENERIC DTS files](http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/arch/evbarm/conf/GENERIC).
  [[!toc startlevel=3]]

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

Removed from v.1.71
changed lines
	Added in v.1.79