linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: jfaslist <jfaslist@yahoo.fr>
To: linuxppc-embedded@ozlabs.org
Subject: mpc8270 : i2c support
Date: Wed, 03 May 2006 14:33:37 +0200	[thread overview]
Message-ID: <4458A321.1030206@yahoo.fr> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii; format=flowed, Size: 1153 bytes --]

Hi,
We have designed a system using a mpc8270 cpu. The firmware we 
use is u-boot and we can access all our i2c devices from u-boot.

But when we try to access i2c devices from under linux 2.6 using 
the /dev/i2c-0 special file we get an ENODEV on opening that 
file. I think it is because we lack an adapter driver.

If I look in the official kernel, it looks like the adapter 
driver for the mpc8270 i2c system is 
./drivers/i2c/busses/i2c-mpc.c. Is this correct?

Why is this driver registering as a platform driver and not as a 
i2c bus driver?

In DENX ELDK there is also a i2c-mpc8260.c, but we couldn't get 
that to work either.

What should I do to be able to access i2c devices using the 
/dev/i2c-0 file? I feel I need to modify the i2c adapter driver 
to follow the driver model, but in what ways?

Thx for any help,
-jf simon

	

	
		
___________________________________________________________________________ 
Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. 
Rendez-vous sur http://fr.yahoo.com/set

             reply	other threads:[~2006-05-03 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 12:33 jfaslist [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03 20:11 mpc8270 : i2c support Heiko Schocher
     [not found] <20060503205654.39188.qmail@web26605.mail.ukl.yahoo.com>
2006-05-04  4:34 ` Heiko Schocher
2006-05-11  5:12 Heiko Schocher

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=4458A321.1030206@yahoo.fr \
    --to=jfaslist@yahoo.fr \
    --cc=linuxppc-embedded@ozlabs.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 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).