[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Call to grub_file_read fails in grub_multiboot_load_elf64

From: Chris Plant
Subject: Re: Call to grub_file_read fails in grub_multiboot_load_elf64
Date: Mon, 11 May 2020 16:09:56 +0100
User-agent: Evolution 3.30.5-1.1

Hello Daniel,

Firstly, I want to apologise, because as is nearly always the case,
when I've gone away and looked at this more closely, most of the
problems I've encountered (this one included) are my fault, this was a
mismatch between two macros.  I've now got grub booting the OS happily
with the appropriate Multiboot2 tags.

Secondly, why not EFI for ARM?  I'm playing around with GNU Mach (why? 
Lockdown!) on a Raspberry Pi 3, and initially I was using no

However, as my project/time consumer moved on I needed GRUB to keep
things more ARM64 general and to provide various things that align
better with the i386 version of Mach.

When I'm happy with the code, and I've managed to get into the GRUB
coding standards, I'll submit a patch for people to tear to pieces, but
it basically just enables Multiboot2 on ARM64, with the associated
cpu_relocator code that is required.  

With regards to the Multiboot2 specification for ARM64, I'll document
this within the patch, but it's very similar to the MIPS registers at
the moment.


On Mon, 2020-05-11 at 16:39 +0200, Daniel Kiper wrote:
> Adding Leif and Ard,
> On Sun, May 03, 2020 at 09:17:50PM +0100, Chris Plant via Grub-devel
> wrote:
> > Hello,
> > 
> > I'm fairly new to grub coding, and I'm trying to get multiboot2
> > working
> > on the arm64-efi target for an OS project. However, I'm running up
> > against an issue with a call to grub_file_read from
> > grub_multiboot_load_elf64 around line 170 in multiboot_elf.c.  This
> > causes a synchronous error (esr 0x96000045) which is a Data Abort
> > caused by a translation error in the level 1 table during a write.
> > 
> > At first I thought it was that the load address in the ELF header
> > (this
> > is used as a "target" in the relocator_alloc_chunk_addr) was the
> > issue,
> > but tweaking that around doesn't seem to change any issue.
> > 
> > Does anyone have any experience with the ARM64-EFI target or the
> > multiboot2 code who could help me understand where the issue is?
> First of all, why cannot you use EFI loader for ARM? There is no
> the Multiboot2 specification for ARM...
> Daniel
> _______________________________________________
> Grub-devel mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]