public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problem with xf86-video-ati & nvidia-drivers
Date: Wed, 20 Jul 2011 14:22:01 -0700	[thread overview]
Message-ID: <CAN0CFw0ngSCOmWvFK4da3qn8LCO738KacXTqUS-xpxECsyK3cA@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiBB-GopNKA85_fqooyk-uYGthtfnzpa7uo2k1J3wRBn_A@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?
>>>
>>> no.
>>>
>>> If your tv is a standard flat panel, the sub pixels only go from on to off and
>>> back. Nothing else. There is no analog signal, no transformation nothing. And
>>> off means 'let light through' and on 'black'
>>
>> Every digital signal is encoded into an analog signal.  I think it
>> would take some serious EMI to sufficiently change the characteristics
>> of an analog signal so as to create an error in the overlying digital
>> signal if that signal is traveling along a wire.  I can imagine it
>> happens but I would think it's rare.  Even if that signal were
>> altered, I would think it just about impossible that anything but an
>> error could be produced.
>>
>> Whether an LED is on or off is determined by whether or not it is
>> forward biased.  Biasing is established by analog voltages and/or
>> currents, and those can be altered by EMI.  Again, I would think it's
>> very rare that EMI could affect an LED's forward biasing and change
>> its state from on to off or off to on.
>>
>> However, what color an LED emits is determined by the energy gap of
>> the semiconductor which is very much an analog process.  How could it
>> be anything else?  How do you tell a photon to emit a certain color by
>> feeding it 1's and 0's?  There has to be at least one D/A conversion
>> somewhere between the digital signal and the emittance of the LED, and
>> that is the most likely point for EMI to affect the final output.
>>
>>> If you have an led display it is pretty much the same. All the levels you see
>>> are achieved with fast switching. There are no analog levels.
>>>
>>> Stroller is probably correct with overscan/underscan.
>>>
>>> But that has nothing to do with digital/analog conversion.
>>>
>>>
>>>> Digital is just a figment of our imagination after
>>>> all.
>>>
>>> emm, no, seriously not.
>>
>> It is though.  It only exists in the conceptual world, not the
>> physical world.  If you want to do anything with your digital signal
>> besides change it, store it, or transfer it, there must be a D/A
>> conversion.
>
> You're thinking of PCM. (And that's what I was thinking of, earlier,
> too). I assume Stroller and Volker are talking about PWM, where a
> perceived analog value is achieved by rapidly turning a signal from
> full-on to full-off.
>
> (Yes, there's no such thing as pure-digital in the physical world. The
> confusion here appears to be in PWM vs PCM.)
> --
> :wq

Everything I said above applies to both PCM and PWM.  They are only
conceptual layers built on top of a physical/analog base.  PWM
switching from full-on to full-off and back is an analog process
representing digital data in order to represent an analog signal.

- Grant



  reply	other threads:[~2011-07-20 21:23 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
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 [this message]
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=CAN0CFw0ngSCOmWvFK4da3qn8LCO738KacXTqUS-xpxECsyK3cA@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