From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
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: Help re Frame Buffer/Console Problems
Date: Wed, 3 Nov 2004 05:40:06 +0800 [thread overview]
Message-ID: <200411030540.06262.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10411021743001.4822-100000@mtfhpc.demon.co.uk>
On Wednesday 03 November 2004 02:03, Mark Fortescue wrote:
> Hi all,
>
> I have identified what is going on. My CG3 console uses the same font and
> exactly overlaps prom console. [I have re-inserted the console margin code
> for my CG3 driver]. The timing is such that the prom overwrites the
> console text (using colour 255) a fraction later than the fbcon code.
>
> The two problems to be solved are (apart from seting the red,green and
> blue structures up for the cg series fb cards):
>
> 1) The prom write (from -p) needs to be disabled as soon as an alternative
> console becomes active (either prom console, fbcon console or serial
> console). This has probably been the major cause of hassel.
>
> 2) The restore pallet function (see cgsix.c in the 2.2.x or 2.4.x kernels)
> needs to be re-introduced in some form and called when exiting fbcon so
> that the prom does not end up as black on black. My prom uses fg=255,
You can implement a cg3fb_open() and cg3fb_release() hooks and set up a
use_count field. You increment the count on every open, decrement on every
release. Then restore whatever on the last release. Optionally, you can even
do hardware inits on the first open.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-02 21:40 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
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 21:40 ` Antonino A. Daplas [this message]
2004-11-02 22:57 ` 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=200411030540.06262.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--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).