All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@masterguardian.com>
To: dri-devel@lists.freedesktop.org
Subject: gma500: wrong pixel clock on LVDS (half the correct frequency)
Date: Thu, 08 May 2014 04:21:07 +0100	[thread overview]
Message-ID: <536AF823.9030604@masterguardian.com> (raw)


Hi all,

I have a embedded PC system here that has an Atom Z510. The system 
includes a GMA500 graphics chip.

The display is connected through the LVDS port and has a resolution of 
1024x768.

The system works ok in Windows and painfully slowly in Linux with the 
vesa driver, but without any flicker.

Using the gma500 driver, the pixel clock seems to be half of what it 
should be (measured with an oscilloscope). When the image is good the 
pixel clock is around 65MHz. When the gma500 driver sets the resolution 
the pixel clock goes to around 32MHz. This gives a frame rate of around 
30Hz which explains the horrible screen flicker. The performance is 
quite good, though.

I tried running xrandr to create new modes, but the pixel clock is 
always wrong, no matter what I tried.

The kernel version is 3.12.1. I looked at the git repository log to see 
if anything changed in the meanwhile that could affect this, but nothing 
popped up.

Can you give me some pointers to what I should try next? Some obscure 
kernel parameter? Do you need more information?

The linux graphics system changed a bit over the last few years (KMS, 
etc.) and I missed some of the changes, so please bare with me if I ask 
silly questions...

Thanks in advance for any help,

Paulo Marques

                 reply	other threads:[~2014-05-08  4:23 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=536AF823.9030604@masterguardian.com \
    --to=pmarques@masterguardian.com \
    --cc=dri-devel@lists.freedesktop.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 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.