From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72648] All 3 monitor EDIDs show the same
Date: Fri, 13 Dec 2013 18:19:50 +0000 [thread overview]
Message-ID: <bug-72648-502-VToCgPGy5G@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72648-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 633 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72648
--- Comment #9 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #8)
> fwiw, the last one is an AOC E2252S monitor,
> I guess "LNX" is a placeholder/default due to the Raw EDID errors,
> happening since I plugged in the AOC.
Yes, it comes from edid/1920x1080.bin
>
> So I agree that sysfs is somehow to blame for the original worry.
> I guess I'll post over on LKML, and refer back to this bug-rpt.
> After testing if the EDID cmdline addition might be involved.
You might try dri-devel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1496 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-13 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 19:27 [Bug 72648] New: All 3 monitor EDIDs show the same bugzilla-daemon
2013-12-12 20:53 ` [Bug 72648] " bugzilla-daemon
2013-12-13 15:35 ` bugzilla-daemon
2013-12-13 15:37 ` bugzilla-daemon
2013-12-13 15:38 ` bugzilla-daemon
2013-12-13 16:18 ` bugzilla-daemon
2013-12-13 16:24 ` bugzilla-daemon
2013-12-13 16:50 ` bugzilla-daemon
2013-12-13 18:12 ` bugzilla-daemon
2013-12-13 18:19 ` bugzilla-daemon [this message]
2013-12-13 18:22 ` bugzilla-daemon
2013-12-13 23:29 ` bugzilla-daemon
2013-12-16 23: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-72648-502-VToCgPGy5G@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).