From: Sylvain Munaut <tnt@246tNt•com>
To: ivica@asist-traffic•com
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: i2c on mpc5200
Date: Sat, 25 Dec 2004 13:34:40 +0100 [thread overview]
Message-ID: <41CD5E60.10404@246tNt.com> (raw)
In-Reply-To: <41C72733.9030300@asist-traffic.com>
Hi
> I have a hardware clock (RTC) which is not yet supported in
> the linux kernel. It is RX-8025 module from EPSON and it is
> I2C bus-interface based. Before I start writing support for this
> module I would like to have I2C support working in my kernel.
> Has anybody succeeded in getting I2C supported for MPC5200
> based boards with 2.6 kernels? I'm using the one which maintains
> Sylvain Munaut. If I boot up the kernel with I2C support in it
> I don't get any initialization messages for I2C, only this one line:
> ----------------------------------------------------------------------
> eth0: Phy @ 0x0, type LXT971 (0x001378e2)
> mice: PS/2 mouse device common for all mice
> i2c /dev entries driver
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> -----------------------------------------------------------------------
Are you sure it doesn't work ?
On my system there are no I2C init message either, the driver is just
not noisy ... (unless you activate all the I2C debug stuff).
I have the exact same message than you but if I activate the eeprom
support then in
/sys/bus/i2c/devices, the lite5200 eeprom shows up and I can read it ...
Sylvain
next prev parent reply other threads:[~2004-12-25 12:34 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
2004-12-21 10:37 ` ivica
2004-12-25 12:34 ` Sylvain Munaut [this message]
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=41CD5E60.10404@246tNt.com \
--to=tnt@246tnt$(echo .)com \
--cc=ivica@asist-traffic$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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