dri-devel Archive on 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: Mon, 07 Apr 2014 15:45:17 +0000	[thread overview]
Message-ID: <bug-77009-502-No48xNEPIR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77009-502@http.bugs.freedesktop.org/>


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

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

--- Comment #21 from Garrett <socalfisher@gmail.com> ---
Created attachment 97043
  --> https://bugs.freedesktop.org/attachment.cgi?id=97043&action=edit
368 and others dmesg

>Garrett, please stop trying to merge the patches. Since the initial change is >already upsteram we are going to need to fix it in a separate patch anyway.

Sorry.  New to this FOSS stuff.  OE is a complete OS download with local code
not pulling from mainline kernels (from what I can tell).  It was tricky for me
to patch it.  I am trying to be transparent so others can reproduce my results
easily.


>My fix limited the reference divider so that "post_div * ref_div <= 100". Could >you try to raise the 100 to see at which point your TV says the signal isn't >valid any more?

>With a limit of 500 you should be at the same point as before, so I suggest to >try values of 200, 300, 400 first. Then if 200 works but 300 doesn't (for >example) try 250, and so on...

Thanks for the tips.

OK- I built many.  368 is the closest I got.  I have to head to the office.  I
uploaded all dmesg, tests.  What I don't understand is the pll numbers go up
and down, despite having the higher max vals.  This concerns me..

Hope it helps.  I assume you do not want to run all pc's at max.  Else
tolerances at the hardware/silica/chipset level may result in similar results
to my sys.  But at least now I can tune my sys.  :)  

368 is much higher than 100.  LMK if you need more. TIA.

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

[-- Attachment #1.2: Type: text/html, Size: 2611 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-07 15:45 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 [this message]
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
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-No48xNEPIR@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox