From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@transvirtual.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Comments on fbgen.c and fbcon-accel.c
Date: 04 May 2002 23:48:47 +0800 [thread overview]
Message-ID: <1020527361.752.1.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.10.10205031444260.9732-100000@www.transvirtual.com>
On Sat, 2002-05-04 at 05:47, James Simmons wrote:
>
> > I have a few observations on fbgen and fbcon-accel.
>
> Don't mix fbgen with fbcon-accel. The new gen_* stuff in fbgen.c is meant
> to replace the old fbgen_* stuff. That is why the below doesn't work.
>
Okay, I've succeeded in rewriting the i810/i815 driver to use the gen_*
stuff instead of fbgen_*. As far as I can tell everything works :) --
y-panning, accel, etc -- although gen_update_var() may not work
properly. I'm still getting incorrect cursor colors in 8 bpp, but
that's probably my fault. And you're right, it's actually easier to
write the driver using the gen_* stuff.
>
> > 2. Also, fbgen_switch basically just do an fbgen_do_set_var()
> > (decode_var(), followed by set_par()). This is okay most times, but
> > it's probably better if fbgen_switch also does an encode_fix() since
> > fbcon's drawing functions also rely on fix->line_length.
>
> Most likely that is also broken. I haven't thought about it since I plan
> to make all the old fbgen_* functions go away.
>
fb_gen_switch may be broken, but I think gen_switch works just okay as
long as info->fix is updated in set_par().
> > If an fb_fix_screeninfo is not updated, display corruption occurs when
> > switching to another display with a different pixelformat.
>
> Correct. That is why I require info->fix to be updated when set_par is
> called.
>
Right.
The i810fb patch is at
http://prdownloads.sourceforge.net/i810fb/linux-2.5.13-i810fb.tar.bz2.
Tony
--- fbgen.c.orig Sat May 4 14:35:32 2002
+++ fbgen.c Sat May 4 15:02:37 2002
@@ -514,7 +514,8 @@
if (con == info->currcon) {
if (info->fbops->fb_pan_display) {
- if ((err = info->fbops->fb_pan_display(&info->var, con, info)))
+ /* Tony: offsets are still in disp->var, not info->var */
+ if ((err = info->fbops->fb_pan_display(&fb_display[con].var, con, info)))
return err;
}
}
prev parent reply other threads:[~2002-05-04 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1020419481.724.0.camel@daplas>
2002-05-03 21:47 ` [Linux-fbdev-devel] Comments on fbgen.c and fbcon-accel.c James Simmons
2002-05-04 15:48 ` Antonino Daplas [this message]
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=1020527361.752.1.camel@daplas \
--to=adaplas@pol.net \
--cc=jsimmons@transvirtual.com \
--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