The ARM coreboot target supports multiple boards, but they are all built
using the same object path. The only difference in target boards is done
in mkimage to determine the load address.
Currently, mkimage is looking at a board specific path
(/usr/lib/grub/arm-coreboot-vexpress) for modules while it installs it
at a non-specific path (/usr/lib/grub/arm-coreboot).
So let's sync the two up again and tell mkimage to look for coreboot
modules at a board agnostic path, syncing it up with all other targets.
Signed-off-by: Alexander Graf <ag...@csgraf.de>
Reviewed-by: Daniel Kiper <daniel.ki...@oracle.com>
---
util/mkimage.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/util/mkimage.c b/util/mkimage.c
index 37d6249f1..f1a9c9c86 100644
--- a/util/mkimage.c
+++ b/util/mkimage.c
@@ -553,7 +553,7 @@ static const struct grub_install_image_target_desc
image_targets[] =
},
/* For coreboot versions that don't support self-relocating images. */
{
- .dirname = "arm-coreboot-vexpress",
+ .dirname = "arm-coreboot",
.names = { "arm-coreboot-vexpress", NULL },
.voidp_sizeof = 4,
.bigendian = 0,
@@ -572,7 +572,7 @@ static const struct grub_install_image_target_desc
image_targets[] =
.link_addr = 0x62000000,
},
{
- .dirname = "arm-coreboot-veyron",
+ .dirname = "arm-coreboot",
.names = { "arm-coreboot-veyron", NULL },
.voidp_sizeof = 4,
.bigendian = 0,
--
2.16.4
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
