From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Using quirks to fix incorrect Monitor physical size
Date: Mon, 13 Sep 2010 07:14:26 -0400 [thread overview]
Message-ID: <4C8E0792.3090404@earthlink.net> (raw)
In-Reply-To: <1016714344.725559.1284372628877.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
On 2010/09/13 10:10 (GMT) Nasa composed:
>> Is there a way to tell the driver to use DisplaySize to pass the
>> correct dimensions to
>> the i915 driver? from my searches, I saw the following note:
>> News: xf86-video-intel only supports KMS now
>> 2010-02-11 - Jan de Groot
>> With the move of xf86-video-intel 2.10.0 to extra, support for UMS has
>> been removed from the intel driver. This means that KMS is a
>> requirement now.
>> Does this mean that there's no way to override incorrect (or in my
>> case) missing EDID info? I am assuming so,
>> which is why I am asking about quirks. Thanks in advance,
> So...
> Given the lack of a response, I am guessing this means the drivers don't
> support this capability. Is there a reason for limiting user capabilities?
> Removing users ability to work around hardware issues just seems like the
> wrong way to go. At least in my humble opinion.
I'm not implying what you're asking for is unreasonable or too much to ask,
but have you tried Meego's vesa or fbdev drivers with KMS disabled? If those
don't cut it for you, maybe you just need to wait a while longer for the
Intel devs to replace more of what got discarded when UMS got dumped from its
driver. Maybe you need to file an xorg bug to help that along.
What was on the laptop when you bought it? You'd think the vendor would have
shipped something works with its hardware. I can't tell from
http://lists.freedesktop.org/archives/intel-gfx/2010-August/007907.html what
it was you bought.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2010-09-13 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <631910804.725536.1284372575092.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-13 10:10 ` Using quirks to fix incorrect Monitor physical size Nasa
2010-09-13 11:14 ` Felix Miata [this message]
2010-09-13 11:42 ` Nasa
2010-09-13 13:16 ` Felix Miata
2010-09-13 13:44 ` The Fungi
[not found] <1524502115.868672.1284559892980.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-15 14:18 ` Nasa
[not found] <728542343.735537.1284385743146.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-13 13:57 ` Nasa
2010-09-13 21:58 ` Felix Miata
2010-09-13 22:42 ` Nasa
2010-09-15 13:53 ` Felix Miata
[not found] <439980487.671370.1284230896263.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-11 18:56 ` Nasa
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=4C8E0792.3090404@earthlink.net \
--to=mrmazda@earthlink.net \
--cc=intel-gfx@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.