From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: macro@linux-mips.org, dan@debian.org, vagabon.xyz@gmail.com,
linux-mips@linux-mips.org
Subject: Re: RFC: Sentosa boot fix
Date: Tue, 30 Jan 2007 15:18:42 +0000 [thread overview]
Message-ID: <20070130151841.GA31405@linux-mips.org> (raw)
In-Reply-To: <20070130.234537.126574565.anemo@mba.ocn.ne.jp>
On Tue, Jan 30, 2007 at 11:45:37PM +0900, Atsushi Nemoto wrote:
> On Mon, 29 Jan 2007 18:47:12 +0000 (GMT), "Maciej W. Rozycki" <macro@linux-mips.org> wrote:
> > I have BUILD_ELF64 enabled for my SWARM configuration and I do not plan
> > to change it. If there is a bug in the definition of __pa_page_offset()
> > for such a setup it should be fixed indeed.
>
> Though I do not object to remove "&& !defined(CONFIG_BUILD_ELF64)"
> from __pa_page_offset(), are there any point of CONFIG_BUILD_ELF64=y
> if your load address was CKSEG0?
Code in CKSEG0 allows shorter a shorter code sequence for address loads.
Yet some machines such as IP27 require 64-bit ELF for booting.
Ralf
next prev parent reply other threads:[~2007-01-30 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 18:08 RFC: Sentosa boot fix Daniel Jacobowitz
2007-01-29 9:59 ` Franck Bui-Huu
2007-01-29 15:46 ` Maciej W. Rozycki
2007-01-29 16:14 ` Atsushi Nemoto
2007-01-29 16:27 ` Franck Bui-Huu
2007-01-30 16:41 ` Atsushi Nemoto
2007-01-30 17:56 ` Maciej W. Rozycki
2007-01-29 18:07 ` Thiemo Seufer
2007-01-29 18:32 ` Maciej W. Rozycki
2007-01-29 18:09 ` Thiemo Seufer
2007-01-29 15:52 ` Daniel Jacobowitz
2007-01-29 16:06 ` Franck Bui-Huu
2007-01-29 16:14 ` Daniel Jacobowitz
2007-01-29 18:47 ` Maciej W. Rozycki
2007-01-30 14:45 ` Atsushi Nemoto
2007-01-30 15:18 ` Ralf Baechle [this message]
2007-01-30 17:33 ` Maciej W. Rozycki
2007-02-01 9:51 ` Franck Bui-Huu
2007-02-01 13:20 ` Maciej W. Rozycki
2007-02-01 14:31 ` Atsushi Nemoto
2007-02-01 14:36 ` Atsushi Nemoto
2007-02-01 15:59 ` Franck Bui-Huu
2007-02-08 15:49 ` Maciej W. Rozycki
2007-02-08 16:36 ` Franck Bui-Huu
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=20070130151841.GA31405@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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.