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] [CALL FOR TESTERS] i2c-nforce2 support for MCP04
Date: Sun, 24 Jul 2005 16:46:06 +0000	[thread overview]
Message-ID: <20050724164602.1bcb9103.khali@linux-fr.org> (raw)
In-Reply-To: <42E24D97.3080104@gmx.net>

Hi Hans,

> is there anybody on the list who has an nForce4 SLI intel edition or a
> prototype of the mainboard with the upcoming nVidia CK8-04u/MCP51
> chipset?

I do not, sorry.

> Can you please apply the attached patch and check whether
> i2c-nforce2 finds the 2 SMBusses. The output of i2cdetect would be
> appreciated as an indication that the module not only finds the
> busses, but also has the minimum functionality. The patch is against
> 2.6.13-rc3-mm1 with the cleanup patch included that I have sent to the
> list today. It also applies to vanilla 2.6.13-rc3-mm1, but with some
> offset.

But I'd have a comment about the patch:

> +/* temporarily needed! */
> +#ifndef PCI_DEVICE_ID_NVIDIA_NFORCE_MCP04_SMBUS
> +#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP04_SMBUS 0x0034
> +#endif
> +#ifndef PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SMBUS
> +#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SMBUS 0x0264
> +#endif

Such constructs are dangerous and should be avoided. These definitions
belong to include/linux/pci_ids.h, please add them there.

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2005-07-24 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23 16:01 [lm-sensors] [CALL FOR TESTERS] i2c-nforce2 support for MCP04 and Hans-Frieder Vogt
2005-07-24 16:46 ` Jean Delvare [this message]
2005-08-08  0:13 ` Hans-Frieder Vogt

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=20050724164602.1bcb9103.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.