All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, dan@debian.org, linux-mips@linux-mips.org,
	ralf@linux-mips.org
Subject: Re: RFC: Sentosa boot fix
Date: Mon, 29 Jan 2007 18:32:48 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64N.0701291829280.26916@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <20070130.011442.21365159.anemo@mba.ocn.ne.jp>

On Tue, 30 Jan 2007, Atsushi Nemoto wrote:

> >  Well, the option used to select between 64-bit and 32-bit ELF for 
> > building 64-bit configurations.  I can see it has been changed from its 
> > original meaning and it now only controls whether "-mno-explicit-relocs" 
> > is passed to the compiler or not, which is sort of useless and certainly 
> > does not match the intent nor what the description says.  The 64-bit 
> > format is now used unconditionally and you can always pass such obscure 
> > options to the compiler on the make's command line, so instead of this fix 
> > I vote for complete removal of the BUILD_ELF64 option.
> 
> Though I do not know much about -mno-explicit-relocs,
> CONFIG_BUILD_ELF64 controls -msym32 option and this is the reason of
> the tweak in __pa_page_offset().

 I missed this bit, sorry.  Then the original note applies -- the setting 
of BUILD_ELF64 is whatever suits one building the kernel the best.  And 
certainly for binaries built to run from CKSEG0 either value of 
BUILD_ELF64 is reasonable.

  Maciej

  parent reply	other threads:[~2007-01-29 18:33 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 [this message]
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
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=Pine.LNX.4.64N.0701291829280.26916@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dan@debian.org \
    --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 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.