From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 47007] HDMI monitor polling causing 100ms rendering stalls
Date: Fri, 16 Mar 2012 08:47:31 +0000 [thread overview]
Message-ID: <bug-47007-502-FNgiMXTWGJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-47007-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=47007
--- Comment #33 from Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk> 2012-03-16 01:47:31 PDT ---
(In reply to comment #32)
> (In reply to comment #31)
> > It is a single DVI-I physically.
> >
> > But even identifying it would not change anything with regards to polling
> > induced rendering stalls, right?
> >
>
> Well, shared_ddc wouldn't apply in that case since there is only one connector,
> and for better or worse we wouldn't be polling since the connector does have an
> HPD pin (even if it doesn't necessarily work reliably with the analog part of a
> DVI-I connector). So fixing that would avoid the polling stalls on your
> particular board.
Ok, I misunderstood would would happen after applying this quirk. I though we
would still have three connectors, just that DVI-D would become DVI-I. In fact
what should happen is that DVI-D becomes DVI-I and VGA vbios entry is ignored
for this board?
Is this something which can be done in radeon_atom_apply_quirks? I'll give it a
go.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-03-16 8:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 15:51 [Bug 47007] New: HDMI monitor polling causing 100ms rendering stalls bugzilla-daemon
2012-03-06 15:56 ` [Bug 47007] " bugzilla-daemon
2012-03-06 16:11 ` bugzilla-daemon
2012-03-06 16:12 ` bugzilla-daemon
2012-03-06 16:13 ` bugzilla-daemon
2012-03-06 16:15 ` bugzilla-daemon
2012-03-07 10:10 ` bugzilla-daemon
2012-03-07 10:42 ` bugzilla-daemon
2012-03-07 19:46 ` bugzilla-daemon
2012-03-07 19:47 ` bugzilla-daemon
2012-03-07 20:03 ` bugzilla-daemon
2012-03-08 9:56 ` bugzilla-daemon
2012-03-12 13:44 ` bugzilla-daemon
2012-03-12 14:56 ` bugzilla-daemon
2012-03-12 15:13 ` bugzilla-daemon
2012-03-12 18:34 ` bugzilla-daemon
2012-03-13 8:46 ` bugzilla-daemon
2012-03-13 11:44 ` bugzilla-daemon
2012-03-15 7:56 ` bugzilla-daemon
2012-03-15 8:14 ` bugzilla-daemon
2012-03-15 9:50 ` bugzilla-daemon
2012-03-15 10:52 ` bugzilla-daemon
2012-03-15 11:20 ` bugzilla-daemon
2012-03-15 13:10 ` bugzilla-daemon
2012-03-15 13:29 ` bugzilla-daemon
2012-03-15 13:59 ` bugzilla-daemon
2012-03-15 14:08 ` bugzilla-daemon
2012-03-15 14:57 ` bugzilla-daemon
2012-03-15 15:02 ` bugzilla-daemon
2012-03-15 15:03 ` bugzilla-daemon
2012-03-15 15:16 ` bugzilla-daemon
2012-03-15 15:34 ` bugzilla-daemon
2012-03-15 15:45 ` bugzilla-daemon
2012-03-15 16:13 ` bugzilla-daemon
2012-03-15 17:41 ` bugzilla-daemon
2012-03-16 3:54 ` bugzilla-daemon
2012-03-16 8:47 ` bugzilla-daemon [this message]
2012-03-16 13:18 ` bugzilla-daemon
2012-03-16 13:57 ` bugzilla-daemon
2012-03-16 14:04 ` bugzilla-daemon
2012-03-16 14:16 ` bugzilla-daemon
2012-03-16 14:46 ` bugzilla-daemon
2012-03-16 15:09 ` bugzilla-daemon
2012-03-16 15:16 ` bugzilla-daemon
2012-03-16 15:30 ` bugzilla-daemon
2012-03-16 15:35 ` bugzilla-daemon
2012-03-16 15:59 ` bugzilla-daemon
2012-03-16 16:09 ` bugzilla-daemon
2012-04-01 12:57 ` bugzilla-daemon
2012-04-01 12:57 ` 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-47007-502-FNgiMXTWGJ@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.