From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: PCI configuration space of the VGA controller and laptop LCD picture quality.
Date: Thu, 13 Jan 2011 15:29:45 -0500 [thread overview]
Message-ID: <4D2F60B9.0@earthlink.net> (raw)
In-Reply-To: <360714.55093.qm@web110503.mail.gq1.yahoo.com>
On 2011/01/13 11:58 (GMT-0800) SD composed:
> I still can't figure out why Fedora (13,14,15) shows LCD picture much
> worse then opensuse 11.1.
What does "worse" mean? Most people who see "worse" are actually complaining
about fonts, and in most cases even then they don't define what is "worse"
about the fonts. Can you upload screenshots of both so people can see what
"worse" means?
That said, Fedora sets some system wide variables that affect X
quality/behavior in /etc/X11/Xresources:
Xft.dpi
Xft.hintstyle
Xft.hinting
openSUSE doesn't do that. If you comment those away in Fedora, or match the
Xft.dpi number to your LCD's actual DPI, you may find the difference is
reduced or disappears, particularly if actual DPI varies more than nominally
from the Xft.dpi setting. OTOH, they may produce little or no improvement if
you've set your DTE to force DPI or tweaked its font smoothing settings.
If you need to comment further, also specify which DTE you use, as that can
matter as well in future responses.
> As long as I still want to use Fedora on my laptop I would like to ask -
> can picture quality be spoiled by different PCI configuration?
I highly doubt it, other than if it's wrong there's no picture to assess the
quality of.
--
"How much better to get wisdom than gold, to choose
understanding rather than silver." Proverbs 16:16 NKJV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2011-01-13 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 19:58 PCI configuration space of the VGA controller and laptop LCD picture quality SD
2011-01-13 20:29 ` Felix Miata [this message]
2011-01-14 7:50 ` SD
2011-01-14 10:03 ` SD
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=4D2F60B9.0@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.