[BACK]Return to arm64.html CVS log [TXT][DIR] Up to [local] / www
File: [local] / www / arm64.html (download) (as text)

Revision 1.9, Tue May 2 18:25:33 2017 UTC (7 years ago) by kettenis
Branch: MAIN
Changes since 1.8: +12 -6 lines 

Mention Firefly-RK3399.

<!DOCTYPE HTML PUBLIC  "-//W3C//DTD HTML 4.01 Transitional//EN"
	"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>OpenBSD/arm64</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="the OpenBSD/arm64 page">
<meta name="copyright" content="This document copyright 2017 by OpenBSD.">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/arm64.html">
</head>

<body bgcolor="#ffffff" text="#000000" link="#23238e">

<h2>
<a href="index.html">
<font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
<font color="#e00000">arm64</font>
</h2>
<hr>

<p>
OpenBSD/arm64 is a port of OpenBSD to various 64-bit ARM based systems.
</p>

<p>
A mailing list for ARM-based ports is available at
<u><font color="#23238e">arm@openbsd.org</font></u>.
To join the OpenBSD/arm mailing list, send a message body of
<b>"subscribe arm"</b> to
<a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>.
Please be sure to check our <a href="mail.html">mailing list policy</a> before
subscribing.

<br clear=all>
<hr>

<a name="status"></a>
<h3><font color="#0000e0"><strong>Current status</strong></font></h3>

<p>
The current target platforms are Firefly-RK3399, Pine64, Raspberry Pi
3 and Opteron A1100.
</p>

<p>
The Pine64 currently requires an image based on a non-redistributable
boot0 file from Allwinner to be installed on the system disk.  This
will hopefully be resolved by a replacement in a future U-Boot
release.  The install media does not include these boot images or a
Pine64 device tree.  For similar reasons we do not provide install
media for the Firefly-RK3399 either.
</p>

<p>
The Raspberry Pi 3 requires closed but redistributable files on the
system disk to load into the VC4 GPU which starts the ARM cores.
By default the boot ROM will only try to load these files off an SD card.
These files are present in the install media but there is no driver
for SD/MMC yet so a USB disk drive and manual steps are required.
To load the firmware off the SD card and have the root disk on USB
after installing OpenBSD reboot and interrupt U-Boot before the timeout
expires and instruct U-Boot to prefer USB over the SD card:
</p>

<blockquote><pre>
Hit any key to stop autoboot:  0
U-Boot&gt; setenv boot_targets usb0 mmc0 pxe dhcp
U-Boot&gt; saveenv
U-Boot&gt; boot
</pre></blockquote>

<p>
Opteron A1100 machines on the other hand come with a UEFI firmware
that includes a device tree and can boot off SATA or USB devices without
board specific boot files on the system disk.
<p>

<a name="hardware"></a>
<h3><font color="#0000e0"><strong>Supported hardware</strong></font></h3>

<p>
OpenBSD/arm64 bundles various platforms sharing the 64-bit ARM
architecture. Due to the fact that there are many System on a
Chips (SoC) around, OpenBSD/arm64 differentiates between various
SoCs and may have a different level of support between them.
</p>

<ul>
	<li>Allwinner A64
	<ul>
		<li>Pine64
	</ul>
	<li>AMD Opteron A1100 (Seattle)
	<ul>
		<li>AMD Seattle Development Board
		<li>SoftIron OverDrive 1000
		<li>SoftIron OverDrive 3000
	</ul>
	<li>Broadcom BCM2837
	<ul>
		<li>Raspberry Pi 3
	</ul>
	<li>Rockchip RK3399
	<ul>
		<li>Firefly-RK3399
	</ul>
</ul>

<h4>Ethernet</h4>
<ul>
	<li><a href="http://man.openbsd.org/?query=smsc&amp;sektion=4&amp;arch=arm64">smsc(4)</a>
	  integrated SMSC LAN95xx 10/100 USB Ethernet on <tt>Raspberry Pi 3</tt></li>
	<li><a href="http://man.openbsd.org/?query=msk&amp;sektion=4&amp;arch=arm64">msk(4)</a>
	  integrated Marvell Yukon-2 10/100/Gigabit Ethernet on <tt>OverDrive 1000</tt></li>
</ul>

<h4>Storage</h4>
<ul>
	<li><a href="http://man.openbsd.org/?query=ahci&amp;sektion=4&amp;arch=arm64">ahci(4)</a>
	  on <tt>Opteron A1100</tt></li>
</ul>

<h4>USB</h4>
<ul>
	<li><a href="http://man.openbsd.org/?query=dwctwo&amp;sektion=4&amp;arch=arm64">dwctwo(4)</a>
	  on <tt>Raspberry Pi 3</tt></li>
	<li><a href="http://man.openbsd.org/?query=ehci&amp;sektion=4&amp;arch=arm64">ehci(4)</a>
	  on <tt>Pine64</tt> and <tt>Firefly-RK3399</tt></li>
	<li><a href="http://man.openbsd.org/?query=xhci&amp;sektion=4&amp;arch=arm64">xhci(4)</a>
	  on <tt>OverDrive 1000</tt></li>
</ul>

<b>No real time clock:</b> Many of the arm64 devices do not have a
battery-backed real time clock. For this reason, using the <tt>-s</tt>
option of <a href="faq/faq8.html#OpenNTPD">OpenNTPD</a> may be desirable.

<a name="install"></a>
<h3><font color="#0000e0">
<strong>Getting and installing</strong>
</font></h3>

<p>
Snapshots are made available from time to time, in
<a href="https://ftp.OpenBSD.org/pub/OpenBSD/snapshots/arm64">this location</a>
as well as in a few
<a href="ftp.html">mirrors</a>.
Here are the
<a href="https://ftp.OpenBSD.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64">
OpenBSD/arm64 snapshot installation instructions</a> as well.
</p>

</body>
</html>