From: "???" <tachyon@postech.ac.kr>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: [i2c] Do I need ucode relocation patch?
Date: Tue, 5 Dec 2000 02:14:35 +0900 [thread overview]
Message-ID: <016101c05e15$ace61d60$296cabd3@dongdong> (raw)
Hello.
I'm running Montavista hardhat Linux kernel-2.2.14 with my custom board.
Since there is video decoder board which is connected by I2C bus with MPC860SAR on board, I have to adopt i2c device driver of Kim Jorgensen and my first attempt to write a value to i2c bus makes Linux hang.
There are many posting of I2C and SCC1 conflict, so I've searched 860 errata from Motorola web site. But my 860 is not listed anywhere on it.
The version number of MPC860SAR is "XPC860SRZP50D3 , QQFV00261 , 2K20A".
I'm using SCC1 as ethernet and SMC1 as ttyS0.
Do I need ucode relocation patch to work with i2c bus?
Thanks in advance.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-04 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 17:14 ??? [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-04 17:51 [i2c] Do I need ucode relocation patch? Cha Hyun Joon
2000-12-04 19:29 Ian Abbott
2000-12-05 13:30 Tobias Otto-Adamczak
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='016101c05e15$ace61d60$296cabd3@dongdong' \
--to=tachyon@postech.ac.kr \
--cc=linuxppc-embedded@lists.linuxppc.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