From: "Jan Beulich" <JBeulich@suse.com>
To: "Shawn Starr" <shawn.starr@rogers.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [Intel][RNG] PCI IDs commented out for 82801I (ICH9 Mobile and non-mobile)?
Date: Thu, 21 Mar 2013 08:00:43 +0000 [thread overview]
Message-ID: <514ACC3B02000078000C765B@nat28.tlf.novell.com> (raw)
In-Reply-To: <514A2195.9060402@zytor.com>
>>> On 20.03.13 at 21:52, "H. Peter Anvin" <hpa@zytor.com> wrote:
> On 03/20/2013 01:42 PM, Shawn Starr wrote:
>> Hello folks,
>>
>> I was looking at why I can't load the Intel RNG driver (or why it doesn't
> load automatically) and
>> it just so happens I have both the mobile and non-mobile ICH9 chipset.
> Looking at the driver I noticed:
>>
>> /* BAM, CAM, DBM, FBM, GxM
>> { PCI_DEVICE(0x8086, 0x2448) }, */
>>
>> /* BA, CA, DB, Ex, 6300, Fx, 631x/632x, Gx
>> { PCI_DEVICE(0x8086, 0x244e) }, */
>>
>> IDs from both machines:
>>
>> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
> [8086:2448] (rev 93)
>> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e]
> (rev 92)
>>
>> I saw a thread from 2006 explaining the 50% chance there's no RNG (but these
> days all modern chipsets should have an RNG) and I know
>> this chipset I have does have an RNG so I'd like to use the HW random
> generator vs software.
>>
>
> Do you know that for sure?
I haven't seen _any_ half way recent system having this old style
FWH.
>> Do we need to revisit this? Even if I try to force it to load it still fails:
>>
>> # modprobe intel_rng no_fwh_detect=-1 or =1
>> modprobe: ERROR: could not insert 'intel_rng': No such device
>>
>
> The Intel RNG of that era lived in the Firmware Hub (a.k.a. BIOS flash)
> rather than in the chipset proper... so even with the right chipset you
> might or might not actually have the the RNG. The code really detects
> the presence of a chipset which could support a FWH flash part.
>
> Jan, in c24c95a085c6b52c11c2f5afecc38b0ca143cdae you comment out a
> number of PCI IDs. Was that intentional?
Yes, as explained in the description (albeit, reading it now, 6.5
years later, again, I admit it could have been written in better
ways): Before that change, the selection of which particular
device from a chipset was chose was more or less random. But
with the new code now actually accessing the device, it has to be
the LPC one. And the list of devices stops at ICH7 - that was,
afaict now, the newest one in existence back then. Therefore, if
there really are newer chipsets with FWH, the code would need
auditing for correctness when intending to add further PCI IDs.
Jan
next prev parent reply other threads:[~2013-03-21 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 20:42 [Intel][RNG] PCI IDs commented out for 82801I (ICH9 Mobile and non-mobile)? Shawn Starr
2013-03-20 20:52 ` H. Peter Anvin
2013-03-21 8:00 ` Jan Beulich [this message]
2013-03-20 21:03 ` Bjørn Mork
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=514ACC3B02000078000C765B@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.com \
/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