All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeff@jdfiles.org (Jeff Sacksteder)
To: lm-sensors@vger.kernel.org
Subject: i2c for Alpha
Date: Thu, 19 May 2005 06:24:21 +0000	[thread overview]
Message-ID: <200310131613.49854.jeff@jdfiles.org> (raw)
In-Reply-To: <200310121707.56799.jeff@jdfiles.org>

> Most (all?) of the code is CPU independant.  You'll need to figure out
> what the I2C/SMBus host is and see if it is supported

I suppose I should start by asking has anyone has built it successfully on any 
64-bit platform- Alpha, Itanium or AMD?

My operating assumption is that I will use the i2c package to patch my kernel, 
replacing the existing i2c code with the current rev. I can then build the 
sensors package to create the user programs to manipulate the hardware.

This mainboard has an Intel chipset of some sort on it- possibly PIIX4. It 
says PCIset on it, not AGPset. Not sure what chipset that is. Actually has 
USB in the chip, though there are no physical bus connections to add devices.
Does the I2C controller live in there(Intel chipset)?

   


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 i2c for Alpha Jeff Sacksteder
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jeff Sacksteder [this message]
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Mark Studebaker
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Mark Studebaker
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Morris, John
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jean Delvare

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=200310131613.49854.jeff@jdfiles.org \
    --to=jeff@jdfiles.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.