From: Ralf Baechle <ralf@linux-mips.org>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>, davem@davemloft.net
Subject: Re: [RFC] [IP22] parsing PROM variables at startup
Date: Tue, 13 Oct 2009 22:40:29 +0200 [thread overview]
Message-ID: <20091013204029.GC727@linux-mips.org> (raw)
In-Reply-To: <90edad820910131330t67d6b293o150bef62aec0c5eb@mail.gmail.com>
On Tue, Oct 13, 2009 at 11:30:29PM +0300, Dmitri Vorobiev wrote:
> >> I tried booting a few kernels, ranging from 2.2.1 to the current Linus
> >> Git, on my IP22s using an ecoff image directly, without the help of
> >> arcboot or tip22. It turns out that during many years (at least, since
> >> the times of late 2.4 series) the sizes of ecoff images have been so
> >> big that ARCS was not capable of reading the kernel images. Therefore,
> >> I'd like to claim that it's safe to assume that at least from now on,
> >> nobody is ever going to boot ecoffs on IP22 whatsoever, and arcboot
> >> and tip22 remain the only way to load Linux on an IP22 machine.
> >
> > Only the very oldest IP22 firmware does not support ELF files. In practice
> > those seem to be very rare - I never encountered one - and Linux
> > distributions are shipping a 2nd stage bootloader, so there never has
> > been much of a need for booting ECOFF, at least not on Indy.
>
> That is, it's safe to assume that it's either a 32-bit ELF or a 2nd
> stage bootloader that gets loaded by the firmware.
Yes. The IP22 firmware does not support 64-bit ELF, so 64-bit kernels
have to be converted to 32-bit ELF for booting first. The vmlinux.32
target does that.
Ralf
prev parent reply other threads:[~2009-10-13 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 17:55 [RFC] [IP22] parsing PROM variables at startup Dmitri Vorobiev
2009-10-13 19:58 ` Ralf Baechle
2009-10-13 20:30 ` Dmitri Vorobiev
2009-10-13 20:40 ` Ralf Baechle [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=20091013204029.GC727@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-mips@linux-mips.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).