From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Nahkola Mikko <mikko.nahkola@nokia.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] framebuffer depth and other issues ...
Date: Mon, 28 Oct 2002 22:15:14 +0100 [thread overview]
Message-ID: <20021028211514.GA4269@solo.franken.de> (raw)
In-Reply-To: <20021028112551.GR15137@aurinko.ntc.nokia.com>
On Mon, Oct 28, 2002 at 01:25:52PM +0200, Nahkola Mikko wrote:
> I was wondering ... the VIS-EG is about as close to "fully supported" as
> they get, right?
there are still 2D drawing accelerations possible, hardware cursor,
color recovery and usage of the second color map.
> Is it possible to get more than 8 bpp out of a VIS-EG?
no, VIS-EG is 8 bit color, no way to get more.
> How much of a difference is there between VIS-EG/PCI (A4977A) and
> VIS-EG/GSC (A4450A) in this regard? I have an A4450A in there at the
> moment.
no difference in color depth between PCI and GSC cards.
> HP-UX seems to find a whole lot of differences and such ... and I did run
> GNOME/HP-UX once on a VIS-EG/PCI without running out of colors but then
> again HP-UX does color recovery and acceleration and all that on those...
I guess the HP-UX Xserver uses the second color map and color recovery.
I've looked a little bit how to use the second color map and I haven't
found a simple to way to add support to XFree for it. It's a nice way
to have 256 color for the desktop and 256 independant colors for the
application with focus. Maybe some XFree86 guru could give me a hint how
to implement it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ Alexander Viro on linux-kernel ]
next prev parent reply other threads:[~2002-10-28 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 11:25 [parisc-linux] framebuffer depth and other issues Nahkola Mikko
2002-10-28 14:56 ` Carlos O'Donell
2002-10-28 21:15 ` Thomas Bogendoerfer [this message]
2002-10-29 0:49 ` Grant Grundler
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=20021028211514.GA4269@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=mikko.nahkola@nokia.com \
--cc=parisc-linux@lists.parisc-linux.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox