From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 7/7] Add support for ARM UEFI ("EFI") platforms
Date: Tue, 09 Apr 2013 19:30:46 +0200 [thread overview]
Message-ID: <51645046.6070403@gmail.com> (raw)
In-Reply-To: <20130404125414.GP23069@rocoto.smurfnet.nu>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On 04.04.2013 14:54, Leif Lindholm wrote:
> On Wed, Apr 03, 2013 at 10:01:59PM +0200, Vladimir '??-coder/phcoder' Serbinenko wrote:
>>> I don't see grub-mkimage currently being fully cross-platform anyway,
>>> so I would (as mentioned in previous email) prefer to postpone any
>>> such adjustments until the basic support is in. I have the patches
>>> for it, if not entirely up to date.
>>
>> grub-mkimage is fully cross-platform and is intended to be usable this
>> way. If you see a problem, please tell.
>
> Well, the straightforward relocations for EM_386 and EM_X86_64 look OK,
> but much of the fiddly IA64 patching that goes on in grub-mkimagexx.c
> (add_value_to_slot_* and make_trampoline) does not appear
> endianess-safe to me.
>
Fixed
> Since I didn't want to have to duplicate my relocation handling
> between kernel and grub-mkimage, I use kern/arm/dl.c for both.
>
Could you move the common functions to dl_helper.c as in ISA64?
> In order to do that in an endianess-safe way, I need to be able to
> export target platform information over there, as well as the
> host_to_target/target_to_host macros. This would involve moving these
> macros, as well as the struct image_target_desc definition, out of
> grub-mkimage.c.
Is big-endian ARM of any interest at all? I was under impression that it
was limited to few devices and not supported by either u-boot or EFI.
You still have grub_le_to_cpu / grub_cpu_to_le
>
> However, this would also make it possible to do the same for IA64,
> and get rid of some code duplication between grub-mkimagexx.c and
> kern/ia64/dl.c.
>
I already did. For IA64 I simply used le_to_cpu/cpu_to_le as ia64-efi is
always little-endian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-04-09 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 17:01 [PATCH 7/7] Add support for ARM UEFI ("EFI") platforms Leif Lindholm
2013-04-01 2:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 10:41 ` Francesco Lavra
2013-04-01 11:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 14:10 ` Francesco Lavra
2013-04-01 14:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 14:49 ` Francesco Lavra
2013-04-03 17:50 ` Leif Lindholm
2013-04-01 16:24 ` Francesco Lavra
2013-04-03 18:07 ` Leif Lindholm
2013-04-03 20:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-04 12:54 ` Leif Lindholm
2013-04-09 17:30 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-05-09 18:08 ` Leif Lindholm
2013-05-11 8:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-11 18:00 ` Francesco Lavra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51645046.6070403@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=leif.lindholm@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).