From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: mpm@selenic.com
Cc: akpm@linux-foundation.org, linux-mips@linux-mips.org,
ralf@linux-mips.org, linux-kernel@vger.kernel.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH] hwrng: Add TX4939 RNG driver
Date: Mon, 01 Jun 2009 02:18:07 +0900 (JST) [thread overview]
Message-ID: <20090601.021807.250571902.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <1243789210.22069.23.camel@calx>
On Sun, 31 May 2009 12:00:09 -0500, Matt Mackall <mpm@selenic.com> wrote:
> > >From the datasheet:
> >
> > The quality of the random numbers generated immediately after
> > reset can be insufficient. Therefore, do not use random
> > numbers obtained from the first and second generations; use
> > the ones from the third or subsequent generation.
>
> Does the datasheet say anything about -how- the random numbers are
> produced? Most physical sources that I'm aware of don't have this sort
> of issue. But some pseudo-RNGs do. So this looks a little worrisome.
Nothing for "how". If a RNG was actually a pseudo-RNG, does anything
a driver should do? Any future plan to select one RNG from multiple
sources based on randomness grade?
---
Atsushi Nemoto
next prev parent reply other threads:[~2009-05-31 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 15:02 [PATCH] hwrng: Add TX4939 RNG driver Atsushi Nemoto
2009-05-29 23:29 ` Andrew Morton
2009-05-31 1:30 ` Herbert Xu
2009-05-31 16:18 ` Ralf Baechle
2009-05-31 16:45 ` Atsushi Nemoto
2009-05-31 16:45 ` Atsushi Nemoto
2009-05-31 17:00 ` Matt Mackall
2009-05-31 17:18 ` Atsushi Nemoto [this message]
2009-06-02 3:53 ` Herbert Xu
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=20090601.021807.250571902.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mpm@selenic.com \
--cc=ralf@linux-mips.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