From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>, adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net, 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 07:46:24 +0800 [thread overview]
Message-ID: <200411020746.27871.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10411011719270.2438-100000@mtfhpc.demon.co.uk>
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 doubt that the problem is at the driver layer since you were able to
see the logo. It's probably higher up.
Try this mod, hardwire the foreground color to 0x07.
Edit drivers/video/console/bitblit.c:bit_putcs() and change this line:
image.fg_color = fg;
image.bg_color = bg;
to
image.fg_color = 0x07070707;
image.bg_color = 0x0;
You can also try the reverse:
image.fg_color = 0x0;
image.bg_color = 0x07070707
If you get visible text, the problem is either in fbcon.c or vt.c.
Tony
next prev parent reply other threads:[~2004-11-01 23:46 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 [this message]
2004-11-02 0:26 ` Helge Deller
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=200411020746.27871.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--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).