All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77009] 24P playback video signal loss with latest DRI patches
Date: Wed, 09 Apr 2014 12:17:21 +0000	[thread overview]
Message-ID: <bug-77009-502-1TlDiA4xHz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77009-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=77009

--- Comment #28 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #27)
> "the signal gets more unstable"
> 
> So it is the gpu that varies its freq. at higher divs (multipliers) and my
> set is not tolerant of signal freq. fluctuations to keep data in sync? 

Yes.

> If I understand this correctly- This is like in a micro-controller where
> deviations in baud rate (a pll generated clock) leads to serial transmission
> errors when > 5% deviation, for example. In micro-controllers: high
> multipliers * internal pll = less stable freq >> less stable baud rate.

Yes that's exactly the same problem just a completely different use case.

Depending on the details of their electrical implementation all PLLs behave
more or less like this. The trick is to know how to find the right numbers
without violating the contrains.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1951 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-04-09 12:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 14:56 [Bug 77009] New: 24P playback video signal loss with latest DRI patches bugzilla-daemon
2014-04-03 15:39 ` [Bug 77009] " bugzilla-daemon
2014-04-03 16:03 ` bugzilla-daemon
2014-04-03 21:06 ` bugzilla-daemon
2014-04-04 11:59 ` bugzilla-daemon
2014-04-04 12:06 ` bugzilla-daemon
2014-04-04 14:18 ` bugzilla-daemon
2014-04-04 17:45 ` bugzilla-daemon
2014-04-04 17:49 ` bugzilla-daemon
2014-04-04 17:49 ` bugzilla-daemon
2014-04-04 18:10 ` bugzilla-daemon
2014-04-05 22:44 ` bugzilla-daemon
2014-04-05 22:46 ` bugzilla-daemon
2014-04-06  4:02 ` bugzilla-daemon
2014-04-06  4:13 ` bugzilla-daemon
2014-04-06 20:59 ` bugzilla-daemon
2014-04-06 21:00 ` bugzilla-daemon
2014-04-06 21:01 ` bugzilla-daemon
2014-04-07  0:32 ` bugzilla-daemon
2014-04-07  0:37 ` bugzilla-daemon
2014-04-07  7:28 ` bugzilla-daemon
2014-04-07  7:28 ` bugzilla-daemon
2014-04-07  7:29 ` bugzilla-daemon
2014-04-07  7:29 ` bugzilla-daemon
2014-04-07  7:30 ` bugzilla-daemon
2014-04-07  7:39 ` bugzilla-daemon
2014-04-07 15:45 ` bugzilla-daemon
2014-04-08  5:01 ` bugzilla-daemon
2014-04-08 13:29 ` bugzilla-daemon
2014-04-08 14:00 ` bugzilla-daemon
2014-04-08 14:15 ` bugzilla-daemon
2014-04-08 14:31 ` bugzilla-daemon
2014-04-09  2:23 ` bugzilla-daemon
2014-04-09 12:17 ` bugzilla-daemon [this message]
2014-04-10 14:00 ` bugzilla-daemon
2014-04-11 13:41 ` bugzilla-daemon
2014-04-22 14:53 ` bugzilla-daemon
2014-05-08 19:01 ` bugzilla-daemon

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=bug-77009-502-1TlDiA4xHz@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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.