public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: dsaxena@plexity.net
Cc: jgarzik@pobox.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] RNG rewrite...
Date: Sat, 15 Oct 2005 06:40:49 -0400	[thread overview]
Message-ID: <4350DCB1.7010201@pobox.com> (raw)
In-Reply-To: <20051015043120.GA5946@plexity.net>

Deepak Saxena wrote:
> I want to add support for the RNG on Intel's IXP4xx NPU and 
> looking at the existing hw-random.c code, it is written with
> the assumption that the RNG is on the PCI bus. I can put a
> big #ifdef ARCH_IXP4XX in there but instead I would rather
> rewrite the damn thing to use the device model and have a rng
> device class with individual drivers for each RNG model, including
> IXP4xx. I'll keep the miscdev interface around but will add a
> new interface under /sys/class/rng that the userspace tools 
> can transition to. Is this OK with folks?

How does the hardware export RNG functionality?  CPU insn?  Magic memory 
address?  Can it be done 100% in userspace?


> One question I have is about the following comment:
> 
>  * This data only exists for exporting the supported
>  * PCI ids via MODULE_DEVICE_TABLE.  We do not actually
>  * register a pci_driver, because someone else might one day
>  * want to register another driver on the same PCI id.
> 
> Why? Is there something else on those IDs that another driver might
> care about?

They are bridge ids, not device ids.

	Jeff




  reply	other threads:[~2005-10-15 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15  4:31 [RFC] RNG rewrite Deepak Saxena
2005-10-15 10:40 ` Jeff Garzik [this message]
2005-10-16  0:53   ` Deepak Saxena
2005-10-17 23:15     ` H. Peter Anvin
2005-10-17 23:26       ` Jeff Garzik
2005-10-18  0:22         ` H. Peter Anvin
2005-10-17 23:31     ` Jeff Garzik
2005-10-18  1:00       ` Deepak Saxena
2005-10-18  1:05         ` Deepak Saxena
2005-10-18  1:09         ` Jeff Garzik

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=4350DCB1.7010201@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dsaxena@plexity.net \
    --cc=jgarzik@pobox.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