From: Oliver Xymoron <oxymoron@waste.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: henrique <henrique@cyclades.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with random.c and PPC
Date: Fri, 16 Aug 2002 11:28:02 -0500 [thread overview]
Message-ID: <20020816162802.GF5418@waste.org> (raw)
In-Reply-To: <20020815210449.GA26993@opus.bloom.county>
On Thu, Aug 15, 2002 at 02:04:49PM -0700, Tom Rini wrote:
> On Thu, Aug 15, 2002 at 01:59:33PM -0600, Andreas Dilger wrote:
> > On Aug 15, 2002 12:03 -0700, Tom Rini wrote:
> > > On Thu, Aug 15, 2002 at 12:25:56PM -0600, Andreas Dilger wrote:
> > > > Maybe the PPC keyboard/mouse drivers do not add randomness?
> > >
> > > Well, how is this set for the i386 ones? I grepped around and I didn't
> > > really see anything, so I'm sort-of confused.
> >
> > I think it is something like "add_mouse_entropy" and "add_keyboard_entropy"
> > or similar. If you look at the random.c sources you can find the actual
> > function names and work backwards from there.
>
> Ah, thanks. In that case, no. It doesn't look like the input-layer USB
> keyboards contribute to entropy (but mice do), and I don't think the ADB
> ones do. I'll take a crack at adding this to keyboards monday maybe.
Tom, I'm working on a set of patches that completely change this
interface because there are a bunch of problems with the current
entropy accounting.
What PPC and other arches really need in this area is a higher
resolution timing source. The jiffies-based timing is rather
limiting, especially after the entropy accounting stops overestimating
things by orders of magnitude. Does the PPC port have a convenient way
to access the TBR or something similar?
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next prev parent reply other threads:[~2002-08-16 16:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 15:14 Problem with random.c and PPC henrique
2002-08-15 18:25 ` Andreas Dilger
2002-08-15 19:03 ` Tom Rini
2002-08-15 19:59 ` Andreas Dilger
2002-08-15 21:04 ` Tom Rini
2002-08-16 1:50 ` H. Peter Anvin
2002-08-16 16:33 ` Oliver Xymoron
2002-08-16 16:28 ` Oliver Xymoron [this message]
[not found] ` <20020816170126.GD26993@opus.bloom.county>
2002-08-16 17:15 ` Oliver Xymoron
-- strict thread matches above, loose matches on Subject: below --
2002-08-15 16:10 henrique
2002-08-16 10:00 Jon Burgess
2002-08-16 19:52 ` Oliver Xymoron
2002-08-16 17:51 ` henrique
2002-08-16 21:21 ` Ruth Ivimey-Cook
2002-08-17 0:47 ` Oliver Xymoron
2002-08-17 0:45 ` Oliver Xymoron
2002-08-17 6:05 ` Andreas Dilger
2002-08-17 7:23 ` Oliver Xymoron
2002-08-17 9:09 ` Andreas Dilger
2002-08-17 16:56 ` Oliver Xymoron
2002-08-19 9:29 ` Marco Colombo
2002-08-19 14:02 ` Oliver Xymoron
2002-08-19 15:11 ` Marco Colombo
2002-08-19 15:29 ` Oliver Xymoron
2002-08-19 16:20 ` Marco Colombo
2002-08-19 16:33 ` Oliver Xymoron
2002-08-19 20:23 ` Marco Colombo
2002-08-22 3:16 ` David Wagner
2002-08-16 20:52 ` Chris Friesen
2002-08-17 0:29 ` Oliver Xymoron
2002-08-22 3:19 ` David Wagner
2002-08-22 15:40 ` Chris Friesen
2002-08-22 17:25 ` Remco Post
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=20020816162802.GF5418@waste.org \
--to=oxymoron@waste.org \
--cc=henrique@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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