summaryrefslogtreecommitdiff
path: root/distrib/notes/arm64
diff options
context:
space:
mode:
authorPatrick Wildt <patrick@cvs.openbsd.org>2017-01-25 02:29:26 +0000
committerPatrick Wildt <patrick@cvs.openbsd.org>2017-01-25 02:29:26 +0000
commitad596d04a4436767918cdccac8be9e73caae9ee1 (patch)
treeaa9ec981f10be87b0cf4d99e2d3158cb2346876b /distrib/notes/arm64
parent7b0f0047f8d6149c308cb3c969a4723bbe92ee21 (diff)
Copy install notes for arm64 from armv7. These still need to be
modified to make sense for arm64.
Diffstat (limited to 'distrib/notes/arm64')
-rw-r--r--distrib/notes/arm64/contents56
-rw-r--r--distrib/notes/arm64/features40
-rw-r--r--distrib/notes/arm64/hardware41
-rw-r--r--distrib/notes/arm64/install47
-rw-r--r--distrib/notes/arm64/prep87
-rw-r--r--distrib/notes/arm64/upgrade2
-rw-r--r--distrib/notes/arm64/whatis6
-rw-r--r--distrib/notes/arm64/xfer13
8 files changed, 292 insertions, 0 deletions
diff --git a/distrib/notes/arm64/contents b/distrib/notes/arm64/contents
new file mode 100644
index 00000000000..408276846f3
--- /dev/null
+++ b/distrib/notes/arm64/contents
@@ -0,0 +1,56 @@
+dnl $OpenBSD: contents,v 1.1 2017/01/25 02:29:25 patrick Exp $
+TopPart
+
+ miniroot-am335x-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; BeagleBone version.
+
+ miniroot-beagle-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; BeagleBoard version.
+
+ miniroot-cubie-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; Cubieboard2 version.
+
+ miniroot-cubox-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; CuBox-i version.
+
+ miniroot-nitrogen-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; Nitrogen6x version.
+
+ miniroot-panda-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; PandaBoard (ES) version.
+
+ miniroot-wandboard-{:--:}OSrev.fs
+ A miniroot filesystem to be used for
+ installation; Wandboard version.
+
+OpenBSDdistsets
+
+OpenBSDbsd
+
+OpenBSDrd
+dnl not yet...
+dnl OpenBSDcd
+
+DistributionDescription(eight)
+
+OpenBSDbase(59810834,166146114)
+
+OpenBSDcomp(49060908,148496717)
+
+OpenBSDgame(2677213,6022047)
+
+OpenBSDman(10062290,39102681)
+
+OpenBSDxbase(12620198,33609128)
+
+OpenBSDxfont(39938719,52169245)
+
+OpenBSDxserv(5945263,14963812)
+
+OpenBSDxshare(4411475,24366232)
diff --git a/distrib/notes/arm64/features b/distrib/notes/arm64/features
new file mode 100644
index 00000000000..3a463871059
--- /dev/null
+++ b/distrib/notes/arm64/features
@@ -0,0 +1,40 @@
+dnl $OpenBSD: features,v 1.1 2017/01/25 02:29:25 patrick Exp $
+dnl
+dnl This file lists almost all the conditional features of this port,
+dnl which are used to provide accurate installation notes.
+dnl
+dnl Information about the installer script features should be in sync with
+dnl src/distrib/arm64/ramdisk/install.md
+dnl and the list files in
+dnl src/distrib/arm64/ramdisk/list
+dnl
+dnl ====
+dnl
+dnl architecture name (for the packages directory)
+define({:-MACHINE_ARCH-:},arm)dnl
+dnl
+dnl define if /sbin/kbd exists on the media
+define({:-MDKBD-:},)dnl
+dnl
+dnl define if serial consoles needs to be enabled in /etc/ttys
+dnl (i.e. md_consoleinfo is not empty)
+define({:-MDSERCONS-:},)dnl
+dnl
+dnl define if SMP kernels are provided
+define({:-MDSMP-:},)dnl
+dnl
+dnl define if shared libraries are provided
+define({:-MDSO-:},1)dnl
+dnl
+dnl define if some media have timezone information (TZ in their list)
+define({:-MDTZ-:},1)dnl
+dnl
+dnl define if glass console is possible
+dnl (XXX does not imply availablity of X servers though)
+define({:-MDX-:},)dnl
+dnl
+dnl define if the X server can't start until machdep.allow_aperture is set
+define({:-MDXAPERTURE-:},)dnl
+dnl
+dnl define if the X server can start without a configuration file
+define({:-MDXDM-:},)dnl
diff --git a/distrib/notes/arm64/hardware b/distrib/notes/arm64/hardware
new file mode 100644
index 00000000000..aa749f6453f
--- /dev/null
+++ b/distrib/notes/arm64/hardware
@@ -0,0 +1,41 @@
+dnl $OpenBSD: hardware,v 1.1 2017/01/25 02:29:25 patrick Exp $
+The following machines are targeted by OpenBSD/MACHINE:
+
+ BeagleBoard, BeagleBoard xM
+ Supported on-board devices:
+ standard serial port (com)
+ watchdog controller (omdog)
+ GPIO controller (omgpio)
+
+ BeagleBone, BeagleBone Black
+ Supported on-board devices:
+ standard serial port (com)
+ watchdog controller (omdog)
+ Ethernet controller (cpsw)
+ GPIO controller (omgpio)
+
+ PandaBoard (ES)
+ Supported on-board devices:
+ standard serial port (com)
+ USB controller (ehci)
+ watchdog controller (omdog)
+ GPIO controller (omgpio)
+
+ Cubieboard, pcDuino
+ Supported on-board devices:
+ standard serial port (com)
+ watchdog controller (sxidog)
+ Ethernet controller (sxie)
+ USB controller (ehci)
+ AHCI controller (ahci)
+ GPIO controller (sxipio)
+
+ SABRE Lite, Nitrogen6X, Wandboard, CuBox-i4Pro, Utilite, Novena
+ Supported on-board devices:
+ standard serial port (com)
+ USB controller (ehci)
+ watchdog controller (imxdog)
+ Ethernet controller (fec)
+ GPIO controller (imxgpio)
+ OTP controller (imxocotp)
+ AHCI controller (ahci)
diff --git a/distrib/notes/arm64/install b/distrib/notes/arm64/install
new file mode 100644
index 00000000000..660ff83ae93
--- /dev/null
+++ b/distrib/notes/arm64/install
@@ -0,0 +1,47 @@
+dnl $OpenBSD: install,v 1.1 2017/01/25 02:29:25 patrick Exp $
+OpenBSDInstallPrelude
+
+OpenBSDInstallPart2
+
+OpenBSDInstallPart3(,"sd0")
+
+OpenBSDInstallPart4
+
+OpenBSDInstallMBRPart1
+
+dnl OpenBSDInstallMBRPart2(indeed)
+ The fdisk(8) utility will be invoked to let you edit your MBR
+ partitioning. The current MBR partitions defined will be
+ displayed and you will be allowed to modify them, and add new
+ partitions.
+
+ The setup will need two partitions, one 'OpenBSD' for the
+ OpenBSD/MACHINE installation, and one 'MSDOS' for the
+ U-Boot scripts/bootloader.
+
+ If you use the whole disk option, the install script
+ will create a small 'MSDOS' partition and use the rest of
+ the disk for the OpenBSD installation.
+
+ After your OpenBSD MBR partition has been setup, the real
+ partition setup can follow.
+
+OpenBSDInstallPart5
+
+OpenBSDInstallPart6({:-CD-ROM, -:})
+
+OpenBSDURLInstall
+
+OpenBSDCDROMInstall
+
+OpenBSDDISKInstall(,,{:-, Linux (ext2) or MS-DOS-:})
+
+OpenBSDCommonInstall
+
+OpenBSDInstallWrapup
+
+OpenBSDCongratulations
+
+
+
+OpenBSDUnattendedInstallation
diff --git a/distrib/notes/arm64/prep b/distrib/notes/arm64/prep
new file mode 100644
index 00000000000..2919b58c25a
--- /dev/null
+++ b/distrib/notes/arm64/prep
@@ -0,0 +1,87 @@
+dnl $OpenBSD: prep,v 1.1 2017/01/25 02:29:25 patrick 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
+miniroot images are used, U-Boot and DTB files are distributed as part
+of the miniroot disk images.
+
+OpenBSD can be installed onto a disk by copying the miniroot for your
+board "miniroot-board-{:--:}OSrev.fs" image to an SD card.
+
+Booting from an SD card:
+
+ To use the miniroot image you will need another machine to plug the
+ SD card in to. Any machine type will do, as long as it supports SD card
+ storage devices. Under OpenBSD, it will appear as a ``sd'' device, for
+ example sd1.
+
+ Use the dd(1) utility to copy the miniroot to the hard drive.
+ The command would likely be, under OpenBSD:
+ dd if=miniroot-beagle-{:--:}OSrev.fs of=/dev/rsd1c
+
+ When you have connected the BeagleBoard to you computer, a command such
+ as "cu -l cuaU0 -s 115200" (assuming cuaU0 is your serial port device)
+ should connect you to the board's console.
+
+ Note: By default the BeagleBone Black will boot from the internal emmc.
+ In order to make it boot from the micro SD card, you will need to hold down
+ the small button located by the SD card slot while powering on the board.
+ Once you have done this the board will boot from the SD card as the default.
+
+Running EFI payloads with U-Boot:
+
+If the U-Boot target supports "distro_bootcmd" efiboot will automatically
+be loaded by placing bootarm.efi into /efi/boot/bootarm.efi on a FAT
+filesystem. With dtb files placed in in /, /dtbs/, or /dtb/current/.
+
+If the U-Boot target supports bootefi but not automatically finding it with
+"distro_bootcmd" then it must be loaded manually or by U-Boot commands or
+script.
+ => run findfdt
+ => load mmc 0:1 ${fdt_addr_r} ${fdtfile}
+ => load mmc 0:1 ${kernel_addr_r} efi/boot/bootarm.efi
+ => bootefi ${kernel_addr_r} ${fdt_addr_r}
+The bootloader will then run and try to load sd0a:/bsd off an FFS
+filesystem after a timeout.
+
+Install on systems without a supported miniroot:
+
+ If a miniroot is not available for your system you will have to modify
+ an existing image before booting it.
+
+ To do so first install the u-boot-arm and dtb packages. Write one of the
+ provided miniroot images to an SD card:
+
+ dd if=miniroot-beagle-{:--:}OSrev.fs of=/dev/rsdXc
+
+ Add a board specific DTB file:
+
+ mount /dev/sdXi /mnt
+ cp /usr/local/share/dtb/arm/board.dtb /mnt/
+ umount /mnt
+
+ For systems based on Texas Instruments OMAP and AMxxxx SoCs:
+
+ mount /dev/sdXi /mnt
+ cp /usr/local/share/u-boot/board/{MLO,u-boot.img} /mnt/
+ umount /mnt
+
+ For systems based on Freescale/NXP i.MX SoCs:
+
+ dd if=/usr/local/share/u-boot/board/SPL of=/dev/rsdXc bs=1024 seek=1
+ dd if=/usr/local/share/u-boot/board/u-boot.img \
+ of=/dev/rsdXc bs=1024 seek=69
+
+ For systems based on Allwinner Axx Socs:
+
+ dd if=/usr/local/share/u-boot/board/u-boot-sunxi-with-spl.bin \
+ of=/dev/rsdXc bs=1024 seek=8
diff --git a/distrib/notes/arm64/upgrade b/distrib/notes/arm64/upgrade
new file mode 100644
index 00000000000..db748fc076b
--- /dev/null
+++ b/distrib/notes/arm64/upgrade
@@ -0,0 +1,2 @@
+dnl $OpenBSD: upgrade,v 1.1 2017/01/25 02:29:25 patrick Exp $
+OpenBSDUpgrade({:-your usual boot device-:})
diff --git a/distrib/notes/arm64/whatis b/distrib/notes/arm64/whatis
new file mode 100644
index 00000000000..f0e4855ba18
--- /dev/null
+++ b/distrib/notes/arm64/whatis
@@ -0,0 +1,6 @@
+dnl $OpenBSD: whatis,v 1.1 2017/01/25 02:29:25 patrick Exp $
+
+OpenBSD/MACHINE runs on the BeagleBoard and newer xM models, as well as
+PandaBoard, PandaBoard ES, BeagleBone, BeagleBone Black, SABRE Lite,
+Nitrogen6X, Wandboard, CuBox-i4Pro, Utilite and Novena. Hardware support is
+currently limited, but this port is a heavy work in progress.
diff --git a/distrib/notes/arm64/xfer b/distrib/notes/arm64/xfer
new file mode 100644
index 00000000000..5a76a87d9ce
--- /dev/null
+++ b/distrib/notes/arm64/xfer
@@ -0,0 +1,13 @@
+dnl $OpenBSD: xfer,v 1.1 2017/01/25 02:29:25 patrick Exp $
+
+Installation is supported from several media types, including:
+
+ CD-ROM
+ FFS partitions
+ DOS (FAT) partitions
+ EXT2 partitions
+ HTTP
+
+OpenBSDXferShortPrelude
+
+OpenBSDXferFFS