All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] i2cdetect fails on a Asus P5ND2-Sli Deluxe
Date: Fri, 09 Dec 2005 20:35:22 +0000	[thread overview]
Message-ID: <20051209213522.4415984b.khali@linux-fr.org> (raw)
In-Reply-To: <4399D312.1010109@free.fr>

Hi Fred,

> And lspci sounds good :
> 
> 0000:00:0a.0 ISA bridge: nVidia Corporation: Unknown device 0030 (rev a3)
>         Subsystem: Asustek Computer, Inc.: Unknown device 818a
>         Flags: bus master, 66MHz, fast devsel, latency 0
> 
> 0000:00:0a.1 SMBus: nVidia Corporation: Unknown device 0034 (rev a2)
>         Subsystem: Asustek Computer, Inc.: Unknown device 818a
>         Flags: 66MHz, fast devsel, IRQ 3
>         I/O ports at e400 [size2]
>         I/O ports at 5000 [sized]
>         I/O ports at 5100 [sized]
>         Capabilities: <available only to root>

It doesn't, actually. Device 0x0034 isn't supported by the i2c-nforce2
driver (yet). No wonder it doesn't work.

What kind of nForce chip is it? If it brand new?

You may take your chance and add 0x0034 to the list of IDs in
drivers/i2c/busses/i2c-nforce2.c. If your chip is actually compatible
with the earlier incarnations, it may work. Or it may not work, and
may even do bad things. Unless you have a datasheet, it's impossible
for us to tell. And you're on your own if something bad happens, of
course.

If you try it out, please let us know the outcome.

-- 
Jean Delvare


  reply	other threads:[~2005-12-09 20:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 18:55 [lm-sensors] i2cdetect fails on a Asus P5ND2-Sli Deluxe fred
2005-12-09 20:35 ` Jean Delvare [this message]
2005-12-11 21:03 ` fred
2005-12-12 19:27 ` Jean Delvare
2005-12-13 18:45 ` fred
2005-12-13 19:07 ` fred
2005-12-13 19:27 ` fred
2005-12-13 22:03 ` Jean Delvare
2005-12-13 22:06 ` fred
2005-12-13 22:31 ` fred
2005-12-14 19:03 ` Jean Delvare
2005-12-14 19:16 ` Jean Delvare
2005-12-14 20:04 ` fred

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=20051209213522.4415984b.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.