[Top] [All Lists]

Re (R8000...): Re: [PATCH] Impact video driver for SGI Indigo2

To: Joshua Kinard <>
Subject: Re (R8000...): Re: [PATCH] Impact video driver for SGI Indigo2
From: peter fuerst <>
Date: Tue, 13 Sep 2011 23:32:17 +0200 (CEST)
In-reply-to: <>
References: <Pine.LNX.4.64.1109111200400.4146@Indigo2.Peter> <>

On Tue, 13 Sep 2011, Joshua Kinard wrote:

Date: Tue, 13 Sep 2011 08:43:39 -0400
From: Joshua Kinard <>
Subject: Re: [PATCH] Impact video driver for SGI Indigo2


+# elif defined(CONFIG_SGI_IP26)
+#  define IPNR 26

Just to uphold hope ;)

I don't think IP26 will ever live.  I think the old R8000 TLB code was
removed a few years ago, too, so to get such systems to work, someone needs
to actually have one (I do), resurrect the old code, add in the TLB pieces
(the Manual is available, so this isn't beyond impossible now), and test it.
But at 75MHz, these machines aren't exactly speed demons, compared even to
an R10K I2.

But the R8000 is more exotic ;-) And there are SPEC FP benchmarks, where it
outperforms a 333MHz Alpha 21164 :-)

But (to me) it seems uncertain, whether enough information can be retrieved
to make this machine work. Consider alone the cache handling (same constraints
for uncached memory accesses on IP26 and IP28): the manual states nothing about
whether this processor has inerited R4k's cacheflush-ops. Looking at the sample
code for cache initialization there, i fear, such easy methods are not

+    /* CFIFO parameters */

If I recall correctly, doesn't IMPACT_CFIFO_* break down to a pointer

Yes.  (Above each address occurs only once, so no pointer-variables are used)

              I was thinking it might be more readable to finally create a
static inline function called impact_write* and impact_read* to take care of
register access than doing pointer dereferences.

I had prepared such functions, which would replace the assignments, to handle
32Bit and 64Bit accesses to the card transparently. But, although the Xserver
shows, that at least a subset of 32Bit-accesses work, i came to the conclusion,
that the benefits from allowing 32Bit-accesses aren't worth the exertion.
Staying with 64Bit mode we can use the simple assignments and IMHO demanding
a 64Bit kernel for IP22-Impact isn't asking to much.

                                                  I got dinged on this when
trying to submit a driver for the RTC 1687-5 in O2 and Octane a few months ago.

+    *cfifo = IMPACT_CMD_COLORMASKLSBSA(0xffffff);
+    *cfifo = IMPACT_CMD_COLORMASKLSBSB(0xffffff);
+    *cfifo = IMPACT_CMD_XFRMASKLO(0xffffff);
+    *cfifo = IMPACT_CMD_XFRMASKHI(0xffffff);

Ditto per the above.

Don't have a working IP22 board anymore.  Haven't setup my old IP28 in a
while, but it is intact and does have a SolidImpact in it.  I also have a
working IP26 (as noted above), but I would be surprised if anyone ever
tackled R8000 support, given the exotic nature of that CPU.

Yell if you ever pick up an Octane -- I could use some help getting that
beast to work again...

Joshua Kinard
4096R/D25D95E3 2011-03-28

"The past tempts us, the present confuses us, the future frightens us.  And
our lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

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