From: phil@edgedesign.us (Philip Edelbrock)
To: lm-sensors@vger.kernel.org
Subject: i2c for Alpha
Date: Thu, 19 May 2005 06:24:21 +0000 [thread overview]
Message-ID: <3F8ADBC8.3030807@edgedesign.us> (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
(http://secure.netroedge.com/~lm78/supported.html). If not, then you
could try to get a datasheet and try to hack up a new driver. The nice
thing is that once you have a working bus, all the chip drivers should
automaticly work on it.
Phil
Jeff Sacksteder wrote:
>I am now the proud parent of a Digital Server 5000, based on a 533Mhz Alpha.
>This is the 'Rawhide' platform and was designed for NT on Alpha
>installations. It most certainly has an I2C bus of some sort on it. I have a
>functioning Linux install on it now and would like to experiment with
>hardware monitoring. I will most likely need some coaching as I work my way
>through the problems I encounter. Is there a list where I should direct my
>questions? Alternately, does anyone want to volunteer to work with me on
>this?
>
>
>
next prev 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
2005-05-19 6:24 ` Philip Edelbrock
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Philip Edelbrock [this message]
2005-05-19 6:24 ` Jean Delvare
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 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` jeff
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 ` Jean Delvare
2005-05-19 6:24 ` jeff
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=3F8ADBC8.3030807@edgedesign.us \
--to=phil@edgedesign.us \
--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.