From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: I2C/SPI/SMC relocation patch works for both SMC 1 and 2?
Date: Wed, 29 Sep 2004 16:22:35 +0200 [thread overview]
Message-ID: <20040929142240.AC2C5C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 28 Sep 2004 13:21:16 EDT." <Pine.LNX.4.60.0409281317590.11302@localhost.localdomain>
In message <Pine.LNX.4.60.0409281317590.11302@localhost.localdomain> you wrote:
>
> > It relates to the SMC which parameter RAM location is in conflict
> > with the SPI/I2C parameter RAM, i. e. SMC1.
>
> huh? what does SMC1 relocation have to do with either of I2C or SPI?
Ooops. You are right. Please s/SPI\/I2C/SCC2 ethernet/ ! Before I
tell more such nonsense let's quote the description that comes
included with the patch: "model allows concurrent operation of
Ethernet and SMC(UART) and I2C/SPI by solving the parameter RAM
conflict caused by the fact that some of the Ethernet parameters
overlay the SMC(UART) and I2C/SPI parameters."
> i don't see how SMC1 can be "in conflict with the SPI/I2C parameter
> RAM" as you claim. can you explain that?
If you use SCC2 for ethernet, it's parameter RAM will use the DPRAM
from offset 3E00 to offset 3EA4; without relocation the SMC1
parameter RAM uses offsets 3E80 to 3EB4, thus you have a conflict for
the 3E80...3EA4 area.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The IQ of the group is the lowest IQ of a member of the group divided
by the number of people in the group.
prev parent reply other threads:[~2004-09-29 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:43 I2C/SPI/SMC relocation patch works for both SMC 1 and 2? Robert P. J. Day
2004-09-28 15:22 ` Wolfgang Denk
2004-09-28 17:21 ` Robert P. J. Day
2004-09-29 14:22 ` Wolfgang Denk [this message]
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=20040929142240.AC2C5C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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;
as well as URLs for NNTP newsgroup(s).