From: Gene Heskett <gene.heskett@gmail.com>
To: Keith Packard <keithp@keithp.com>,
Ben Brewer <ben.brewer@codethink.co.uk>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: i915 SSC Patch
Date: Fri, 29 Jul 2011 18:01:39 -0400 [thread overview]
Message-ID: <201107291801.40049.gene.heskett@gmail.com> (raw)
In-Reply-To: <yunwrf1gc3b.fsf@aiko.keithp.com>
On Friday, July 29, 2011, Keith Packard wrote:
>On Fri, 29 Jul 2011 13:55:35 +0100, Ben Brewer
<ben.brewer@codethink.co.uk> wrote:
>> I've added a global SSC (Spread Spectrum Clock) parameter to the i915
>> driver, since having SSC enabled breaks (distorts) VGA output on some
>> Core i5/i7 chips (see
>> https://bugs.freedesktop.org/show_bug.cgi?id=38750). SSC is still
>> enabled by default so the behaviour won't change but setting the
>> global_use_ssc parameter will turn this feature off and allow affected
>> devices to function correctly (notably the Dell Vostro 3300).
>
>The question I have is why is SSC enabled on the VGA output at all? I
>don't see any way VGA could ever tolerate it.
Something does not make sense here Keith, so I'm with you, and my
background is from about 60 years in tv maintenance and 45 in broadcasting.
A pure digital output, where its a high speed serial transfer of bytes to
the monitor, is generally not going to be sensitive the any SS used unless
the baud rate slams around too much on a byte to byte basis. Since SS is
generally just a few percent, even that should not be a problem. But
feeding analog signals up a video cable to a vga monitor, and the pixel
time is wobbling by 2 to 5% and you won't have much of a viewable image
left. The analog signals, vga etc, needs their own video clock, a dead
stable one.
We used to spend $10k-30k$ just so we could take the signal from a
mechanically unstable vcr that only cost us $10k, and make it stable enough
to work on your home tv's without the top of the pix waving around like
hurricane Katrina was in the neighborhood.
Hardware design error in the Dell?
Cheers, gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Apathy is not the problem, it's the solution"
next prev parent reply other threads:[~2011-07-29 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 12:55 i915 SSC Patch Ben Brewer
2011-07-29 18:45 ` Keith Packard
2011-07-29 19:02 ` Chris Wilson
2011-07-29 21:18 ` Keith Packard
2011-07-29 22:01 ` Gene Heskett [this message]
2011-07-29 22:18 ` Keith Packard
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=201107291801.40049.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=ben.brewer@codethink.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--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