Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
	Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: RFC: Sentosa boot fix
Date: Mon, 29 Jan 2007 10:52:54 -0500	[thread overview]
Message-ID: <20070129155253.GA2070@nevyn.them.org> (raw)
In-Reply-To: <cda58cb80701290159m5eed331em5945eac4a602363a@mail.gmail.com>

On Mon, Jan 29, 2007 at 10:59:37AM +0100, Franck Bui-Huu wrote:
> Hi,
> 
> On 1/28/07, Daniel Jacobowitz <dan@debian.org> wrote:
> >The problem is __pa_symbol(&_end); the kernel is linked at
> >0xffffffff80xxxxxx, so subtracting a PAGE_OFFSET of 0xa800000000000000
> >does not do anything useful to this address at all.
> >
> 
> In my understanding, if your kernel is linked at 0xffffffff80xxxxxx,
> you shouldn't have CONFIG_BUILD_ELF64 set.

What Maciej said.  But also: please compare the description of
CONFIG_BUILD_ELF64 with the targets that link at that address.
Almost every supported target links at that address, except for
IP27.  How do any of them work today?

config BUILD_ELF64
        bool "Use 64-bit ELF format for building"
        depends on 64BIT
        help
          A 64-bit kernel is usually built using the 64-bit ELF binary object
          format as it's one that allows arbitrary 64-bit constructs.  For
          kernels that are loaded within the KSEG compatibility segments the
          32-bit ELF format can optionally be used resulting in a somewhat
          smaller binary, but this option is not explicitly supported by the
          toolchain and since binutils 2.14 it does not even work at all.

          Say Y to use the 64-bit format or N to use the 32-bit one.

          If unsure say Y.


% grep load- arch/mips/Makefile | grep ffffffff8 | wc
     55     165    2743

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2007-01-29 15:56 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 [this message]
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
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=20070129155253.GA2070@nevyn.them.org \
    --to=dan@debian.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox