> Date: Sat, 25 Mar 2023 16:32:17 +0000
> From: Klemens Nanni <k...@openbsd.org>
>
> We must not throw away all errors, dd(1) can be silenced properly.
>
> OK?
>
> I don't have the hardware to test, but will need to tweak this MD code soon
> for get softraid installs working on those boards.
To be honest I think we should remove this from the installer scripts.
This code tries to handle the case where we've just whacked the disk
we've booted from since we're trying to install on it. My current
advice to people is to put the "system" firmware on a different disk
than the OS (e.g. the firmware on uSD and the OS on USB). This only
tries to handle the pine64. The only thing that sets pine64 apart
from many other boards is that it was the first board we ran on.
If we want to have support for updating the "system" firmware, we
probably should follow the apple model, where we handle this in
installboot. But the we probably should do a better job at curating
these firmwares. At this point I'm not even confident the firmware we
ship for pine64 actually works. We've basically stopped updating the
u-boot package because each update broke a subset of the boards we
supported.
> Index: ramdisk/install.md
> ===================================================================
> RCS file: /cvs/src/distrib/arm64/ramdisk/install.md,v
> retrieving revision 1.36
> diff -u -p -r1.36 install.md
> --- ramdisk/install.md 6 Feb 2023 08:41:00 -0000 1.36
> +++ ramdisk/install.md 25 Mar 2023 16:28:50 -0000
> @@ -66,7 +66,7 @@ md_installboot() {
> ;;
> pine64)
> dd if=$_mdec/u-boot-sunxi-with-spl.bin of=${_disk}c \
> - bs=1024 seek=8 >/dev/null 2>&1
> + bs=1024 seek=8 status=none
> ;;
> rpi)
> mount ${MOUNT_ARGS_msdos} ${_disk}i /mnt/mnt
>
>
