All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: David Kesselring <dkesselr@mmc.atmel.com>, linux-mips@linux-mips.org
Subject: Re: state of 64 bit support
Date: Mon, 9 Jun 2003 11:44:08 -0400	[thread overview]
Message-ID: <20030609154408.GA1781@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030609164009.2806n-100000@delta.ds2.pg.gda.pl>

On Mon, Jun 09, 2003 at 05:28:18PM +0200, Maciej W. Rozycki wrote:
> On Fri, 6 Jun 2003, David Kesselring wrote:
> 
> > I've been trying to get a 64 bit compiler working for a 5kc/5kf core,
> > searching the net for info, and following this list for the last couple of
> > weeks. I have not been able to get some basic questions answered and I
> > hope that some of you can help me.
> 
>  With the above statement I assume you want to have a compiler suitable
> for a kernel build only (which is easier to get running) and you do not
> need to do 64-bit userland builds (which is tougher).  And that you want a
> cross-compiler.
> 
> > First what is the current status of mips 5k 64bit little-endian support
> > for gcc? Do I have to use 2.95/2.96? I don't think there is a linux binary
> > but if you know of one I'd love the link. I have been unsuccessful getting
> > this built.
> 
>  There are a few gcc 2.95.x i386/Linux LE binary RPM packages available at
> my site, but they have preliminary R4k workarounds applied which have
> disadvantageous side effects for later processors.  Your best bet is to
> get an RPM source package, disable R4k patches and rebuild. 
> 
> > On the web, there is a howto to build a mipsel gcc 3.2. Does 3.2 support
> > 64 bit mips? Has anyone gotten it to work?
> 
>  If going for version 3.x, you probably want to get 3.3.  I can't say if
> it supports MIPS64/Linux without patching -- probably yes.

More or less yes (kernel space).  Userspace went in to 3.4.

> 
> > Also linux. From my understanding, kernel 2.4.20 has the latest patches
> > for mips32 and mips64. Is that a valid codebase?
> 
>  Up till now most development was done based on 2.4.x, but Ralf has just
> finished updating 2.5.x, so you can select the version that suits you
> best.

... But you have to get it from the linux-mips.org CVS, not from
kernel.org!  Just clarifying.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-06-09 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 16:55 state of 64 bit support David Kesselring
2003-06-09 15:28 ` Maciej W. Rozycki
2003-06-09 15:44   ` Daniel Jacobowitz [this message]
2003-06-09 17:37     ` Building a stand-alone FS on a very limited flash (newbie question) Baruch Chaikin
2003-06-09 17:37       ` Baruch Chaikin
2003-06-09 16:56       ` Thiemo Seufer
2003-06-10 12:26         ` Johannes Stezenbach
2003-06-10 12:38         ` Wolfgang Denk
2003-06-10 12:56           ` Thiemo Seufer
2003-06-10 13:15             ` Wolfgang Denk
2003-06-15 15:47               ` Baruch Chaikin
2003-06-15 15:47                 ` Baruch Chaikin
2003-06-17 12:16                 ` Johannes Stezenbach
2003-06-09 18:49       ` Jeff Baitis
2003-06-09 19:01         ` Jeff Baitis

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=20030609154408.GA1781@nevyn.them.org \
    --to=dan@debian.org \
    --cc=dkesselr@mmc.atmel.com \
    --cc=linux-mips@linux-mips.org \
    --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 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.