grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Lavra <francescolavra.fl@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Andrey Borzenkov <arvidjaar@gmail.com>, leif.lindholm@linaro.org
Subject: Re: ARM how-to?
Date: Sun, 21 Jul 2013 15:48:18 +0200	[thread overview]
Message-ID: <51EBE6A2.6060707@gmail.com> (raw)
In-Reply-To: <20130721125721.0bb6b7f2@opensuse.site>

On 07/21/2013 10:57 AM, Andrey Borzenkov wrote:
> В Thu, 18 Jul 2013 18:47:11 +0100
> Leif Lindholm <leif.lindholm@linaro.org> пишет:
> 
>> On 18 July 2013 17:58, Andrey Borzenkov <arvidjaar@gmail.com> wrote:
>>> Could someone provide simple steps how to actually use ARM port? As I
>>> understand core.img need to be installed as payload for native
>>> bootloader, right? Is it supported by grub-install or needs manual
>>> intervention?
>>
>> If you are using the u-boot port, you need to manually tell u-boot
>> where to find and load the image.
>>
>> There is a little bit of documentation on the Linaro wiki:
>> https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB
>> https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOT
>>
> 
> Does restriction about non-relocatable core.img still apply?

Yes.

Please note that to have support for device tree working correctly you
may need to replace the file grub-core/lib/fdt.c in the ARM branch with
the file I sent to the list on April 7th (see
http://lists.gnu.org/archive/html/grub-devel/2013-04/msg00086.html).
The patch I posted earlier today is needed too.

Regards,
Francesco


      reply	other threads:[~2013-07-21 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 16:58 ARM how-to? Andrey Borzenkov
2013-07-18 17:47 ` Leif Lindholm
2013-07-21  8:57   ` Andrey Borzenkov
2013-07-21 13:48     ` Francesco Lavra [this message]

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=51EBE6A2.6060707@gmail.com \
    --to=francescolavra.fl@gmail.com \
    --cc=arvidjaar@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).