Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Re: Newbie question...
Date: Fri, 15 Jun 2001 15:31:48 +0200	[thread overview]
Message-ID: <20010615153147.A7621@lug-owl.de> (raw)
In-Reply-To: <p05001901b74d8f7fb72c@[192.168.1.3]>; from mjpento@mediaone.net on Wed, Jun 13, 2001 at 05:50:06PM -0400

[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]

On Wed, Jun 13, 2001 at 05:50:06PM -0400, mjpento wrote:
[Indigo R3000]

> 1. Is there someone out there working on a port to the R3000's 
> Indigo's? If so, does someone know who it is or a link to a 
> website??? etc ...

Rumor was that Michael Engel was working on the Indigo. I've got
such a beast as well (okay, it's an OEM version build by Siemens
Nixdorf), but there's no Linux running on this box these days.

From what I've heared, the Indigo R3k is quite different to most
other supported machines (Indy, Indigo2) so a port will be
somewhat difficult. The machine isn't the fastest one (well, 
mine is running wirh Irix 5.2 and the flight simulator is quite nice
to play with:-), but it *would* be more then fast enough to run
Linux.

> 2. Since I am rather new to porting, is there a resource that you 
> folks would suggest out there on the internet that would be a good 
> starting point for information or tips on the best porting methods?

Porting Linux to Indigo R3k is difficult. There seems to be no
hardware documentation available (except Irix header files). So
porting will be a means of reading header files, using an oscilloscope
and disassembline Irix' kernel. 

> Any help would be greatly appreciated,

I'd really *love* to see Linux running on Indigo R3k, but I'm not
experienced enough to do the port. However, I'd like to help and
cooperate with more experienced programmers to make it running, but
they're more or less fixed to their bigger^Wfaster machines...

Michael, have you had any success with your Indigo R3k?

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-172-7608481 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  parent reply	other threads:[~2001-06-15 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 13:59 Newbie question Bartosch Pixa
2001-06-13 15:07 ` Mat Withers
2001-06-13 15:22   ` Keith M Wesolowski
2001-06-13 15:14 ` Keith M Wesolowski
2001-06-13 21:50   ` mjpento
2001-06-15 12:12     ` Florian Lohoff
2001-06-15 13:31     ` Jan-Benedict Glaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-21 14:43 newbie question phess.linux
2005-09-21 14:50 ` Nigel Stephens
2002-01-27 18:59 Newbie Question Robert Rusek
2002-01-27 18:59 ` Robert Rusek
2001-06-13 15:43 Newbie question Bartosch Pixa
2001-02-19 13:11 strace sysmips support (was: Re: [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call) Wichert Akkerman
2001-02-19 19:52 ` newbie question Can Altineller
2001-02-20  7:06   ` David Jez
2001-02-20 20:26     ` Mike McDonald
2001-02-20 20:30       ` nick
2001-02-20 20:53       ` Ralf Baechle

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=20010615153147.A7621@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-mips@oss.sgi.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