From: Ian Abbott <abbotti@mev.co.uk>
To: linuxppc-embedded@lists.linuxppc.org
Subject: RE: [i2c] Do I need ucode relocation patch?
Date: Mon, 4 Dec 2000 19:29:44 -0000 [thread overview]
Message-ID: <00933BFA237CD2119B3400409543582704A290@MEV01> (raw)
Hi,
On Monday, December 04, 2000 5:15 PM you wrote:
> I'm using SCC1 as ethernet and SMC1 as ttyS0.
>
> Do I need ucode relocation patch to work with i2c bus?
Yes. This is because the size of the parameter area for SCC1 ethernet is
bigger than the area allocated it, so they overlap the usual I2C
parameter area. (There is a similar conflict between SCC2 ethernet and
SPI.) The relocation patch moves the I2C and SPI parameters to a new
parameter area.
Be aware that the CPM I2C commands for initializing RX and TX buffer
parameters, etc. do not work when using the relocation patch.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-04 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 19:29 Ian Abbott [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-05 13:30 [i2c] Do I need ucode relocation patch? Tobias Otto-Adamczak
2000-12-04 17:51 Cha Hyun Joon
2000-12-04 17:14 ???
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=00933BFA237CD2119B3400409543582704A290@MEV01 \
--to=abbotti@mev.co.uk \
--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