From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problem with xf86-video-ati & nvidia-drivers
Date: Sun, 17 Jul 2011 16:28:19 -0700 [thread overview]
Message-ID: <CAN0CFw2mXo7wfxnwD-mfKHM7E3QzS8_GwrtraU3CetJ=B=id7A@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiA5DK4SA+y8HmSEj7iJOqsOjQv-770nOJHL7_SKsLA1zQ@mail.gmail.com>
>>>> I was thinking about this. The digital HDMI signal must be converted
>>>> into an analog signal at some point if it's being represented as light
>>>> on a TV screen. Electrical interference generated by the computer and
>>>> traveling up the HDMI wire should have its chance to affect things
>>>> (i.e. create weird shadows) at that point, right?
>>>
>>> Not with DFPs. Those work digital even internally. I assume of course that
>>> his HDMI TV *is* a DFP.
>>
>> But at some point the 1s and 0s must be converted to some sort of an
>> analog signal if only right behind the diode. A diode must be
>> presented with a signal in some sort of analog form in order to
>> illuminate, right? Digital is just a figment of our imagination after
>> all.
>
> Sure, but that couldn't introduce ghosting as shown in the picture.
> Ghosting represents the image being offset in its intended raster
> coordinates. By the time a diode is turned on or off, the decision if
> which diode a signal goes to has already been made.
True, but *is* that D/A conversion made right behind each diode?
- Grant
next prev parent reply other threads:[~2011-07-17 23:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 23:21 [gentoo-user] Problem with xf86-video-ati & nvidia-drivers Grant
2011-07-10 0:20 ` meino.cramer
2011-07-11 23:48 ` Grant
2011-07-12 22:33 ` Grant
2011-07-13 2:27 ` meino.cramer
2011-07-13 15:55 ` Roger Mason
2011-07-13 16:17 ` meino.cramer
2011-07-13 17:13 ` Grant
2011-07-13 17:38 ` meino.cramer
2011-07-14 19:44 ` Grant
2011-07-14 20:07 ` Michael Mol
2011-07-14 23:29 ` Grant
2011-07-14 20:23 ` [gentoo-user] " Nikos Chantziaras
2011-07-14 23:30 ` Grant
2011-07-17 16:22 ` Grant
2011-07-17 16:47 ` Nikos Chantziaras
2011-07-17 16:54 ` Grant
2011-07-17 21:53 ` Michael Mol
2011-07-17 23:28 ` Grant [this message]
2011-07-18 13:18 ` [gentoo-user] " Stroller
2011-07-18 22:52 ` Grant
2011-07-19 0:56 ` Grant
2011-07-19 16:03 ` Daniel Frey
2011-07-19 19:41 ` Grant
2011-07-19 21:00 ` Mick
2011-07-20 18:38 ` Grant
2011-07-20 14:29 ` Stroller
2011-07-20 15:29 ` Michael Mol
2011-07-19 2:01 ` [gentoo-user] " Volker Armin Hemmann
2011-07-19 20:35 ` Grant
2011-07-19 20:54 ` Michael Mol
2011-07-20 21:22 ` Grant
2011-07-13 7:19 ` Nikos Chantziaras
2011-07-13 17:27 ` Grant
2011-07-13 7:13 ` Nikos Chantziaras
2011-07-13 12:25 ` Mick
2011-07-13 14:42 ` Nikos Chantziaras
2011-07-13 16:36 ` Mick
2011-07-16 16:22 ` Mick
2011-07-13 17:23 ` Grant
2011-07-14 6:13 ` Nikos Chantziaras
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='CAN0CFw2mXo7wfxnwD-mfKHM7E3QzS8_GwrtraU3CetJ=B=id7A@mail.gmail.com' \
--to=emailgrant@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