From: John Bradford <john@grabjohn.com>
To: list@fluent2.pyramid.net (Stephen Satchell)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Want a random entropy source?
Date: Sat, 28 Dec 2002 16:00:25 +0000 (GMT) [thread overview]
Message-ID: <200212281600.gBSG0P4r001160@darkstar.example.net> (raw)
In-Reply-To: <5.2.0.9.0.20021228073445.01d386c0@fluent2.pyramid.net> from "Stephen Satchell" at Dec 28, 2002 07:40:29 AM
> I was astonished to see that the resulting signal is a white-noise
> pattern with a slight emphasis at the high end (when sampled at 44
> kilosamples per second). In short, it looks like diode noise with a
> 4 kilohertz square wave thrown in.
> "That suggests to me that this would make a fair source of random samples,
> especially after you slot out the interfering signal.
How can you guarantee that you are sampling noise, though, what if a
sound card was picking up 50 Hz mains hum, for example, that would
de-randomise the data quite a bit.
> "How many computers don't have cheap sound cards and CD-ROM drives?"
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.
John.
next prev parent reply other threads:[~2002-12-28 15:52 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 [this message]
2002-12-28 16:38 ` Dr. David Alan Gilbert
2002-12-28 16:47 ` Russell King
2002-12-28 17:15 ` John Bradford
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=200212281600.gBSG0P4r001160@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=list@fluent2.pyramid.net \
/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.