Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Michel Dänzer" <michdaen@iiic.ethz.ch>, caslivkoff@yahoo.com
Cc: xpert@XFree86.Org, parisc-linux@lists.parisc-linux.org
Subject: Re: [Xpert][parisc-linux] white is blue
Date: Sat, 18 Aug 2001 21:46:46 +0200	[thread overview]
Message-ID: <20010818194852.79AE7482A@dsl2.external.hp.com> (raw)
In-Reply-To: <3B7EC209.87A159D2@iiic.ethz.ch>

> > That's what I though too, but I've tried this on 2 different 712's and
> > have the same behavior.
>
> But I assume you use the same framebuffer device on both? (Note that when I
> say framebuffer device, I refer to the Linux kernel driver)

Both 712 have the same Graphics chip ("Artist") and use the same stifb driver (it's 
also the only one which supports HP's build-in graphics atm).

> > What is strange is that the framebuffer can display white text with no
> > problem on the console (the default cursor is white). Also, under X,
> > specifying #fefefe shows up as "almost white".
>
> There are no known problems with the XFree86 fbdev colormap handling, but
> maybe you have found one... :)

This is definitively a bug in the linux kernel stifb driver.
I wrote (migrated) most parts of this stifb driver and it works perfectly without any
color-problems together with the XFree86 fbdev driver here on my 715/64. 
The 715/64 has the Artist graphics chip too, so I suspect we just need some more 
initialization for the "older revisions" of the Artist chip in the 712 machines.

Greetings,
Helge

  reply	other threads:[~2001-08-18 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B7DE89A.5A665A16@yahoo.com>
     [not found] ` <3B7E9021.AA279076@iiic.ethz.ch>
2001-08-18 19:13   ` [Xpert][parisc-linux] white is blue caslivkoff
2001-08-18 19:29     ` Michel Dänzer
2001-08-18 19:46       ` Helge Deller [this message]
2001-08-21  7:09         ` Grant Grundler
2001-08-18 19:55     ` Dr Andrew C Aitchison
2001-08-18 23:42       ` caslivkoff

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=20010818194852.79AE7482A@dsl2.external.hp.com \
    --to=deller@gmx.de \
    --cc=caslivkoff@yahoo.com \
    --cc=michdaen@iiic.ethz.ch \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xpert@XFree86.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