public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: rmk@arm.linux.org.uk (Russell King)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Want a random entropy source?
Date: Sat, 28 Dec 2002 17:15:46 +0000 (GMT)	[thread overview]
Message-ID: <200212281715.gBSHFkf3001354@darkstar.example.net> (raw)
In-Reply-To: <20021228164750.A5217@flint.arm.linux.org.uk> from "Russell King" at Dec 28, 2002 04:47:50 PM

> > I have never understood how a 16-bit DAC or ADC can have noise above
> > 96 dB.  Surely _by definition_ a 16-bit DAC or ADC is one that does
> > not have noise above that level.
> 
> You're assuming that the ADC input is coupled to a noiseless source.
> Most ADCs have a chunk of analogue circuitry just before them which
> is a nice source of noise.
> 
> Not only will noise be picked up via disconnected inputs, but it will
> also be picked up via the power supply and ground connections to that
> analogue circuit.  How much of that noise gets into the ADC input is
> dependent on the quality, design and physical layout of the analogue
> circuit.

Right...  So basically it can be claimed to be a 16-bit ADC as long as
it is noiseless above 96 dB, when all of the inputs to the ADC are
correctly terminated directly at the ADC inputs.

I just think it's funny that loads of "16-bit" soundcards are
effectively only 12-bit soundcards :-).  Especially as that's about
the noise-floor of good quality vinyl :-).

> (As a side note, it's interesting that (what used to be) Crystal
> Semiconductor published a large chunk of information on the layout of
> boards including the routing of power supplies for combined digital
> and analogue circuits (and ADCs fall into that category.))

Good idea - I'd be grateful if more manufacturers would supply a
datasheet at all :-).

John.

  reply	other threads:[~2002-12-28 17:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 16:16 two 2.5 modules bugs Mikael Pettersson
2002-12-27 23:24 ` Petr Vandrovec
2002-12-28 10:37 ` Rusty Russell
2002-12-28 15:40   ` Want a random entropy source? Stephen Satchell
2002-12-28 16:00     ` John Bradford
2002-12-28 16:38       ` Dr. David Alan Gilbert
2002-12-28 16:47       ` Russell King
2002-12-28 17:15         ` John Bradford [this message]
2002-12-28 20:28       ` Folkert van Heusden
2002-12-28 20:39         ` John Bradford
2002-12-28 20:53           ` Folkert van Heusden
2002-12-28 23:20         ` Stephen Satchell
2002-12-28 23:41           ` John Bradford
2002-12-28 20:27     ` Folkert van Heusden

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=200212281715.gBSHFkf3001354@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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