Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: JP Foster <jp.foster@exterity.co.uk>
To: Peter Popov <ppopov@embeddedalley.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Big Endian au1550
Date: Thu, 24 Feb 2005 17:09:26 +0000	[thread overview]
Message-ID: <1109264967.8690.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050224161542.74749.qmail@web203.biz.mail.re2.yahoo.com>

>2.95 is too old. We're using 3.3.3 and binutils 2.15.
>We're working on making a toolkit available soon, or
>you can try ELDK3.0.
>

Thanks I'll try that. Thanks to everyone for all their help and advice.
I *WILL* get this built. It usually isn't this hard :)

-- 
jp.foster@exterity.co.uk
Digital Simplicity

  reply	other threads:[~2005-02-24 17:09 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 [this message]
2005-02-25 17:29               ` JP Foster
2005-02-24 16:19             ` Clem Taylor
  -- 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=1109264967.8690.3.camel@localhost.localdomain \
    --to=jp.foster@exterity.co.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@embeddedalley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox