From: Ralf Baechle <ralf@oss.sgi.com>
To: Karsten Merker <karsten@excalibur.cologne.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: Status RM200
Date: Tue, 27 Nov 2001 17:25:50 +1100 [thread overview]
Message-ID: <20011127172550.D29424@dea.linux-mips.net> (raw)
In-Reply-To: <20011127071800.A292@excalibur.cologne.de>; from karsten@excalibur.cologne.de on Tue, Nov 27, 2001 at 07:18:10AM +0100
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
next prev parent reply other threads:[~2001-11-27 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 19:45 Status RM200 Florian Lohoff
2001-11-26 20:34 ` Karsten Merker
2001-11-26 22:17 ` Florian Lohoff
2001-11-26 22:35 ` Martin Schulze
2001-11-26 23:00 ` Florian Lohoff
2001-11-27 6:18 ` Karsten Merker
2001-11-27 6:25 ` Ralf Baechle [this message]
2001-11-27 16:39 ` Florian Lohoff
2001-11-27 6:19 ` Ralf Baechle
2001-11-27 16:39 ` Florian Lohoff
2001-11-27 22:12 ` Ralf Baechle
[not found] ` <Pine.LNX.4.21.0112022120330.27932-100000@ns>
2001-12-03 6:00 ` o200 oops 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=20011127172550.D29424@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=karsten@excalibur.cologne.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 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.