From: Kimmo Surakka <kimmo.surakka@oxinst.fi>
To: linuxppc-embedded@ozlabs.org
Subject: MPC5200 I2C unstable?
Date: Wed, 3 May 2006 16:08:47 +0300 [thread overview]
Message-ID: <200605031608.47579.kimmo.surakka@oxinst.fi> (raw)
Hi,
I'm using a MPC5200 based board (namely TQM5200) and the
linuxppc_2_4_devel-2005-10-25-1440 kernel from denx.de. To get the serial
ports more stable, I've applied the serial port patch by Achim Machura (can
be found in
http://marc.theaimsgroup.com/?l=linuxppc-embedded&m=112901824515097&w=2). The
patch needed small adjustments, but nothing too large -- mostly different
line numbers.
Also, to get the first I2C interface to work, I've had to change the file
drivers/i2c/i2c-tqm5200.c followingly:
-#define MPC5xxx_I2C1_ENABLE 0 /* Disable */
+#define MPC5xxx_I2C1_ENABLE 1 /* Enable */
The code compiles OK, but the I2C bus gets stuck after a short while. Has
anyone else experienced something similar? I tried to Google for information
but didn't find anything relevant. Maybe I just didn't know the right
keywords to search for?
Thanks in advance,
Kimmo Surakka
This message has been scanned by F-Secure Anti-Virus
### OXFORD INSTRUMENTS http://www.oxford-instruments.com/ ###
Unless stated above to be non-confidential, this E-mail and any
attachments are private and confidential and are for the addressee
only and may not be used, copied or disclosed save to the addressee.
If you have received this E-mail in error please notify us upon receipt
and delete it from your records. Internet communications are not secure
and Oxford Instruments is not responsible for their abuse by third
parties nor for any alteration or corruption in transmission.
next reply other threads:[~2006-05-03 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 13:08 Kimmo Surakka [this message]
2006-05-03 14:15 ` MPC5200 I2C unstable? Arno Geissel
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=200605031608.47579.kimmo.surakka@oxinst.fi \
--to=kimmo.surakka@oxinst.fi \
--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