public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?
Date: Wed, 25 Aug 2010 21:20:50 +0200	[thread overview]
Message-ID: <201008252120.51120.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <201008251730.30210.peter@humphrey.ukfsn.org>

Apparently, though unproven, at 18:30 on Wednesday 25 August 2010, Peter 
Humphrey did opine thusly:

> On Wednesday 25 August 2010 15:44:58 Mick wrote:
> > Fair enough, but anything other than the native resolution on an LCD
> > monitor will end looking distorted or blurred.
> 
> Why? Granted, LCD panels are made up of discreet pixels, but so are
> CRTs: the dots are deposited in trios, each illuminated through a hole
> in the shadow mask.

That is incorrect.

A CRT display is not pixelated - it is made up of triads (not trios) and there 
is no way of knowing which triad is lit up for any given "logical pixel". The 
electron beam is an analogue signal and it works mainly because there are more 
triads than logical pixels.

LCDs on the other hand are pixelated. Each group of three display elements is 
addressable in a consistent fashion. 

CRTs and LCDs are about as different as cassette tapes and CDs, and just as 
incompatible. Both cases need lots of magic voodoo to arrive at some 
commonality.


-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-08-25 19:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24  2:27 [gentoo-user] New HD monitor stretches everything. How to teach Xorg? Kevin O'Gorman
2010-08-24  2:38 ` Bill Longman
2010-08-24  3:58   ` dennisonic
2010-08-24  5:24     ` Kevin O'Gorman
2010-08-24  5:40       ` d.fedorov
2010-08-24  7:30         ` Petri Rosenström
2010-08-24 17:09         ` Kevin O'Gorman
2010-08-24 10:23       ` Adam Carter
2010-08-24 11:27         ` Mick
2010-08-24 17:10           ` Kevin O'Gorman
2010-08-24 18:48             ` Paul Hartman
2010-08-24 22:07               ` Kevin O'Gorman
2010-08-24 22:18                 ` Paul Hartman
2010-08-24 22:37                   ` Dale
2010-08-24 22:59                     ` Paul Hartman
2010-08-24 23:10                       ` dhk
2010-08-25  0:00                         ` Kevin O'Gorman
2010-08-25  0:07                         ` Dale
2010-08-25 10:38                           ` dhk
2010-08-25  0:03                   ` Kevin O'Gorman
2010-08-25 14:17                     ` Paul Hartman
2010-08-25 14:25                       ` Mick
2010-08-25 14:38                         ` Paul Hartman
2010-08-25 14:44                           ` Mick
2010-08-25 14:57                             ` Paul Hartman
2010-08-25 20:29                               ` Kevin O'Gorman
2010-08-27  2:00                                 ` Walter Dnes
2010-08-25 16:30                             ` Peter Humphrey
2010-08-25 16:39                               ` Maciej Grela
2010-08-25 17:09                                 ` Peter Humphrey
2010-08-25 16:39                               ` Maciej Grela
2010-08-25 19:20                               ` Alan McKinnon [this message]
2010-08-24  2:51 ` Adam Carter
2010-08-25 20:48 ` Håkon Alstadheim
2010-08-25 20:56   ` Kevin O'Gorman
2010-08-26  3:11     ` Kevin O'Gorman

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=201008252120.51120.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.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