From: Kyle Moffett <mrmacman_g4@mac.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bodo Eggert <7eggert@gmx.de>, LKML <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
Date: Sun, 7 Aug 2005 21:13:54 -0400 [thread overview]
Message-ID: <96358AEB-784F-444E-A0BA-04AD920284B3@mac.com> (raw)
In-Reply-To: <1123431219.30257.115.camel@gaston>
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
>> I've got an LCD, and on mine
>> it looks like every third pixel-line gets shifted about 32-64
>> pixels to
>> the left, and they move with display refresh. My guess is that
>> something is interrupting radeonfb during a critical time in display
>> syncing and forcing the video card to wait too far into the next line
>> before sending pixels.
>
> radeonfb is mostly inactive after it has setup the framebuffer and
> unless you actually draw something, in which case, accel code is
> called.
>
> _However_ there is an unrelated problem with some panels, including
> some
> of the 17": The panel doesn't always "sync" properly. This seem to be
> related to some subtle timing issue in the LVDS code but I don't know
> exactly what yet. You can usually get it back by repeately turning the
> backlight all the way down (which shuts the panel off) and back up
> until
> it "catches".
Hmm. This doesn't really fit as my issues are very reproducible. The
behaviour under stock Debian 2.6.8 is identical during reboots and after
fblevel 0 ; sleep X ; fblevel 15. Likewise, stock 2.6.11, 2.6.12.4, and
2.6.13-rc5, although I'm just getting back to testing things.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so
simple that there are obviously no deficiencies. And the other way is
to make
it so complicated that there are no obvious deficiencies. The first
method is
far more difficult.
-- C.A.R. Hoare
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-08 1:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 22:03 Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5 Bodo Eggert
2005-08-04 22:44 ` Benjamin Herrenschmidt
2005-08-05 17:38 ` Bodo Eggert
2005-08-07 7:51 ` Benjamin Herrenschmidt
2005-08-07 13:45 ` Kyle Moffett
2005-08-07 16:13 ` Benjamin Herrenschmidt
2005-08-08 1:13 ` Kyle Moffett [this message]
2005-08-08 2:41 ` Kyle Moffett
2005-08-07 17:25 ` Bodo Eggert
2005-08-07 21:48 ` Benjamin Herrenschmidt
2005-08-08 0:06 ` Bodo Eggert
2005-08-08 8:19 ` Benjamin Herrenschmidt
2005-08-09 20:13 ` Bodo Eggert
2005-08-09 23:13 ` Bodo Eggert
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=96358AEB-784F-444E-A0BA-04AD920284B3@mac.com \
--to=mrmacman_g4@mac.com \
--cc=7eggert@gmx.de \
--cc=benh@kernel.crashing.org \
--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).