Fixed typos.

Since boot partition detect is done by u-boot, there is no change in kernel part table, so mmcblk0 will be boot device in any case
OLIMEX · Dec 7, 2018 · 672fff7 · 672fff7
1 parent eb4506d
commit 672fff7
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/SOFTWARE/A64-TERES/scripts/configuration-files/fstab b/SOFTWARE/A64-TERES/scripts/configuration-files/fstab
@@ -1,3 +1,3 @@
 # <file system>	<dir>	<type>	<options>			<dump>	<pass>
-/dev/mmcblk1p1	/boot	vfat	defaults			0		2
-/dev/mmcblk1p2	/		ext4	defaults,noatime	0		1
+/dev/mmcblk0p1	/boot	vfat	defaults			0		2
+/dev/mmcblk0p2	/		ext4	defaults,noatime	0		1
diff --git a/SOFTWARE/A64-TERES/scripts/install_kernel.sh b/SOFTWARE/A64-TERES/scripts/install_kernel.sh
@@ -91,7 +91,7 @@ selinux=permissive
 enforcing=0
 optargs=no_console_suspend
 kernel_filename=a64/Image
-initrd_filename=ramdisk.img
+initrd_filename=initrd.img
 recovery_initrd_filename=ramdisk-recovery.img
 hardware=sun50iw1p1