summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjsg <jsg@openbsd.org>2016-07-23 16:22:17 +0000
committerjsg <jsg@openbsd.org>2016-07-23 16:22:17 +0000
commite3b182c737625a185b73d01d466b3de6840806bc (patch)
tree8c41cf52b0835f1e8076306f25f74f3edc3daa1e
parentBack out the dhclient BPF change. There are DHCP servers out there which (diff)
downloadwireguard-openbsd-e3b182c737625a185b73d01d466b3de6840806bc.tar.xz
wireguard-openbsd-e3b182c737625a185b73d01d466b3de6840806bc.zip
Some armv7 machines are shipped with linux images that run USB OTG ports
in client mode and provide serial access to a getty and networking. Make it clear that a real serial console that can interact with the firmware is required. Suggested by and wording tweaks from ian@
-rw-r--r--distrib/notes/armv7/prep8
1 files changed, 7 insertions, 1 deletions
diff --git a/distrib/notes/armv7/prep b/distrib/notes/armv7/prep
index c9738dd950b..4743c22be9d 100644
--- a/distrib/notes/armv7/prep
+++ b/distrib/notes/armv7/prep
@@ -1,7 +1,13 @@
-dnl $OpenBSD: prep,v 1.9 2016/07/09 07:19:52 jsg Exp $
+dnl $OpenBSD: prep,v 1.10 2016/07/23 16:22:17 jsg Exp $
Please be aware that OpenBSD support for this platform is far from
complete.
+To perform an installation you must be able to interact with the serial
+console of the machine. USB OTG ports such as the one found on the
+BeagleBone will not function as a console. You need to be able to
+interact with the firmware on the console. Often this requires a 3.3V
+TTL level adapter connected to pins or a header on the board.
+
Firmware which provides an EFI interface with a Device Tree Blob (DTB)
file is required to boot. In most cases this is provided by images of
U-Boot 2016.07 or newer on SD/MMC devices or in SPI flash. If the