Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Michael Anburaj <michaelanburaj@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linux for MIPS Atlas 4Kc board
Date: Thu, 10 Apr 2003 03:25:29 +0200	[thread overview]
Message-ID: <20030410032529.A1493@linux-mips.org> (raw)
In-Reply-To: <BAY1-F817dKwKkLxFjj00070900@hotmail.com>; from michaelanburaj@hotmail.com on Wed, Apr 09, 2003 at 02:32:03PM -0700

On Wed, Apr 09, 2003 at 02:32:03PM -0700, Michael Anburaj wrote:

> I am new to Linux. But I have a strong ARM & MIPS background with kernel 
> porting & other stuff.
> 
> I want to get a higher-level view of the essential components of Linux for 
> MIPS & documentation about the kernel. Please point me to documents on the 
> net.

I suggest http://www.linux-mips.org to get started.

> Question 2:
> Does Linux-MIPS support the MIPS Atlas board with 4Kc processor using 
> mipsisa32-elf build tool chain (Contain the appropriate HAL or BSP)? Is so, 
> please point me to documents that gives the exact build steps for the same.

No.  You must use a Linux configuration of the tools, that's mips-linux.

> Also do let me know if Cygwin over Win98 dev. environment is good for 
> building & developing with Linux-MIPS or do I need to have Linux installed 
> on my dev. machine?

I've never use Cygwin myself.  The reports I've received are a mixed bag
ranging from extremly bad to very good.

  Ralf

  reply	other threads:[~2003-04-10  1:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 21:32 Linux for MIPS Atlas 4Kc board Michael Anburaj
2003-04-10  1:25 ` Ralf Baechle [this message]
2003-04-10  6:29   ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11  9:24 Michael Anburaj
2003-04-11  9:28 ` Geert Uytterhoeven
2003-04-11 16:47 ` Jun Sun
2003-04-11  9:48 Michael Anburaj
     [not found] <BAY1-F124jn04x29xDb00011e0b@hotmail.com>
2003-04-11 10:04 ` Geert Uytterhoeven
2003-04-29 19:40 Michael Anburaj
2003-04-29 20:00 ` Wolfgang Denk
2003-04-29 20:06 ` Muthukumar Ratty
2003-04-29 20:06   ` Muthukumar Ratty
2003-04-30  4:00 Michael Anburaj
2003-04-30  4:06 ` Keith Owens
2003-04-30  7:13 Michael Anburaj
2003-04-30  7:24 ` Greg Lindahl
2003-04-30  8:56 Michael Anburaj
2003-05-01  8:53 Michael Anburaj
2003-05-05  0:27 Michael Anburaj
2003-05-05  2:21 ` Muthukumar Ratty
2003-05-05  2:21   ` Muthukumar Ratty
2003-05-05  8:26 Michael Anburaj
2003-05-05 21:52 ` Muthukumar Ratty
2003-05-05 21:52   ` Muthukumar Ratty
2003-05-08 10:09 Michael Anburaj
2003-05-08 11:20 ` Jan-Benedict Glaw
2003-05-08 17:02 Michael Anburaj
2003-05-08 21:40 ` Jan-Benedict Glaw
2003-05-09  5:47 Michael Anburaj
2003-05-09  6:31 Michael Anburaj
2003-05-09  8:25 ` Jan-Benedict Glaw
2003-05-09 18:34 Michael Anburaj
2003-05-10  4:57 Michael Anburaj
2003-05-10  5:44 ` Muthukumar Ratty
2003-05-10  5:44   ` Muthukumar Ratty
2003-05-10 10:30 ` Jan-Benedict Glaw
2003-05-10 15:56 Michael Anburaj
2003-05-10 19:49 ` Jan-Benedict Glaw
2003-05-10 21:07 Michael Anburaj
2003-05-13  7:31 Michael Anburaj

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=20030410032529.A1493@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=michaelanburaj@hotmail.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