Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@oss.sgi.com
Subject: Re: New binutils for kernel
Date: Tue, 20 Aug 2002 17:17:35 +0200	[thread overview]
Message-ID: <20020820171735.A24832@linux-mips.org> (raw)
In-Reply-To: <20020820151135.GA23807@nevyn.them.org>; from dan@debian.org on Tue, Aug 20, 2002 at 11:11:35AM -0400

On Tue, Aug 20, 2002 at 11:11:35AM -0400, Daniel Jacobowitz wrote:

> > > > Well, I think 2.13's a good idea, but it's very new.  I'd say that was
> > > > acceptable as long as you're looking at MIPS64 only, not at MIPS32. 
> > > 
> > > Such considerations have kept us back at antique levels of binutils.  And
> > > juggling with several different versions for userland, and two kernel
> > > flavours is evil ...
> > 
> >  Any version since 2.11, possibly older, should work just fine for 32-bit
> > MIPS.  I don't think there are any significant interface changes between
> > 2.11 and 2.13, so if 2.13 works then 2.11 will not bail out either.  Thus
> > there is no need to force 2.13 for 32-bit MIPS, but I think it is
> > acceptable to stop caring about versions older than 2.11 in the nearby
> > future.
> 
> Sure.

Sounds like we'll then recommend 2.13 for the fearless and 64-bit developers
and 2.11 for everybody else.

  Ralf

  reply	other threads:[~2002-08-20 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020819171238.A7457@linux-mips.org>
     [not found] ` <Pine.GSO.3.96.1020820161204.8700H-100000@delta.ds2.pg.gda.pl>
2002-08-20 14:29   ` New binutils for kernel Ralf Baechle
2002-08-20 14:50     ` Daniel Jacobowitz
2002-08-20 14:58       ` Ralf Baechle
2002-08-20 15:02         ` Daniel Jacobowitz
2002-08-20 15:08         ` Maciej W. Rozycki
2002-08-20 15:11           ` Daniel Jacobowitz
2002-08-20 15:17             ` Ralf Baechle [this message]
2002-08-20 15:10         ` H. J. Lu
2002-08-20 17:27     ` Karsten Merker

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=20020820171735.A24832@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dan@debian.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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