config: Use booti instead of bootz on 64-bit ARM
PATCH 1/1 config: Use booti instead of bootz on 64-bit ARM
From: Thierry Reding <[email protected]>
The bootz command doesn't work with Linux kernel images on 64-bit ARM. The replacement command with the same interface and functionality is booti.
--- include/config_distro_defaults.h | 4 ++++ 1 file changed, 4 insertions(+)
include/config_distro_defaults.h +4 -0
@@ -31,7 +31,11 @@#define CONFIG_OF_LIBFDT +#ifdef CONFIG_ARM64 +#define CONFIG_CMD_BOOTI +#else #define CONFIG_CMD_BOOTZ +#endif #define CONFIG_CMD_DHCP #define CONFIG_CMD_ELF #define CONFIG_CMD_EXT2
Signature · 1 line
2.3.2
PATCH 1/1 config: Use booti instead of bootz on 64-bit ARM
Quoted 5 lines · Thierry Reding
From: Thierry Reding <[email protected]>
The bootz command doesn't work with Linux kernel images on 64-bit ARM. The replacement command with the same interface and functionality is booti.
Uggh. Why can't bootz work everywhere, or why can't bootz be an alias to booti on ARM64? Are the command-line parameters different? It'd be really nice to be able to create one boot.scr.uimg file that just works everywhere, and having different command names will scupper that.
PATCH 1/1 config: Use booti instead of bootz on 64-bit ARM
Quoted 7 lines · Stephen Warren
Quoted 5 lines · Thierry Reding
From: Thierry Reding <[email protected]>
The bootz command doesn't work with Linux kernel images on 64-bit ARM. The replacement command with the same interface and functionality is booti.
Quoted 5 lines
Uggh. Why can't bootz work everywhere, or why can't bootz be an alias to booti on ARM64? Are the command-line parameters different? It'd be really nice to be able to create one boot.scr.uimg file that just works everywhere, and having different command names will scupper that.
So, a long while back I asked about maybe adding a "bootSOMETHING-THAT-GUESSES-YOUR-FORMAT" command to help here. The issue is that "bootz" means "boot an ARM Linux Kernel with the kernel's decompressor that's at the front". It's not even (sadly, arg) what "boot an x86 Linux Kernel with the kernel's decompressor that's at the front" is, that's zboot. In the kernel (today), there's no desire to add the decompressor "arm" has to "aarch64" and instead leave decompression to the loader (And compression to the user). So we have to handle the Image format that aarch64 uses.
Frankly I've always looked at the distro work here as the "boot-do-what-I-mean" stuff where we hide that the common multi-platform image types aren't popular and just let people boot the "normal" kernel for their architecture.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150320/948004f6/attachment.sig>
PATCH 1/1 config: Use booti instead of bootz on 64-bit ARM
Quoted 24 lines · Tom Rini
Quoted 7 lines · Stephen Warren
Quoted 5 lines · Thierry Reding
From: Thierry Reding <[email protected]>
The bootz command doesn't work with Linux kernel images on 64-bit ARM. The replacement command with the same interface and functionality is booti.
Quoted 5 lines
Uggh. Why can't bootz work everywhere, or why can't bootz be an alias to booti on ARM64? Are the command-line parameters different? It'd be really nice to be able to create one boot.scr.uimg file that just works everywhere, and having different command names will scupper that.
So, a long while back I asked about maybe adding a "bootSOMETHING-THAT-GUESSES-YOUR-FORMAT" command to help here. The issue is that "bootz" means "boot an ARM Linux Kernel with the kernel's decompressor that's at the front". It's not even (sadly, arg) what "boot an x86 Linux Kernel with the kernel's decompressor that's at the front" is, that's zboot. In the kernel (today), there's no desire to add the decompressor "arm" has to "aarch64" and instead leave decompression to the loader (And compression to the user). So we have to handle the Image format that aarch64 uses.
Quoted 4 lines
Frankly I've always looked at the distro work here as the "boot-do-what-I-mean" stuff where we hide that the common multi-platform image types aren't popular and just let people boot the "normal" kernel for their architecture.
Ah yes, I guess that's true. A hypothetical universal "boot this image" function would be nice to enable everywhere. IIRC, bootm does some image format detection (uimage vs. FIT) so perhaps it could just grow the ability to boot anything?
I suppose it isn't too hard for a distro to detect ARM vs. ARM64 vs. x86 and select bootz/booti/zboot for those cases, so long as all boards of an architecture are consistent.
Quoted 9 lines · Thierry Reding
From: Thierry Reding <[email protected]>
The bootz command doesn't work with Linux kernel images on 64-bit ARM. The replacement command with the same interface and functionality is booti.
Cc Dennis Gilmore <[email protected]>Cc Tom Rini <[email protected]>Signed-off-by Thierry Reding <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150328/e853d2c8/attachment.sig>