Return to evbarm.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / ports

Update for the 9.2 release

    1: [[!template id=port
    2: port="evbarm"
    3: port_alt="arm"
    4: port_var1="earmv6hf"
    5: port_var2="earmv7hf"
    6: port_var3="earmv7hfeb"
    7: port_var4="aarch64"
    8: port_var_install_notes="evbarm-earm"
    9: pkg_rel="9.0"
   10: cur_rel="9.2"
   11: future_rel="10.0"
   12: changes_cur="9.0"
   13: changes_future="10.0"
   14: thumbnail="//wiki.netbsd.org/ports/evbarm/images/beaglebone.jpg"
   15: about="""
   16: NetBSD/evbarm is the port of NetBSD to various systems based on chips
   17: implementing the ARM architecture. The "evb" component is a reference
   18: to evaluation boards, the original target of the port. However, the
   19: single GENERIC/GENERIC64 kernel now supports a range of machines including
   20: development boards, virtual machines, "ServerReady" (SBBR/SBSA) hardware,
   21: and laptops through both device tree and ACPI based booting.
   22: """
   23: supported_hardware="""
   24: ### CPU types
   25: 
   26: Various CPU variants are supported, e.g:
   27: 
   28: - evbarm-earmv6hf - ARMv6-A with EABI and hardware floating point, e.g.
   29:   the original Raspberry Pi.
   30: - evbarm-earmv7hf - ARMv7-A with EABI and hardware floating point, e.g.
   31:   most recent and common 32-bit ARM boards.
   32: - evbarm-earmv7hfeb - Same as the above, but with the CPU running in
   33:   big endian mode.
   34: - evbarm-aarch64 - 64-bit ARMv8-A
   35: - evbarm-aarch64eb - Same as the above, but with the CPU running in
   36:   big endian mode.
   37: 
   38: Since NetBSD 9.0, 64-bit ARM processors are supported (referred to here
   39: as aarch64). These run with fully 64-bit kernels and userland. Running
   40: 32-bit ARM binaries is also supported with `compat32`. The 64-bit
   41: kernel supports up to 256 CPUs and the 32-bit kernel supports up to 8.
   42: 
   43: Since NetBSD 9.0, there is support for symmetric and asymmetrical
   44: multiprocessing (aka big.LITTLE).
   45: 
   46: evbarm variants are little endian unless otherwise stated. NetBSD provides
   47: big endian images primarily for testing purposes and to ensure that the code
   48: is endian-clean.
   49: 
   50: ### Board specific information (often including installation information)
   51: 
   52:  - [[Allwinner sunxi family SoCs|Allwinner]]
   53:  - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]]
   54:  - [[NVIDIA Tegra|Tegra]]
   55:  - [[ODROID C1 and C1+|ODROID-C1]]
   56:  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
   57:  - [[RockChip SoCs|RockChip]]
   58:  - [[Terasic DE0 Nano-SoC|Cyclone5]]
   59: 
   60: **NOTE**: This list is incomplete. For a full list of supported device tree
   61: based boards, please see the list of
   62: [32-bit](https://github.com/NetBSD/src/blob/netbsd-9/sys/arch/evbarm/conf/GENERIC#L18) and
   63: [64-bit](https://github.com/NetBSD/src/blob/netbsd-9/sys/arch/evbarm/conf/GENERIC64#L20) device trees.
   64: 
   65: ### QEMU
   66: 
   67: See the [[NetBSD/evbarm under QEMU|qemu_arm]] page for instructions on how to get started with QEMU.
   68: """
   69: additional="""
   70: ### armbsd.org builds
   71: 
   72: NetBSD developer Jared McNeill provides [builds of NetBSD 9 and -current for a vast variety of hardware.](https://www.armbsd.org/)   In addition to the standard build, these images have board-specific U-Boot contents.  See also /usr/pkgsrc/sysutils/u-boot*.
   73: 
   74: ### SSH configuration
   75: 
   76: The default configuration will connect to the local network via DHCP and
   77: run an SSH server.
   78: In order to use the SSH server, we must configure users.
   79: This can be done by writing to the SD card's MS-DOS partition.
   80: 
   81: Create a creds.txt file and use:
   82: 
   83:            useradd user password
   84: 
   85: See [creds_msdos(8)](https://man.NetBSD.org/creds_msdos.8) for
   86: additional configuration options.
   87: 
   88: ### anita
   89: 
   90: 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.
   91: 
   92:  - evbarm-earmv7hf uses 'qemu-system-arm -M vexpress-a15'
   93:  - evbarm-aarch64 uses 'qemu-system-aarch64 -M virt'
   94:  - Information on how to test emulated versions of other specific hardware is welcome.
   95: """
   96: ]]
   97: 
   98: [[!tag tier1port]]