public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Eric Van Buggenhaut <ericvb@debian.org>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com, mpm@selenic.com
Subject: Re: [hw_random] device not detected/patch
Date: Wed, 4 Jan 2006 20:54:38 +0100	[thread overview]
Message-ID: <20060104195438.GT3831@stusta.de> (raw)
In-Reply-To: <20060102000856.GA11491@alterna.homelinux.org>

Hi Eric,

Jeff and Matt (Cc'ed) should hopefully be able to answer your questions.

cu
Adrian


On Mon, Jan 02, 2006 at 01:08:57AM +0100, Eric Van Buggenhaut wrote:
> I run a TP42 with 2.6.14.2
> 
> One of the pci device is
> 
> 0000:00:1e.0 0604: 8086:2448 (rev 81)
>         Flags: bus master, fast devsel, latency 0
>         Bus: primary=00, secondary=02, subordinate=08, sec-latency=64
>         I/O behind bridge: 00004000-00008fff
>         Memory behind bridge: c0200000-cfffffff
>         Prefetchable memory behind bridge: e8000000-efffffff
> 
> 
> discover sees it as a hw_random device
> 
> # grep 80862448 /lib/discover/pci.lst 
>         80862448        bridge  i810_rng        82801 Mobile PCI Bridge
> 
> 
> and tries to load i810_rng module when support is really in hw_random:
> 
> # cat drivers/char/hw_random.c
> [...]
> static struct pci_device_id rng_pci_tbl[] = {
>         { 0x1022, 0x7443, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_amd },
>         { 0x1022, 0x746b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_amd },
> 
>         { 0x8086, 0x2418, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x2428, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x2448, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x244e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x245e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
> 
>         { 0, }, /* terminate list */
> };
> 
> 
> device isn't detected though:
> 
> # modprobe hw_random
> FATAL: Error inserting hw_random (/lib/modules/2.6.14.2n/kernel/drivers/char/hw_random.ko): No such device
> 
> hw_random: RNG not detected
> 
> Why wouldn't module detect the device ?
> 
> 
> OTOH, pci.lst also lists device 80862430 as another RNG
> 
> # grep 80862430 /lib/discover/pci.lst 
>         80862430        bridge  i810_rng        82801AB PCI Bridge
> 
> but it's not listed in rng_pci_tbl[]
> 
> Does
> 
> --- drivers/char/hw_random.c.orig       2005-12-22 19:36:00.000000000 +0100
> +++ drivers/char/hw_random.c    2005-12-22 19:36:16.000000000 +0100
> @@ -155,6 +155,7 @@
>  
>         { 0x8086, 0x2418, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x2428, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
> +       { 0x8086, 0x2430, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x2448, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x244e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
>         { 0x8086, 0x245e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, rng_hw_intel },
> 
> seem reasonable ?
> 
> Please CC me on reply
> 
> -- 
> Eric VAN BUGGENHAUT
> ericvb@debian.org

      reply	other threads:[~2006-01-04 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02  0:08 [hw_random] device not detected/patch Eric Van Buggenhaut
2006-01-04 19:54 ` Adrian Bunk [this message]

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=20060104195438.GT3831@stusta.de \
    --to=bunk@stusta.de \
    --cc=ericvb@debian.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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