Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Clem Taylor <clem.taylor@gmail.com>
To: JP Foster <jp.foster@exterity.co.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: Big Endian au1550
Date: Thu, 24 Feb 2005 11:19:51 -0500	[thread overview]
Message-ID: <ecb4efd105022408199abf2c3@mail.gmail.com> (raw)
In-Reply-To: <1109239495.8389.8.camel@localhost.localdomain>

> Great, but I still can't get a running kernel from cvs mips-linux for
> a DB1550 board. Is it perhaps the toolchain? I'm using gcc-3.4.1 perhaps
> that is too recent.
> 
> Tried mipsel last night and got the same result as big end so I suspect
> it may be my compiler/binutils combination. Is there are recommended
> toolchain for mips. Should I go build gcc-2.95 and binutils 2.12 ?

I'm not sure about mipseb, but I've used both crosstool and buildroot
to build toolchains to compile a mipsel 2.6.10 kernel for the
DBAu1550. The kernel is the linux-mips cvs head from a few weeks ago.
Right now I'm using gcc 3.4.3 and binutils 2.15.94.0.2 20041220 that
was built with a recent buildroot checkout.

When I first tried to compile the 2.6.10 I was using
crosstool-0.28-rc37 and I ran into some binutils issues. I ended up
using gcc-3.4.1-glibc-2.3.2 with binutils-050110 (I'm not sure where I
got that). When I switched to buildroot I was able to use the latest
tools it had support for.

                                --Clem

  parent reply	other threads:[~2005-02-24 16:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 11:22 Big Endian au1550 JP Foster
2005-02-23 11:23 ` Ralf Baechle
     [not found] ` <000301c5199d$3154ad40$0300a8c0@Exterity.local>
2005-02-23 12:05   ` JP Foster
2005-02-23 13:17     ` Ralf Baechle
2005-02-23 15:03     ` Dan Malek
2005-02-23 15:06       ` Ralf Baechle
2005-02-23 17:02         ` Dan Malek
2005-03-04 20:23           ` Ralf Baechle
2005-03-04 20:44             ` Dan Malek
2005-02-23 16:57       ` Thomas Sailer
2005-02-23 17:47         ` Pete Popov
     [not found]         ` <000001c519d1$84d9c250$0300a8c0@Exterity.local>
2005-02-24 10:04           ` JP Foster
2005-02-24 16:15             ` Peter Popov
2005-02-24 17:09               ` JP Foster
2005-02-25 17:29               ` JP Foster
2005-02-24 16:19             ` Clem Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 18:30 Prashant Viswanathan
2005-04-28  2:14 Prashant Viswanathan
2005-04-28  2:23 ` Manish Lachwani
2005-04-28  3:44 Prashant Viswanathan
2005-04-28  3:57 ` ppopov
2005-04-28  8:56   ` JP
2005-04-28 18:18 Prashant Viswanathan

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=ecb4efd105022408199abf2c3@mail.gmail.com \
    --to=clem.taylor@gmail.com \
    --cc=jp.foster@exterity.co.uk \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox