I2C/SPI/SMC relocation patch works for both SMC 1 and 2?

I2C/SPI/SMC relocation patch works for both SMC 1 and 2?

[Robert P. J. Day]

   i'm reading the microcode patch PDF doc file describing the 
relocation of I2C/SPI/SMC for the 850.  as i've mentioned, in my case, 
i've relocated *specifically* SMC1 so i can use SCC3 for ethernet and 
it seems to work just fine.

   but the PDF file doesn't refer explicitly to SMC1, just to the 
generic SMC(UART).  does this mean that the same instructions to 
relocate SMC1 could also relocate SMC2 at the same time?  the writeup 
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).

   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.

rday

Re: I2C/SPI/SMC relocation patch works for both SMC 1 and 2?

[Wolfgang Denk]

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>

Re: I2C/SPI/SMC relocation patch works for both SMC 1 and 2?

[Robert P. J. Day]

On Tue, 28 Sep 2004, Wolfgang Denk wrote:

> 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.

huh?  what does SMC1 relocation have to do with either of I2C or SPI? 
i'm looking at the PRAM memory map right now, and whether or not you 
choose to relocate SMC1 seems independent from whether you choose to 
relocate both (or either) of I2C or SPI.

i don't see how SMC1 can be "in conflict with the SPI/I2C parameter 
RAM" as you claim.  can you explain that?

rday

Re: I2C/SPI/SMC relocation patch works for both SMC 1 and 2?

[Wolfgang Denk]

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.