linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: kd@flaga.is
Cc: "Shuangjun Zhu (r44089)" <r44089@email.sps.mot.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Help about device driver in Linux
Date: Tue, 28 Dec 1999 11:53:21 -0500	[thread overview]
Message-ID: <3868EB01.236121F4@netx4.com> (raw)
In-Reply-To: OF9209481E.5CD82FF1-ON00256855.00326F88@flaga.is


kd@flaga.is wrote:
> 
> Hi,
> 
> There is an IIC driver now in kernel 2.2.13. I have not tested it yet so I
> can't comment on how well it works.


I put it there as a way to test some of the CPM microcode patches.
It is one of the devices that is relocated, and I was testing on
an Embedded Planet board which has an I2C serial EEPROM.

It works, and is basically the same code that exists in the 
mbxboot directory to read I2C EEPROMs when booting.  There isn't
a write function, but since the read includes a write operation
it shouldn't be too difficult to create one.  It isn't semantically
correct, there is no EOF on read condition (but I am not sure how
to make this happen given the I2C protocol).  The minor device ID
is used for the I2C device address.

The I2C on the 8xx is troublesome, especially because of all of
the silicon errata in early parts.  Later silicon seems to work
fine.

I have only used I2C in master mode.



	-- Dan

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

       reply	other threads:[~1999-12-28 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF9209481E.5CD82FF1-ON00256855.00326F88@flaga.is>
1999-12-28 16:53 ` Dan Malek [this message]
1999-12-28  2:56 Help about device driver in Linux Shuangjun Zhu
1999-12-28 17:35 ` Dan Malek

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=3868EB01.236121F4@netx4.com \
    --to=dan@netx4.com \
    --cc=kd@flaga.is \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=r44089@email.sps.mot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).