From: "Stephen P. Becker" <geoman@gentoo.org>
To: Michael Joosten <michael.joosten@c-lab.de>
Cc: linux-mips@linux-mips.org
Subject: Re: SGI O2: working framebuffer/X11 modes?
Date: Fri, 09 Dec 2005 16:23:15 -0500 [thread overview]
Message-ID: <4399F5C3.1050706@gentoo.org> (raw)
In-Reply-To: <4399E92C.6000709@c-lab.de>
> As just today another old O2 materialized on the trash heap around here,
> I actually might try my luck - but it's a R10K O2, IP32.
No luck there, as r10k ip32 still has the cache coherency problem, and
won't run linux.
> The sgivwfb driver uses by default 8MB at the highest end of phys
> memory, and increasing it to 16MB hasn't harmed yet.
The gbefb driver won't even let you choose more than 8mb, and I think
2mb is the default.
> Well, I don't have a 1600sw, and there are some internal patches in the
> visws mailing list of Florian Boor who added a I2C self configuration to
> the driver, such that entereing the monitor type by kernel cmd line
> argument is not necessary anymore.
It would be nice to know if these help out on mips, and if so, they
should probably be contributed to the linux-mips tree. I wish I had a
1600sw with which to tinker.
> ...different depths produce funny results. Haven't tried 8bit, but 24 is
> definitely broken. You can still see something, but barely. So, we can
> probably deduce that the other-than-15bit modes were never actually
> tested by the original author (some intern then a SGI?).
There was actually a patch for Xfree by the original author of the
sgio2fb driver (Vivien, aka glaurung, wasn't it?) which allowed X to run
properly in 16bpp. However, this patch was lost in a hard drive crash
if I recall.
> Recent info
> about the chances to get some hardware docs about the VisWS from SGI
> were simply turned down by the astonishing fact that they really dumped
> the whole product line: hardware, contracts, subcontractors (developed
> the gfx drivers for Win NT) and even documentation. Speak about a deed
> (x86 graphics workstations) so awful that nobody at SGI wanted be
> remembered about it ?
There are at least a couple of folks on this mailing list who I'm pretty
sure know more about the specifics of this hardware. The only question
is, are they allowed to talk to you about it?
-Steve
prev parent reply other threads:[~2005-12-09 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 18:29 SGI O2: working framebuffer/X11 modes? Michael Joosten
2005-12-09 18:50 ` Stephen P. Becker
2005-12-09 20:29 ` Michael Joosten
2005-12-09 21:23 ` Stephen P. Becker [this message]
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=4399F5C3.1050706@gentoo.org \
--to=geoman@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=michael.joosten@c-lab.de \
/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.