From: "Jan Beulich" <jbeulich@novell.com>
To: "gmu 2k6" <gmu2006@gmail.com>
Cc: <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix Intel RNG detection
Date: Thu, 27 Jul 2006 17:43:32 +0200 [thread overview]
Message-ID: <44C8FB44.76E4.0078.0@novell.com> (raw)
In-Reply-To: <f96157c40607270835l34cd0de1w8c8a0d95ba8ee39f@mail.gmail.com>
># dmesg | grep rng
>intel_rng: FWH not detected
>
>looks like this ProLiant box with the ICH5 chip has no usable RNG
>included, or should it?
A configuration like this is what actually motivated me to write the
patch. You need to remember that the RNG doesn't live in the ICH, but in
the FWH (which is a different chip not showing up as a separate device
anywhere) with only some access parameters being configured via the LPC
device inside the ICH.
Jan
next prev parent reply other threads:[~2006-07-27 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:23 [PATCH] fix Intel RNG detection Jan Beulich
2006-07-27 14:23 ` Michael Buesch
2006-07-27 15:16 ` Jan Beulich
2006-07-27 15:18 ` gmu 2k6
2006-07-27 15:35 ` gmu 2k6
2006-07-27 15:43 ` Jan Beulich [this message]
2006-07-27 15:51 ` gmu 2k6
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=44C8FB44.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=gmu2006@gmail.com \
--cc=jgarzik@pobox.com \
--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