From: "Paul A. Clarke" <pc@us.ibm.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: vandrove@vc.cvut.cz
Subject: Re: matroxfb-fix-dvi-setup-to-be-more-compatible.patch introduces jitter
Date: Thu, 10 Aug 2006 11:55:07 -0500 [thread overview]
Message-ID: <44DB64EB.3020007@us.ibm.com> (raw)
In-Reply-To: <689964845@web.de>
I've been looking deeper into this problem, which was reportedly introduced by
my patch a while ago, in Linux kernel 2.6.17. I don't doubt the reports, but
I'd like to replicate the problem as seen on the x86 boxes as reported in kernel
bug 6720 and a few others directly to me, so I can verify a fix (if/when I can
create one).
So, I installed SLES 10 on an old x86 box, with a PCI G450 (actually an IBM
GXT135P). I verified that my patch is _not_ included in that kernel
(2.6.16.21). However, I see jittery DVI-D output at all times. I've tried
640x480@60Hz, 1280x1024@60Hz, different "vesa" mode parameters (0x11b, 0x1bb),
XServer "-fbbpp 32". I usually end up losing sync with the monitor after a few
minutes.
I don't have much experience with the G450 on x86, but I'm quite surprised. Has
anyone else observed this?
--
Regards,
Paul Clarke
-------------------------------------------------------------------------
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
next parent reply other threads:[~2006-08-10 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <689964845@web.de>
2006-08-10 16:55 ` Paul A. Clarke [this message]
2006-08-10 19:45 ` matroxfb-fix-dvi-setup-to-be-more-compatible.patch introduces jitter Petr Vandrovec
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=44DB64EB.3020007@us.ibm.com \
--to=pc@us.ibm.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=vandrove@vc.cvut.cz \
/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).