[Top] [All Lists]

Re: Status RM200

To: Karsten Merker <>
Subject: Re: Status RM200
From: Florian Lohoff <>
Date: Tue, 27 Nov 2001 17:39:21 +0100
In-reply-to: <>
Organization: rfc822 - pure communication
References: <> <> <> <> <>
User-agent: Mutt/1.3.23i
On Tue, Nov 27, 2001 at 07:18:10AM +0100, Karsten Merker wrote:
> On Mon, Nov 26, 2001 at 11:35:48PM +0100, Martin Schulze 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.

I compiled a kernel yesterday - The only thing comlaining is a
header file for some definitions.

> > As I remember, you can't switch to "the right" endianess without a support
> > drivers f*ckup disk - which hasn't appeared on the stage yet.
> Right - Ralf had asked around for some disks to convert his LE RM200C to
> BE firmware for further development,  but nobody had yet been able to
> come up with some. Additionally, AFAICS these disks are different for
> different machine types and possibly even for different CPU types
> (RM200 EISA vs. RM200C PCI and R4k vs R5k). If anybody knows more about
> these issues, any help is welcome.

They are - The disk type can be determined by the PartNo.

Florian Lohoff                     +49-5201-669912
Nine nineth on september the 9th              Welcome to the new billenium

Attachment: pgpDGI50OPS9P.pgp
Description: PGP signature

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