From: Wolfgang Denk <wd@denx.de>
To: ivica@asist-traffic.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: i2c on mpc5200
Date: Mon, 20 Dec 2004 22:02:21 +0100 [thread overview]
Message-ID: <20041220210226.E0438C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 20 Dec 2004 20:25:39 +0100." <41C72733.9030300@asist-traffic.com>
In message <41C72733.9030300@asist-traffic.com> you wrote:
>
...
> module I would like to have I2C support working in my kernel.
...
> I tried with v various 2.4 kernels but I only had some success with a
> kernel
> form metrowerks which I got from a colleague. This is it's output.
It works fine with the 2.4.x kernel on our CVS server.
> i2c-core.o: i2c core module
> i2c-dev.o: i2c /dev entries driver module
> i2c-core.o: driver i2c-dev dummy driver registered.
> i2c-algo-bit.o: i2c bit algorithm module
> i2c-proc.o version 2.6.1 (20010825)
> devfs_register(ttyS): could not append to parent, err: -17
> devfs_register(ttyS): could not append to parent, err: -17
> devfs_register(cua): could not append to parent, err: -17
> devfs_register(cua): could not append to parent, err: -17
Did you try NOT using devfs?
> Also if anyone has already succeeded in supporting i2c for mpc5200 I
> would love
> to hear your experience.
We did, in 2.4, where it works OK, at least as long as the hardware
is OK (some of the earlier Icecube boards had some issues).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The ultimate barrier is one's viewpoint.
- Terry Pratchett, _The Dark Side of the Sun_
next prev parent reply other threads:[~2004-12-20 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 19:25 i2c on mpc5200 ivica
2004-12-20 21:02 ` Wolfgang Denk [this message]
2004-12-21 10:37 ` ivica
2004-12-25 12:34 ` Sylvain Munaut
2005-01-05 10:29 ` ivica
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=20041220210226.E0438C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=ivica@asist-traffic.com \
--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