All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
To: "Daniel Jacobowitz" <dan@debian.org>
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 17:06:39 +0100	[thread overview]
Message-ID: <cda58cb80701290806p5d68ba5ck5e3e3b2b3490126f@mail.gmail.com> (raw)
In-Reply-To: <20070129155253.GA2070@nevyn.them.org>

On 1/29/07, Daniel Jacobowitz <dan@debian.org> wrote:
> On Mon, Jan 29, 2007 at 10:59:37AM +0100, Franck Bui-Huu wrote:
> > 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?
>

Surely because none of them define CONFIG_BUILD_ELF64:

        $ git grep BUILD_ELF arch/mips/configs
        arch/mips/configs/bigsur_defconfig:# CONFIG_BUILD_ELF64 is not set
        arch/mips/configs/ip27_defconfig:# CONFIG_BUILD_ELF64 is not set
        arch/mips/configs/ip32_defconfig:# CONFIG_BUILD_ELF64 is not set
        arch/mips/configs/ocelot_c_defconfig:# CONFIG_BUILD_ELF64 is not set
        arch/mips/configs/ocelot_g_defconfig:# CONFIG_BUILD_ELF64 is not set
        arch/mips/configs/sb1250-swarm_defconfig:# CONFIG_BUILD_ELF64 is not set

-- 
               Franck

  reply	other threads:[~2007-01-29 16:06 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 [this message]
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=cda58cb80701290806p5d68ba5ck5e3e3b2b3490126f@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 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.