From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: scrollmode selection problem
Date: Mon, 12 Dec 2005 18:38:43 +0100 [thread overview]
Message-ID: <439DB5A3.9050205@t-online.de> (raw)
Have a look at the following problem:
framebuffer memory size is 8MB
xres is 800, yres is 600, bpp is 8.
xres_virtual is 1024, yres_virtual is 8192.
font dimensions 8x16
check_var() and set_par() are called, set_par() decides that ywrap
scrolling is possible and sets FBINFO_HWACCEL_YWRAP.
Well, that decision is _wrong_ as 600/16 results in a 37 line display
height, 8 pixel lines at the bottom are unused. But they are displayed,
and obviously they contain garbage as YWRAP scrolling is selected by
updatescrollmode().
As the driver does know nothing about fonts, the obvious place to
change is updatescrollmode().
int good_wrap = (cap & FBINFO_HWACCEL_YWRAP) &&
divides(ywrap, vc->vc_font.height) &&
divides(vc->vc_font.height, vyres) &&
divides(vc->vc_font.height, yres);
would be a solution, but I don´t like it. There is no real reason that
ywrap
scrolling should be disallowed when divides(vc->vc_font.height, vyres)
or divides(vc->vc_font.height, yres) are false ... only limitations of the
fbcon scrolling code.
Has someone already written code to remove that limitation?
cu,
Knut
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-12 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 17:38 Knut Petersen [this message]
2005-12-13 0:36 ` scrollmode selection problem Antonino A. Daplas
2005-12-13 11:07 ` Geert Uytterhoeven
2005-12-13 12:28 ` Knut Petersen
2005-12-13 12:35 ` Geert Uytterhoeven
2005-12-13 16:04 ` Antonino A. Daplas
2005-12-13 16:09 ` Antonino A. Daplas
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=439DB5A3.9050205@t-online.de \
--to=knut_petersen@t-online.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.