From: Denis Vlasenko <vda@ilport.com.ua>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH] print an explanation why i810 fb doesn't come up
Date: Mon, 28 Mar 2005 15:30:40 +0300 [thread overview]
Message-ID: <200503281530.40665.vda@ilport.com.ua> (raw)
[-- Attachment #1: Type: text/plain, Size: 185 bytes --]
I've spent silly amonunt of time trying to use i810 fb on my new spiffy
flat panel. This patch will hopefully help other poor souls.
Patch also fixes module parameter comments.
--
vda
[-- Attachment #2: i810_main.c.diff --]
[-- Type: text/x-diff, Size: 1202 bytes --]
--- linux-2.6.11.src/drivers/video/i810/i810_main.c.orig Thu Mar 3 09:30:58 2005
+++ linux-2.6.11.src/drivers/video/i810/i810_main.c Mon Mar 28 15:04:58 2005
@@ -999,8 +999,14 @@ static int i810_check_params(struct fb_v
info->monspecs.dclkmin = 15000000;
if (fb_validate_mode(var, info)) {
- if (fb_get_mode(FB_MAXTIMINGS, 0, var, info))
+ if (fb_get_mode(FB_MAXTIMINGS, 0, var, info)) {
+ int default_sync = (hsync1-HFMIN)|(hsync2-HFMAX)
+ |(vsync1-VFMIN)|(vsync2-VFMAX);
+ printk("i810fb: invalid video mode%s\n",
+ default_sync ? "" :
+ ". Specifying vsyncN/hsyncN parameters may help");
return -EINVAL;
+ }
}
var->xres = xres;
@@ -2020,10 +2026,10 @@ MODULE_PARM_DESC(vyres, "Virtual vertica
" (default = 480)");
module_param(hsync1, int, 0);
MODULE_PARM_DESC(hsync1, "Minimum horizontal frequency of monitor in KHz"
- " (default = 31)");
+ " (default = 29)");
module_param(hsync2, int, 0);
MODULE_PARM_DESC(hsync2, "Maximum horizontal frequency of monitor in KHz"
- " (default = 31)");
+ " (default = 30)");
module_param(vsync1, int, 0);
MODULE_PARM_DESC(vsync1, "Minimum vertical frequency of monitor in Hz"
" (default = 50)");
next reply other threads:[~2005-03-28 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 12:30 Denis Vlasenko [this message]
2005-04-14 5:51 ` [PATCH] print an explanation why i810 fb doesn't come up 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=200503281530.40665.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=adaplas@pol.net \
--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).