All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: Via KT600 as I2C controller
Date: Thu, 19 May 2005 06:24:27 +0000	[thread overview]
Message-ID: <3FC8CF57.D171594D@paradyne.com> (raw)
In-Reply-To: <20031126235249.GA7632@gumby>

thanks. would you please download the latest lm_sensors CVS
and compile the userspace tools with 2.6 support
(make user and make user_install)
and use i2cdetect and i2cdump to test the driver.
use all modes of i2cdump that work (b,w,c,s)
On a DIMM eeprom, for example, all modes should return the
same data.


Jean Delvare wrote:
> 
> > I have an A7V600 motherboard, which has a Via 8237 on it.
> > It is not supported by current 2.6 kernels (test8, for example).
> > I have added support by adding the following lines to vt596_ids[] in
> > /usr/src/linux-2.6.0-test8/drivers/i2c/busses/i2c-viapro.c.
> >
> >     {
> >         .vendor     = PCI_VENDOR_ID_VIA,
> >         .device     = PCI_DEVICE_ID_VIA_8237,
> >         .subvendor  = PCI_ANY_ID,
> >         .subdevice  = PCI_ANY_ID,
> >         .driver_data    = SMBBA3
> >     },
> >
> > I have not observed any brokenness, having used it for several weeks.
> > I could, of course, continue making the change to future kernel
> > versions, but this would surely benefit others if in the regular dist.
> 
> I've added support in our CVS repository. I will also send a patch to
> Greg KH for Linux 2.6. Don't expect it to be added before 2.6.0 final
> though, since only bug fixes will be accepted for now.
> 
> --
> Jean Delvare
> http://www.ensicaen.ismra.fr/~delvare/

  parent reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 Via KT600 as I2C controller Lou
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Mark Studebaker [this message]
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Mark Studebaker

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=3FC8CF57.D171594D@paradyne.com \
    --to=mds@paradyne.com \
    --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.