Lower entry barrier for arm64 development
cover Lower entry barrier for arm64 development
Hi,
So I got this far after many hours of scratching my head. Let's make EXT4, VIRTIO_MMIO, and VIRTIO_BLK part of the default configuration so users have a pleasant ride when attempting to run their freshly built AArch64 kernel. My boot wrapper has diverged from Catalin's quite significantly [1], and it works well for me. I intend to address more papercuts in future patches.
Thanks.
[1]: https://github.com/artagnon/boot-wrapper-aarch64
Ramkumar Ramachandra (2):
arm64: include EXT4 in defconfig
arm64: include VIRTIO_{MMIO,BLK} in defconfig
arch/arm64/configs/defconfig | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
Signature · 1 line
1.8.4.477.g4cae6f5
PATCH 1/2 arm64: include EXT4 in defconfig
Most readily available root filesystems are formatted as EXT4 these days. For example, see the raring rootfs that the Debian folk is preparing [1].
[1]: http://people.debian.org/~wookey/bootstrap/rootfs/
--- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
@@ -72,6 +72,7 @@ CONFIG_LOGO=y # CONFIG_IOMMU_SUPPORT is not set CONFIG_EXT2_FS=y CONFIG_EXT3_FS=y +CONFIG_EXT4_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set # CONFIG_EXT3_FS_XATTR is not set CONFIG_FUSE_FS=y
Signature · 1 line
1.8.4.477.g4cae6f5
PATCH 2/2 arm64: include VIRTIO_{MMIO,BLK} in defconfig
In reply to Ramkumar RamachandraCurrently, development on arm64 is aided by a Foundation_v8 emulator distributed by ARM [1]. To run their kernels, users will execute:
$ ./Foundation_v8 --image linux-system.axf --block-device raring-rootfs
To mount the raring-rootfs filesystem, the kernel parameter should typically include:
root=/dev/vda
For this device to be present, the kernel must be compiled with VIRTIO_{MMIO,BLK}. To make this work out-of-the-box, make it part of the default configuration.
[1]: https://silver.arm.com/browse/FM00A
--- arch/arm64/configs/defconfig | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/arm64/configs/defconfig +3 -1
@@ -42,7 +42,7 @@ CONFIG_IP_PNP_BOOTP=y # CONFIG_WIRELESS is not set CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_DEVTMPFS=y -# CONFIG_BLK_DEV is not set +CONFIG_BLK_DEV=y CONFIG_SCSI=y # CONFIG_SCSI_PROC_FS is not set CONFIG_BLK_DEV_SD=y
@@ -91,3 +91,5 @@ CONFIG_DEBUG_KERNEL=y CONFIG_DEBUG_INFO=y # CONFIG_FTRACE is not set CONFIG_ATOMIC64_SELFTEST=y +CONFIG_VIRTIO_MMIO=y +CONFIG_VIRTIO_BLK=y
Signature · 1 line
1.8.4.477.g4cae6f5
Quoted 7 lines · Ramkumar Ramachandra
So I got this far after many hours of scratching my head. Let's make EXT4,
VIRTIO_MMIO, andVIRTIO_BLKpart of the default configuration so users have a pleasant ride when attempting to run their freshly built AArch64 kernel. My boot wrapper has diverged from Catalin's quite significantly [1], and it works well for me. I intend to address more papercuts in future patches.
Quoted 7 lines
Thanks.
[1]: https://github.com/artagnon/boot-wrapper-aarch64
Ramkumar Ramachandra (2):
arm64: include EXT4 in defconfig
arm64: include VIRTIO_{MMIO,BLK} in defconfig
Thanks. Both patches applied.
Signature · 1 line
Catalin