All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: hellohello <hellohello008@163.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Problem of PowerPc 82xx  when using smc
Date: Fri, 21 May 2010 12:28:18 -0500	[thread overview]
Message-ID: <4BF6C2B2.6030705@freescale.com> (raw)
In-Reply-To: <051501caf896$5c954630$a51cbcc0@sfdomain.com>

On 05/20/2010 10:33 PM, hellohello wrote:
>> No, it shouldn't -- rx_bd_base is of type "cbd_t *", so the multiplication
>> already happens as part of pointer arithmetic.
> ---Yes, you are right. I made a basic mistake.
>
> But now I have another question.
> The SMC1 params can be relocated to any offset of the DPRAM on a 64 byte boundary, not as the SCC1, which must be  at 0x8000 offset of the DPRAM.
> The SMC1 params base is set at 0x87FC offset of the DPRAM.
>
> So if  I want SMC1 params start at  0x200 in DPRAM  , I should set 0x200 to the 0x87FC offset of the DPRAM.
> I have see this code in u-boot, but I can not find this code in neither cpm_uart_cpm2.c nor cpm_uart_core.c.
>
> Should I add these code to  cpm_uart_core.c?

Newer kernels support dynamically allocating this parameter RAM.  Older 
kernels use whatever u-boot chose.

Why do you want to set it to a particular address?

-Scott

  parent reply	other threads:[~2010-05-21 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  8:58 Problem of PowerPc 82xx when using smc hellohello
2010-05-20 17:06 ` Scott Wood
2010-05-21  3:33   ` hellohello
2010-05-21 11:20     ` Gary Thomas
2010-05-22  3:37       ` hellohello
2010-05-21 17:28     ` Scott Wood [this message]
2010-05-22  2:51       ` hellohello
  -- strict thread matches above, loose matches on Subject: below --
2010-05-22  6:23 hellohello

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=4BF6C2B2.6030705@freescale.com \
    --to=scottwood@freescale.com \
    --cc=hellohello008@163.com \
    --cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.