From: Scott Wood <scottwood@freescale.com>
To: Boris Shteinbock <bshtein@yahoo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: powerpc port for sbc8260-based board problem
Date: Wed, 07 May 2008 13:53:37 -0500 [thread overview]
Message-ID: <4821FAB1.1070200@freescale.com> (raw)
In-Reply-To: <833555.65590.qm@web50611.mail.re2.yahoo.com>
Boris Shteinbock wrote:
>> The second reg resource depends on where your firmware set up the SMC pram
>> regs. With U-boot, it's usually zero.
>
>> Note that as of 2.6.26-rc1, this is set up dynamically instead, and the
>> second resource should be .
> Is this correct?
>
> reg = <0x11a80 0x20 0x87fc 2>;
Yes.
> I also understand, that latest development kernel contains some significant changes in SMC UART code, especially
> in muram code, is this correct? So does this reg value reflect this change?
Yes, those are the changes I was referring to.
>>> Can someone, also, explain, how "fsl, cpm-command" field works,
>
>> It's the device-specific portion of the value that gets written to the CPM
>> command register (page, sub-block, and mcc channel).
>
> Is it possible to get a quick list of all values for all 8260 soc devices somewhere ? Or do I have to dig specific Freescale reference for it?
See table 13-6 (CP Command Register Field Descriptions) in the 8260 manual.
> I am particularly interested in SMC2 and FCC1,2 and 3 ?
SMC2: 0x21200000
FCC1: 0x12000000 (ATM 0x11c00280)
FCC2: 0x16200000 (ATM 0x15c00280)
FCC3: 0x1a400000
For FCCs, add 0x300 for Ethernet, 0x3c0 for transparent.
-Scott
next prev parent reply other threads:[~2008-05-07 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:42 powerpc port for sbc8260-based board problem Boris Shteinbock
2008-05-07 18:53 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 8:31 Boris Shteinbock
2008-05-07 17:38 ` Sergej Stepanov
2008-05-07 18:22 ` Scott Wood
2008-05-07 18:40 ` Sergej Stepanov
2008-05-07 18:57 ` Scott Wood
2008-05-07 19:26 ` Sergej Stepanov
2008-05-07 19:34 ` Scott Wood
2008-05-07 19:40 ` Sergej Stepanov
2008-05-07 19:42 ` Scott Wood
2008-05-07 19:44 ` Scott Wood
2008-05-08 6:22 ` Sergej Stepanov
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=4821FAB1.1070200@freescale.com \
--to=scottwood@freescale.com \
--cc=bshtein@yahoo.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).