From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 20142] enabling underscan by default behaves badly with so many monitors.
Date: Wed, 13 Oct 2010 15:18:53 GMT [thread overview]
Message-ID: <201010131518.o9DFIrST009548@demeter1.kernel.org> (raw)
In-Reply-To: <bug-20142-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=20142
--- Comment #6 from Alex Deucher <alexdeucher@gmail.com> 2010-10-13 15:18:51 ---
It sucks for everyone ;) It would be nice if there was an EDID flag for
overscan.
I would be a good idea to expose connector properties via xorg.conf and
additionally via sysfs, but it's a fair amount of work and I haven't had time
to work on it unfortunately.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
--
next prev parent reply other threads:[~2010-10-13 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 10:34 [Bug 20142] New: enabling underscan by default behaves badly with so many monitors bugzilla-daemon
2010-10-12 10:48 ` [Bug 20142] " bugzilla-daemon
2010-10-12 15:10 ` bugzilla-daemon
2010-10-13 0:05 ` bugzilla-daemon
2010-10-13 0:39 ` bugzilla-daemon
2010-10-13 8:45 ` bugzilla-daemon
2010-10-13 15:18 ` bugzilla-daemon [this message]
2010-10-27 4:00 ` bugzilla-daemon
2010-11-03 18:40 ` bugzilla-daemon
2011-01-10 11:59 ` bugzilla-daemon
2012-08-14 11:07 ` bugzilla-daemon
2012-08-14 11:21 ` 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=201010131518.o9DFIrST009548@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.