linux-mips
[Top] [All Lists]

Re: Status RM200

To: Karsten Merker <karsten@excalibur.cologne.de>
Subject: Re: Status RM200
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Tue, 27 Nov 2001 17:25:50 +1100
Cc: linux-mips@oss.sgi.com
In-reply-to: <20011127071800.A292@excalibur.cologne.de>; from karsten@excalibur.cologne.de on Tue, Nov 27, 2001 at 07:18:10AM +0100
References: <20011126204509.A10341@paradigm.rfc822.org> <20011126213450.B943@excalibur.cologne.de> <20011126231737.B13081@paradigm.rfc822.org> <20011126233548.D26510@finlandia.infodrom.north.de> <20011127071800.A292@excalibur.cologne.de>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Tue, Nov 27, 2001 at 07:18:10AM +0100, Karsten Merker wrote:

> > > How can the RM200 port be wrong endianess - The RM200 is bi-endian
> > > thus any endianess would be ok (As long as the port does not assume
> > > a specific endianess except the prom stuff).
> 
> Unfortunately the firmware functions are different between little- and
> big-endian firmware and there are quite some parts in the RM200 support
> which currently do not work (and some even do not compile) on a big-endian
> machine due to missing (correct) definitions. Another problem regarding 
> the big endian firmware is that nobody seems to have documentation about
> it, not even a function vector table.

As I understand the big endian firmware is just yet another ARC firmware
implementation with some support for old MIPS firmware style vector tables.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>