Each script is designed to be run from within this directory, and aren't made to be
particularly user serviceable.  Ordinarily you won't want to run these scripts, but
if you fancy it, here's what they do:

You would run them in this order:

uboot.build
```````````
  This will download the U-Boot source and build binaries for each of the supported
  devices.
  It'll create a number of xz-compressed ".bin" files within ../bin/

sdcards.build
`````````````````````
  This creates an "image" file for each ARM device type, that can be written to
  the SD card that is used to boot the device from cold.

  Each image contains:
  1) The U-Boot boot loader that the device will use as its initial boot console.

  2) One partition:

  1 x FAT for U-Boot's enviroment and any scripts (Slackware ARM provides no scripts, but
  perhaps may in the future).  The reason for the FAT partition is so that when you
  save the U-Boot environment (using 'saveenv' within the U-Boot console - as documented
  in the Slackware ARM installation documentation - will write those settings to this
  partition).

  Once run, the "../bin/" directory will contain a U-Boot ".bin" and an SD card image
  for each supported ARM device, with symlinks to make it easy to reference them from within
  documentation.  e.g. for the "Orange Pi":-

      The 'SD card' images:
        orangepi.sdcard_latest.img.xz
        orangepi.u-boot-v2019.04-rc1_1_sdcard.img.xz

      The U-Boot binaries:
        orangepi.u-boot-latest.bin.xz
        orangepi.u-boot-v2019.04-rc1_1.bin.xz

Some useful references
========================
http://linux-sunxi.org/Xunlong_Orange_Pi_Plus
http://linux-sunxi.org/Bootable_SD_card#Cleaning
UART:
https://forum.armbian.com/index.php/topic/1524-orange-pi-one-how-to-enable-uart/

Making a u-boot SD card
http://www.orangepi.org/Docs/Makingabootable.html

-- 
Stuart Winter
<mozes@slackware.com>
15-Feb-2019