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: Tue, 28 Sep 2004 17:22:09 +0200 [thread overview]
Message-ID: <20040928152214.CC499C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 28 Sep 2004 08:43:32 EDT." <Pine.LNX.4.60.0409280836340.9825@localhost.localdomain>
In message <Pine.LNX.4.60.0409280836340.9825@localhost.localdomain> you wrote:
>
> but the PDF file doesn't refer explicitly to SMC1, just to the
> generic SMC(UART). does this mean that the same instructions to
It relates to the SMC which parameter RAM location is in conflict
with the SPI/I2C parameter RAM, i. e. SMC1.
> relocate SMC1 could also relocate SMC2 at the same time? the writeup
I think it makes little sense to speculate about this without knowing
anything about how the microcode patch actually works.
> isn't clear on this and, from what i've read, it might be useful to
> relocate SMC2 if one wants to use the reserved memory just before it
> for, say, ethernet on SCC4 (if that's even possible).
No, this is impossible as there is no SCC4 on a MPC823/850.
> so, short question -- i know that patch supports relocating SMC1.
> does it also handle *both* SMC1 and SMC2? or, perhaps, SMC2 all by
> itself? there's nothing in the writeup i can see that clarified this.
It is not even mentioned, so assume it is NOT supported.
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
I think it's a new feature. Don't tell anyone it was an accident. :-)
-- Larry Wall on s/foo/bar/eieio in <10911@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2004-09-28 15:22 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 [this message]
2004-09-28 17:21 ` Robert P. J. Day
2004-09-29 14:22 ` Wolfgang Denk
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=20040928152214.CC499C1430@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).