On Sat, Mar 25, 2023 at 08:36:06PM +0100, Mark Kettenis wrote:
> > From: Klemens Nanni <k...@openbsd.org>
> > We must not throw away all errors, dd(1) can be silenced properly.
Same for the other ARM.
> 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.
Or is this firmware copying obsolete as well?
I have no hardware or clue about armv7.
Diff below just makes potential dd(1) erros visible.
Alternatively, those special cases would go along with firmware files from
install media, in analogy to the arm64 suggestion.
Index: ramdisk/install.md
===================================================================
RCS file: /cvs/src/distrib/armv7/ramdisk/install.md,v
retrieving revision 1.52
diff -u -p -r1.52 install.md
--- ramdisk/install.md 19 Feb 2022 08:33:28 -0000 1.52
+++ ramdisk/install.md 27 Mar 2023 19:27:11 -0000
@@ -64,9 +64,9 @@ md_installboot() {
cubox|wandboard)
cp $_mdec/*.dtb /mnt/mnt/
dd if=$_mdec/SPL of=${_disk}c bs=1024 seek=1 \
- >/dev/null 2>&1
+ status=none
dd if=$_mdec/u-boot.img of=${_disk}c bs=1024 seek=69 \
- >/dev/null 2>&1
+ status=none
;;
nitrogen)
cp $_mdec/*.dtb /mnt/mnt/
@@ -82,7 +82,7 @@ md_installboot() {
cubie)
cp $_mdec/*.dtb /mnt/mnt/
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
;;
esac
