linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Fabio Tosetto" <tosettofabio83@libero.it>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC5200b MMC over SPI into PSC6
Date: Wed, 7 May 2008 10:34:37 -0600	[thread overview]
Message-ID: <fa686aa40805070934t77f8b2b0y2799814b4f131bc8@mail.gmail.com> (raw)
In-Reply-To: <4821A551.3060205@libero.it>

On Wed, May 7, 2008 at 6:49 AM, Fabio Tosetto <tosettofabio83@libero.it> wrote:
>
>  I've tried to port my exesting configurations to the powerpc tree but some
> configurations files are missing.

First, create a new .dts file for your board in arch/powerpc/boot/dts.
(just copy the lite5200.dts file).  Modify the .dts to have your
board's name (in the form "<vendor>,<boardname>") in the compatible
and model properties.

Next, add your boards name to the list of boards in
arch/powerpc/platforms/52xx/mpc5200_simple.c.

>  I need to set PSC3 - PSC4 in uart mode:
>  before in file *arch/ppc/platforms/lite5200.c* I added
>
>  struct mpc52xx_psc_func mpc52xx_psc_functions[] = {
>          {       .id     = 3,
>                  .func   = "uart",
>          },
>          {       .id     = 4,
>                  .func   = "uart",
>          },
>          {       .id     = -1,   /* End entry */
>                  .func   = NULL,
>          }
>  };

Edit your boards .dts file and uncomment PSCs 3 and 4.  Comment out
PSC1 if you aren't using it.

>  I need to set PSC4 as a low level debug: *
>  *before in file  *arch/ppc/platforms/lite5200.h *I added
>
>  #define MPC52xx_PF_CONSOLE_PORT 4    /* PSC4 */

I don't think we have any early debug enabled yet in arch/powerpc for
the mpc5200.

>  Finally I need to set  the virtual memory translation on a range of 128 MB:
>  before in file *arch/ppc/kernel/head.S *I added
>
>  /*ori    r11,r11,BL_128M<<2|0x2    set up BAT registers for 604 */
>
>  ori    r11,r11,BL_128M<<2|0x2    /* set up BAT registers for 604 */
>
>  could you please explain me how to do the same operations in powerpc tree??

New file is arch/powerpc/kernel/head_32.S.  I don't think that is the
cleanest way to do it though.  Why do you need to change the BAT
mapping from 256 to 128?

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-05-07 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 18:12 MPC5200b MMC over SPI into PSC6 Fabio Tosetto
2008-05-06 15:36 ` Grant Likely
2008-05-07 12:49   ` Fabio Tosetto
2008-05-07 16:34     ` Grant Likely [this message]
2008-05-08 15:10       ` Fabio Tosetto
2008-05-08 15:32         ` Grant Likely
2008-05-09 13:40           ` Fabri
2008-05-09 13:51             ` Fabri
2008-05-09 14:06               ` Grant Likely
2008-05-09 15:02                 ` Fabri
2008-05-09 15:20                   ` Grant Likely
2008-05-09 20:01                     ` Fabri
2008-05-12  8:51                     ` Fabio Tosetto
2008-05-22 14:28                     ` Fabri
  -- strict thread matches above, loose matches on Subject: below --
2008-04-16 11:26 MPC5200B " tosettofabio83

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=fa686aa40805070934t77f8b2b0y2799814b4f131bc8@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tosettofabio83@libero.it \
    /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).