From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 4/7] Support for ARM/U-Boot platforms
Date: Tue, 09 Apr 2013 19:26:57 +0200 [thread overview]
Message-ID: <51644F61.6040804@gmail.com> (raw)
In-Reply-To: <20130409102613.GU23069@rocoto.smurfnet.nu>
[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]
>> Trouble is that grub-install now rightfully warns about the lack of
>> platform-specific install.
>> What do we have to do to register the image at u-boot?
>> Put it in specific location?
>
> EFI provides three very nice things:
> - Standardised partition and filesystem type for bootloaders.
> - Standardised runtime services for updating selected boot image.
> - Standardised "removable media" bootloader path.
>
> U-Boot has neither, and different platforms use different mechanisms to
> affect boot images - some "prime" the enviroment with a uEnv.txt, some
> search around a predefined set of filesystems for boot scripts, some
> require you to manually "setenv" from within U-Boot.
Is environment stored in flash?
>
> Debian use a special package called flash-kernel to abstract these things
> away.
>
Can we use it?
> So in short, I think the only sane thing grub-install can do for arm-uboot,
> is what I already have it do - generate an image with the required modules
> embedded.
If that's the only thing we do, then the warning should be kept.
> Now, maybe it shouldn't be grub/arm-uboot/core.img, but that was
> what I ended up using.
>
I'd prefer to keep this file and make a copy if necessarry.
>> Also you spoke about relocatable image but AFAICT header always
>> specifies load address. Do you have a way around it?
>
> Well, it's not so much a way around it as somthing that almost ampounts
> to a new port (certainly a new image type).
> The proper fix would be to generate it as an ELF image _instead_, and use
> U-Boot's ELF loader support to load it properly.
>
It's not really a new port. We already have ports using several image
formats, e.g. i386-pc, sparc64-ieee1275, mips-loongson.
Doesn't U-boot terminate services if it loads an ELF? How good is its
ELF support? Does it handle relocations correctly? If it doesn't we can
use -fPIC for kernel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-04-09 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 17:01 [PATCH 4/7] Support for ARM/U-Boot platforms Leif Lindholm
2013-04-01 2:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 9:53 ` Francesco Lavra
2013-04-01 11:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 14:29 ` Francesco Lavra
2013-04-03 10:29 ` Leif Lindholm
2013-04-03 16:32 ` Leif Lindholm
2013-04-08 10:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-09 10:26 ` Leif Lindholm
2013-04-09 17:26 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-04-09 0:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-09 11:39 ` Leif Lindholm
2013-04-09 11:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-09 12:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=51644F61.6040804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.