public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Folkert van Heusden <folkert@vanheusden.com>
To: Kalin KOZHUHAROV <kalin@thinrope.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 0/5] HW RNG cleanup & new drivers
Date: Sun, 30 Oct 2005 20:35:40 +0100	[thread overview]
Message-ID: <20051030193540.GD19592@vanheusden.com> (raw)
In-Reply-To: <dk32bf$quc$1@sea.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

> > [snip]
> >>Does anyone know if there is a hardware RNG in my Athlons?  XP-2800
> >>here, XP-1400 in the shop box, & a K6-III in the firewall.
> > It's a mainboard feature, not a CPU feature.
> And is there a docmentation on how to find which RNG device you have?
> Or is there lsrng (like lspci) :-)
> Most of the device names I have never heard of, but working with 5+ MB vendors and all the different
> models of MB I really have no idea where do I have this and that...
> So, any method of autodetecting a RNG device?
> And a question, I always wanted to ask: is there a cheap hardware random device usable in linux that
> is PCI/USB/serial whatever pluggable? For MBs without RNG in the chipset.

Consider:
audio-entropyd: use a cheap soundcard for generating entropy (http://www.vanheusden.com/aed/)
video-entropyd: use that obsolete webcam for same thing (http://www.vanheusden.com/ved/)


Folkert van Heusden

-- 
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, colored output, etc. etc. www.vanheusden.com/multitail/
----------------------------------------------------------------------
Get your PGP/GPG key signed at www.biglumber.com!
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 282 bytes --]

  reply	other threads:[~2005-10-30 19:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 19:12 [patch 0/5] HW RNG cleanup & new drivers Deepak Saxena
2005-10-29 19:12 ` [patch 1/5] Remove existing hw_random implementation Deepak Saxena
2005-10-29 19:12 ` [patch 2/5] Core HW RNG support Deepak Saxena
2002-01-01  5:46   ` Pavel Machek
2005-10-29 19:12 ` [patch 3/5] Intel IXP4xx driver Deepak Saxena
2005-10-29 19:12 ` [patch 4/5] x86 driver Deepak Saxena
2005-10-29 19:12 ` [patch 5/5] TI OMAP driver Deepak Saxena
2005-10-29 22:09 ` [patch 0/5] HW RNG cleanup & new drivers Jeff Garzik
2005-10-29 22:25   ` Linus Torvalds
2005-10-29 22:33     ` Jeff Garzik
2005-10-30 19:58       ` Deepak Saxena
2005-10-30  0:23   ` Gene Heskett
2005-10-30 14:31     ` Alistair John Strachan
2005-10-30 18:08       ` Kalin KOZHUHAROV
2005-10-30 19:35         ` Folkert van Heusden [this message]
2005-10-30 20:02   ` Deepak Saxena
2005-10-30 22:35     ` Linus Torvalds
2005-10-30 23:04       ` H. Peter Anvin

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=20051030193540.GD19592@vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=kalin@thinrope.net \
    --cc=linux-kernel@vger.kernel.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