From: Helge Deller <deller@gmx.de>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
Mark Fortescue <mark@mtfhpc.demon.co.uk>,
jsimmons@infradead.org, geert@linux-m68k.org,
sparclinux@vger.kernel.org, ultralinux@vger.kernel.org,
linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: [Linux-fbdev-devel] Help re Frame Buffer/Console Problems
Date: Tue, 2 Nov 2004 01:26:01 +0100 [thread overview]
Message-ID: <200411020126.01891.deller@gmx.de> (raw)
In-Reply-To: <200411020746.27871.adaplas@hotpop.com>
On Tuesday 02 November 2004 00:46, Antonino A. Daplas wrote:
> On Tuesday 02 November 2004 01:32, Mark Fortescue wrote:
> > Hi all,
> >
> > Thanks for the info Antonino. I see you spotted my typing error. Yes it is
> > the 2.6.10-rc1-bk6 kernel. The oter error is the 2.2.8.1. It should be
> > 2.6.8.1.
> >
> > The cgthree driver does not currently set up the all->info.var.red,
> > all->info.var.green or all->info.var.blue structures. Putting a value of 8
> > in the length field of these structures (correct for the cgthree) does get
> > me my logo back but I am still getting black on black text. It makes it
> > very difficult to read. It is begining to look like there is something
> > werid going on with the colour pallet stuf for PSEUDO_COLOUR.
I saw similiar problems with the stifb driver on HPPA.
Changing the driver's pseudo_palette[] struct to support 256 colors solved this problem.
But there might be a problem in higher levels as well....
Helge
next prev parent reply other threads:[~2004-11-02 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 18:22 Help re Frame Buffer/Console Problems Mark Fortescue
2004-10-29 18:27 ` William Lee Irwin III
2004-10-30 0:25 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-11-01 17:32 ` Mark Fortescue
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-02 0:26 ` Helge Deller [this message]
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 22:57 ` [Linux-fbdev-devel] " Mark Fortescue
2004-11-02 23:19 ` Antonino A. Daplas
2004-11-03 0:01 ` Mark Fortescue
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=200411020126.01891.deller@gmx.de \
--to=deller@gmx.de \
--cc=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=ultralinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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;
as well as URLs for NNTP newsgroup(s).