Okay folks, I've done it.
There's usually 2 reasons why a thread (like this one) is left hanging.
1) it didn't work, for various reasons, technological, economical, boredom.
2) girlfriend/wife/dog/taxes.
Now I've tried to solve the most complex problem of all,
how many framebuffers does one need?
The answer is (n+1) where n is the current number of framebuffers.
As such, I pimped up an Octane2, with dual-V12 and dual-dcd, modded a T221 (I didn't do it myself) to allow it to run at 50Hz, and attached it, with opengl multipipe to the Octane2. The result is a very stable and working 3840x2400 "workspace" (aka, 4Dwm), comparable to the g2-brick but deskside (and Xsgi, not Xfree).
I had to find a dual Vpro carrier for the Octane, which Ian (thank you Ian) sourced for me.
Here's the gfxinfo:
Code:
jason@drake:~$ /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 3840x1200
BUZZ version B.0
PB&J version 1
128MB memory
Banks: 4, CAS latency: 3
Monitor 0 type: Unknown
Dual Channel Display option
Monitor 1 type: IBM 9503 Monitor 2 type: IBM 9503
Channel 0:
Origin = (0,0)
Video Output: 1920 pixels, 1200 lines, 50.00Hz (2@1920x1200_50p)
Channel 1:
Origin = (1920,0)
Video Output: 1920 pixels, 1200 lines, 50.00Hz (2@1920x1200_50p)
Graphics board 1 is "ODYSSEY" graphics.
Managed (":0.1") 3840x1200
BUZZ version B.2
PB&J version 1
128MB memory
Banks: 4, CAS latency: 3
Monitor 0 type: Unknown
Dual Channel Display option
Monitor 1 type: IBM 9503 Monitor 2 type: IBM 9503
Channel 0:
Origin = (0,0)
Video Output: 1920 pixels, 1200 lines, 50.00Hz (2@1920x1200_50p)
Channel 1:
Origin = (1920,0)
Video Output: 1920 pixels, 1200 lines, 50.00Hz (2@1920x1200_50p)
Maybe I can push the framerate up a notch, it's not that important; it works, and that's great.