All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian@humboldt.co.uk (Adrian Cox)
To: linuxppc-embedded@lists.linuxppc.org
Cc: sensors@stimpy.netroedge.com
Subject: MPC107 I2C driver
Date: Thu, 19 May 2005 06:23:47 +0000	[thread overview]
Message-ID: <1044359381.19358.44.camel@newt> (raw)

The first version of my driver for the I2C unit in Motorola's MPC107
bridge chip, plus the 824x integrated processors, is released:

http://www.humboldt.co.uk/mpc10xi2c.html

I'd like to know if it works for other people. I've so far tested it
with a pair of LM75 sensors attached to an MPC107 bridge.

I've used an obvious dummy ID number for the I2C interface: I'd like to
get a real one and move the code into the kernel once I have more
results.

- Adrian Cox
http://www.humboldt.co.uk/


WARNING: multiple messages have this Message-ID (diff)
From: Adrian Cox <adrian@humboldt.co.uk>
To: linuxppc-embedded@lists.linuxppc.org
Cc: sensors@stimpy.netroedge.com
Subject: MPC107 I2C driver
Date: 04 Feb 2003 11:49:26 +0000	[thread overview]
Message-ID: <1044359381.19358.44.camel@newt> (raw)


The first version of my driver for the I2C unit in Motorola's MPC107
bridge chip, plus the 824x integrated processors, is released:

http://www.humboldt.co.uk/mpc10xi2c.html

I'd like to know if it works for other people. I've so far tested it
with a pair of LM75 sensors attached to an MPC107 bridge.

I've used an obvious dummy ID number for the I2C interface: I'd like to
get a real one and move the code into the kernel once I have more
results.

- Adrian Cox
http://www.humboldt.co.uk/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 11:49 Adrian Cox [this message]
2005-05-19  6:23 ` MPC107 I2C driver Adrian Cox
2005-05-19  6:23 ` 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=1044359381.19358.44.camel@newt \
    --to=adrian@humboldt.co.uk \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sensors@stimpy.netroedge.com \
    /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.