From: Michael Joosten <joost@c-lab.de>
To: linux-mips@linux-mips.org
Cc: michael.joosten@c-lab.de
Subject: SGI O2: working framebuffer/X11 modes?
Date: Fri, 09 Dec 2005 19:29:24 +0100 [thread overview]
Message-ID: <4399CD04.2781@c-lab.de> (raw)
Hello,
this actually not really a SGI MIPS question, but a rather one about the
SGI 320 VisWS, which is a dual PIII thing, but it shares a lot of the
framebuffer code (sgivwfb.c) with the O2 one (gbefb.c) - and I'm
writing this on an O2 with IRIX.
We've still have such a beast here, and I'm trying to set up a baseline
of required patches for current kernels in order to get a running
configuration out of the box. Because gbefb was derived from sgivwfb
somewhen back in 2002, it is therefore quite interesting to see how
things are going on the MIPS side, as both gfx hardware implementations
are supposed to be very similar (the visws one using hardware from O2
GBE).
Currently, the only VisWS mode that works under X11 is Depth 15bit,
using the 2 byte/16bit ARGB5 mode in sgivwfb.c, with 1280x1024
or higher with the 1600sw LCD panel. Surprisingly, Depth 16 in
/etc/X11/xorg.conf is not completely OK anymore, perhaps due
to problems with the transparency bit. Anything else like 24
or 8 bit looks decidedly odd, and hard to read at all.
Namely 24/32bit is completely broken, the width of the
display is only 2/3 of the screen, though timing is still OK.
Back to the question: What mode(s) are usable on a Linux O2?
Did 24bit work at ANY time on the O2?
Kind regards, Michael
--
Michael Joosten, SBS C-LAB, joost@c-lab.de
Fuerstenallee 11, 33094 Paderborn, Germany
Phone: +49 5251 606127, Fax: +49 5251 606065
C-LAB is a cooperation of University Paderborn & SIEMENS
next reply other threads:[~2005-12-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 18:29 Michael Joosten [this message]
2005-12-09 18:50 ` SGI O2: working framebuffer/X11 modes? Stephen P. Becker
2005-12-09 20:29 ` Michael Joosten
2005-12-09 21:23 ` Stephen P. Becker
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=4399CD04.2781@c-lab.de \
--to=joost@c-lab.de \
--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.