From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72051] [JUNIPER] with kernel 3.12 some HDMI screens are not recognized
Date: Tue, 17 Dec 2013 16:08:57 +0000 [thread overview]
Message-ID: <bug-72051-502-eBSNDfwLDy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72051-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 542 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72051
--- Comment #12 from Eugene Shalygin <eugene.shalygin+bugzilla.FDO@gmail.com> ---
Without the option, the message is not shown, but the HDMI screen is unusable:
every second or third frame is shown shifted by approx. 50 pixels downward.
When the screen is connected before boot, it is recognized always, but it does
not work every time when hot-plugged. So, in my case radeon.hw_i2c=1 seems to
be required option.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1366 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
next prev parent reply other threads:[~2013-12-17 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 20:30 [Bug 72051] New: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized bugzilla-daemon
2013-11-26 20:31 ` [Bug 72051] " bugzilla-daemon
2013-11-26 20:32 ` bugzilla-daemon
2013-11-26 20:33 ` bugzilla-daemon
2013-11-26 20:33 ` bugzilla-daemon
2013-11-26 22:15 ` bugzilla-daemon
2013-11-26 22:17 ` bugzilla-daemon
2013-11-27 15:50 ` bugzilla-daemon
2013-12-16 18:34 ` bugzilla-daemon
2013-12-16 23:40 ` bugzilla-daemon
2013-12-17 12:34 ` bugzilla-daemon
2013-12-17 13:43 ` bugzilla-daemon
2013-12-17 16:08 ` bugzilla-daemon [this message]
2013-12-17 16:15 ` bugzilla-daemon
2013-12-18 11:44 ` bugzilla-daemon
2019-11-19 8:40 ` 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-72051-502-eBSNDfwLDy@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;
as well as URLs for NNTP newsgroup(s).