From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] Type confusion in fbcon
Date: Fri, 20 Dec 2002 21:30:56 +0000 [thread overview]
Message-ID: <20021220213056.A25155@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0212201808070.6471-100000@phoenix.infradead.org>; from jsimmons@infradead.org on Fri, Dec 20, 2002 at 06:10:17PM +0000
On Fri, Dec 20, 2002 at 06:10:17PM +0000, James Simmons wrote:
> > I'll get back to bashing the sa1100fb driver to work out why fbcon is
> > producing a _completely_ blank display, despite characters being written
> > to it.
>
> Did you figure out what was wrong?
Firstly, setting fix.line_length to zero (which the old API didn't care
about) caused one set of problems.
Secondly, the sa1100fb set_par function doesn't set the var RGB elements -
that's left to the check_var function. Originally, we effectively did
a fb_set_var which took care of that for us. Now we explicitly call
our check_var implementation prior to registering the framebuffer
driver with the fbcon core.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-12-20 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 23:14 Type confusion in fbcon Russell King
2002-12-20 18:10 ` [Linux-fbdev-devel] " James Simmons
2002-12-20 21:30 ` Russell King [this message]
2002-12-23 9:18 ` Geert Uytterhoeven
2002-12-23 21:11 ` David S. Miller
2002-12-23 21:17 ` Geert Uytterhoeven
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=20021220213056.A25155@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).