From: "gmu 2k6" <gmu2006@gmail.com>
To: "Michael Buesch" <mb@bu3sch.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hwrng on 82801EB/ER (ICH5/ICH5R) fails rngtest checks
Date: Thu, 27 Jul 2006 14:20:07 +0000 [thread overview]
Message-ID: <f96157c40607270720n1dd5443avfdb53641a1cdad6f@mail.gmail.com> (raw)
In-Reply-To: <200607271529.39549.mb@bu3sch.de>
On 7/27/06, Michael Buesch <mb@bu3sch.de> wrote:
> On Wednesday 26 July 2006 21:44, gmu 2k6 wrote:
> > > But could you try the following patch on top of latest git?
> > > It's just a random test, but I think it's worth trying.
> > > Let's see if it works around the issue.
> > >
> > > Index: linux-2.6/drivers/char/hw_random/intel-rng.c
> > > ===================================================================
> > > --- linux-2.6.orig/drivers/char/hw_random/intel-rng.c 2006-06-27 17:48:13.000000000 +0200
> > > +++ linux-2.6/drivers/char/hw_random/intel-rng.c 2006-07-26 17:27:03.000000000 +0200
> > > @@ -104,9 +104,14 @@
> > > int err = -EIO;
> > >
> > > hw_status = hwstatus_get(mem);
> > > + hw_status = hwstatus_set(mem, hw_status & ~INTEL_RNG_ENABLED);
> > > + hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
> > > +#if 0
> > > + hw_status = hwstatus_get(mem);
> > > /* turn RNG h/w on, if it's off */
> > > if ((hw_status & INTEL_RNG_ENABLED) == 0)
> > > hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
> > > +#endif
> > > if ((hw_status & INTEL_RNG_ENABLED) == 0) {
> > > printk(KERN_ERR PFX "cannot enable RNG, aborting\n");
> > > goto out;
> >
> > well as it didn't work, are you sure it was not intended to be more like this:
> > @@ -104,9 +104,14 @@
> > int err = -EIO;
> >
> > hw_status = hwstatus_get(mem);
> > + hw_status = hwstatus_set(mem, hw_status & ~INTEL_RNG_ENABLED);
> > + hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
> > +#if 0
> > /* turn RNG h/w on, if it's off */
> > if ((hw_status & INTEL_RNG_ENABLED) == 0)
> > hw_status = hwstatus_set(mem, hw_status | INTEL_RNG_ENABLED);
> > +#endif
> > if ((hw_status & INTEL_RNG_ENABLED) == 0) {
> > printk(KERN_ERR PFX "cannot enable RNG, aborting\n");
> > goto out;
> >
> > ?
>
> I don't think that makes a difference to the generated code, does it?
I will test it now as you seem to be interested in the results.
actually I was just curious what sense it made to do
hw_status = hwstatus_get(mem);
twice, though I'm not informed about the semantics there so I could be wrong
in interpreting the API on that level.
next prev parent reply other threads:[~2006-07-27 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060725222209.0048ed15.akpm@osdl.org>
2006-07-26 13:44 ` Michael Buesch
2006-07-26 14:21 ` gmu 2k6
2006-07-26 14:49 ` Michael Buesch
2006-07-26 14:52 ` gmu 2k6
2006-07-26 15:30 ` Michael Buesch
2006-07-26 15:42 ` gmu 2k6
2006-07-26 19:44 ` gmu 2k6
2006-07-27 13:29 ` Michael Buesch
2006-07-27 14:20 ` gmu 2k6 [this message]
2006-07-27 14:32 ` Michael Buesch
2006-07-27 15:07 ` gmu 2k6
2006-07-26 14:23 ` gmu 2k6
2006-07-25 19:37 gmu 2k6
2006-07-25 19:44 ` 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=f96157c40607270720n1dd5443avfdb53641a1cdad6f@mail.gmail.com \
--to=gmu2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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
all inboxes | Powered by JetHome®