linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: typo errors in the modedb.c video mode	tables
Date: Sun, 22 Jul 2007 08:26:07 +0800	[thread overview]
Message-ID: <1185063967.8688.9.camel@daplas> (raw)
In-Reply-To: <BAY137-F3235E7DB69C9967750E90DA3F50@phx.gbl>

On Sat, 2007-07-21 at 18:59 -0400, John Lumby wrote:
> I believe there are a few typos in the mode tables in modedb.c   -   in the 
> current 2.6.22 :

> I also don't know what effect these errors are having - I found them from 
> studying the code after I could not get my desired 1400x1050@60 for my 
> supersavage framebuffer console.       One of the above entries is the one I 
> want.    Is the refresh value in these tables used for matching modes? 

Yes, the refresh field is used for matching.    
 
> It seems so from my reading of fb_find_mode() in the same file.

I'll review those values again and apply the appropriate corrections.
You can also avoid the table lookup and use 1400x1050M@60 instead.  The
timings will be computed.

Tony 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  reply	other threads:[~2007-07-22  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 22:59 typo errors in the modedb.c video mode tables John Lumby
2007-07-22  0:26 ` Antonino A. Daplas [this message]
2007-07-26  3:16   ` typo errors in the modedb.c video modetables John Lumby

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=1185063967.8688.9.camel@daplas \
    --to=adaplas@gmail.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).