From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 8129] New: kyrofb_check_var misses x-resolution and y-resolution setting?
Date: Sun, 4 Mar 2007 22:21:19 -0800 [thread overview]
Message-ID: <20070304222119.13da738b.akpm@linux-foundation.org> (raw)
Begin forwarded message:
Date: Sun, 4 Mar 2007 22:12:42 -0800
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 8129] New: kyrofb_check_var misses x-resolution and y-resolution setting?
http://bugzilla.kernel.org/show_bug.cgi?id=8129
Summary: kyrofb_check_var misses x-resolution and y-resolution
setting?
Kernel Version: Linux 2.6.20
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: shanlu@cs.uiuc.edu
Distribution: Linux 2.6.20
Problem Description:
kyrofb_check_var (the function supposed to set up based video mode) seems to
forget set two framebuffer parameters: x-resolution and y-resolution.
The function is in File drivers/video/kyro/fbdev.c
399 static int kyrofb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
400 {
401 struct kyrofb_info *par = info->par;
...
In above function, almost every display-related fields (upper-margin,
left-margin, sync, etc.) are set for var based on info->par. But var->x_res and
var->y_res (x-resolution and y-resolution) are not. Why not use par->XRES and
par->YRES to set it?
Also the par->X_RES and par->Y_RES do get set in kyrofb_set_par (in the same
file), together with other field like par->HFP (right margin), HBP
(left_margin). I think check_var should take x,y-resolution from par.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
reply other threads:[~2007-03-05 6:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070304222119.13da738b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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).