linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raphael Assenat <raph@8d.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] mbxfb: Fix a chip bug? resulting in	wrong pixclock
Date: Tue, 15 Aug 2006 08:47:03 -0400	[thread overview]
Message-ID: <44E1C247.8040004@8d.com> (raw)
In-Reply-To: <44E0C3A4.6050407@8d.com>

Raphael Assenat wrote:
> This is a workaround for what I think is a bug in the 2700G chip.
> 
> The PLL output frequency is adustable using 3 values (M, N and P. See
> code for formula). The N value range is documented to be 1 to 7 but when
> it is set to 1, the output frequency is lower than it should be (divided 
> by 2),
> giving unexpected results such as no sync on a CRT display.
I just thought it might be useful to post information about how to reproduce this:

Install fbset and link /etc/fb.modes to the fb.modes.ATI distributed with fbset.

Do 'fbset "800x600-70" -depth 16' and the generated pixel clock will result in a v-sync 
around 25 hz. The 800x600-60 and 800x600-72 modes will work correctly, with the expected 
v-sync values.

After applying the patch, the "800x600-70" mode works correctly.

Here are the modelines from my fb.modes file, just in case:
mode "800x600-70"
     # D: 44.90 MHz, H: 44.544 kHz, V: 70.04 Hz
     geometry 800 600 800 600 8
     timings 22272 40 24 15 9 144 12
     hsync high
endmode

mode "800x600-60"
     # D: 40.00 MHz, H: 37.879 kHz, V: 60.32 Hz
     geometry 800 600 800 600 8
     timings 25000 88 40 23 1 128 4
     hsync high
     vsync high
endmode

mode "800x600-72"
     # D: 50.00 MHz, H: 48.090 kHz, V: 72.19 Hz
     geometry 800 600 800 600 8
     timings 20000 64 56 23 37 120 6
     hsync high
     vsync high
endmode



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-08-15 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 18:40 [PATCH 1/2] mbxfb: Fix a chip bug? resulting in wrong pixclock Raphael Assenat
2006-08-15 12:47 ` Raphael Assenat [this message]

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=44E1C247.8040004@8d.com \
    --to=raph@8d.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).