linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: viafb: XO-1.5 video broken on 2.6.39
Date: Wed, 13 Apr 2011 23:05:49 +0000	[thread overview]
Message-ID: <4DA62C4D.8070407@gmx.de> (raw)
In-Reply-To: <BANLkTimFS0yC2629V0tBQQZG+9hJTkSctw@mail.gmail.com>

Hi Daniel,

Daniel Drake schrieb:
> Hi,
> 
> Commit fd3cc69848b7e1873e5f12bbcdd572b20277ecf3 breaks video on the
> XO-1.5 laptop on 2.6.39:

Sorry about that.

> commit fd3cc69848b7e1873e5f12bbcdd572b20277ecf3
> Author: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
> Date:   Fri Mar 11 00:04:01 2011 +0000
> 
>     viafb: remove duplicated clock storage
> 
> This is using the 1200x900 mode (DCON1200x900)
> 
> In the old code, the clock was hardcoded as value 57275000.
> In the new code, the clock gets calculated as 1264x912x60 = 69166080

Having a closer look at it the entire mode looks suspicious as it is neither CVT 
nor GTF compatible. But as it worked I assume the timings are correct and only 
the refresh rate is incorrect. If we reduce the refresh rate to 50Hz we get
1264x912x50 = 57638400 which is pretty close to the old value (and the 
documentation about DCON I found also suggests that it works at 50Hz). I will 
prepare a patch as soon as I have time (the driver tends to assume that 60Gz 
mode is always present and working).

> The result is that the screen gets filled with black and grey
> horizontal lines instead of anything readable.
> 
> Any ideas?
> 
> Thanks,
> Daniel
> 

Thanks a lot for your bug report,

Florian Tobias Schandinat


  reply	other threads:[~2011-04-13 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 20:59 viafb: XO-1.5 video broken on 2.6.39 Daniel Drake
2011-04-13 23:05 ` Florian Tobias Schandinat [this message]
2011-04-15 21:52   ` [PATCH] viafb: fix OLPC DCON refresh rate Florian Tobias Schandinat

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=4DA62C4D.8070407@gmx.de \
    --to=florianschandinat@gmx.de \
    --cc=linux-fbdev@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).