From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@transvirtual.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: problem with gen_update_var
Date: 18 Jun 2002 03:58:41 +0800 [thread overview]
Message-ID: <1024343964.14222.0.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.44.0206171224150.31825-100000@www.transvirtual.com>
On Tue, 2002-06-18 at 03:27, James Simmons wrote:
>
> > Hi,
> >
> > gen_update_var will break panning/wrapping since it passes info->var to
> > fb_pan_display. However, fbcon updates display->var.
>
> It works. The var info struct fb_info is always the foreground console.
> Notice gen_update_var is only called when it is the foreground console.
>
>
In ywrap_up in fbcon.c, it has this code:
p->var.xoffset = 0;
p->var.yoffset = p->yscroll*fontheight(p);
p->var.vmode |= FB_VMODE_YWRAP;
p->fb_info->updatevar(unit, p->fb_info);
(*p is struct display). gen_update_var will call pan_display(info->var,
con, info). But as can be seen, info->var is not updated by ywrap_up.
Unless, the low-level driver's implementation is to get the offsets
from fb_display[con].var, that's the only time it will work. But it
will break userland apps that will call pan_display(var, con, info)
expecting that the offsets contained in the passed var parameter will be
updated.
Tony
_______________________________________________________________
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next prev parent reply other threads:[~2002-06-17 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 16:41 problem with gen_update_var Antonino Daplas
2002-06-17 19:27 ` James Simmons
2002-06-17 19:58 ` Antonino Daplas [this message]
2002-06-17 20:38 ` James Simmons
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=1024343964.14222.0.camel@daplas \
--to=adaplas@pol.net \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).