From: Brady Brown <bbrown@ti.com>
To: Nicu Popovici <octavp@isratech.ro>
Cc: linux-mips@oss.sgi.com
Subject: Re: Atlas Board!
Date: Thu, 26 Oct 2000 14:34:30 -0600 [thread overview]
Message-ID: <39F89556.582FD0B@ti.com> (raw)
In-Reply-To: 39F828B2.A662A568@isratech.ro
Nicu Popovici wrote:
> Hello ,
>
> I want to ask few questions about an Atlas board. Who has such a board
> maybe will give me some tips to have an working Linux on that machine.
>
> 1. What type of RAM do I need ?
> 2. I want to cross - compile the CVS linux kernel for Mips but I failed
> on a i686. Could anyone tell me if I try to compile the kernel on Atlas
> board I will succeed.
>
We have linux running on several Atlas boards here. We are Cross-Compiling
the kernel successfully on an Intel machine. The cross tools we are
currently using are:
binutils-mipsel-linux-2.8.1-1
egcs-c++-mipsel-linux-1.0.3a-2
egcs-g77-mipsel-linux-1.0.3a-2
egcs-mipsel-linux-1.0.3a-2
egcs-libstdc++-mipsel-linux-2.8.0-2
egcs-objc-mipsel-linux-1.0.3a-2
These are available at
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mipsel-linux/
Note: the binutils version 2.9.5-1 gave us some problems when we tried it
so we are still using 2.8.1-1
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Brady Brown (bbrown@ti.com) Work:(801)619-6103
Texas Instruments: Broadband Access Group
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2000-10-26 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 12:50 Atlas Board! Nicu Popovici
2000-10-26 7:15 ` Kevin D. Kissell
2000-10-26 7:15 ` Kevin D. Kissell
2000-10-26 20:34 ` Brady Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-29 20:49 ATLAS board! Nicu Popovici
2000-10-29 21:35 ` nick
2000-10-30 0:13 ` Ralf Baechle
2000-10-30 18:03 ` Brady Brown
2000-11-03 21:18 Nicu Popovici
2000-11-03 13:35 ` Carsten Langgaard
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=39F89556.582FD0B@ti.com \
--to=bbrown@ti.com \
--cc=linux-mips@oss.sgi.com \
--cc=octavp@isratech.ro \
/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.