linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: Mark A. Greer <mgreer@mvista.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform
Date: Mon, 30 Apr 2007 11:15:23 -0500	[thread overview]
Message-ID: <35d250938c0c5d7dae6a8735343059b7@bga.com> (raw)

On Thu Apr 26 10:02:27 EST 2007, Mark A. Greer wrote:
> Add support for Motorola ECC PrPMC280/PrPMC2800 Platform.
> The PrPMC280 sits on an F101 baseboard and the PrPMC2800 sits on a
> F101e baseboard.  Logic has been added to determine which board
> (and variant thereof) the code is being run on.

>
> +       /* Update /mv64x60/device_type, if this is a mv64362 */
> +       if (bip->bridge_type == BRIDGE_TYPE_MV64362) {
> +               devp = finddevice("/mv64x60");
> +               if (devp == NULL)
> +                       fatal("Error: Missing /mv64x60 device tree 
> node\n\r");
> +               setprop(devp, "device_type", "mv64362", 
> strlen("mv64362") + 1);
> +       }
> +

That is not a device_type.   It might be a model,   Or even a 
compatable.
but not a type.

> +       platform_ops.exit = prpmc2800_reset;

No delay to let the user know see what is wrong?

> +
> +/* Following code is put at very beginning of zImage (64KB into ELF 
> file) */
> +asm (" .globl _zimage_start\n\
> +       _zimage_start:\n\
> +               mfmsr   10\n\
> +               rlwinm  10,10,0,~(1<<15)        /* Clear MSR_EE */\n\
> +               sync\n\
> +               mtmsr   10\n\
> +               isync\n\
> +               b _zimage_start_lib\n\
> +");
>

That comment is very wrong.   This object might be the first to be 
linked,
and the text will be near the top.  But there is nothing in that 
fragment
to make it be the beginning of the image.  Not even in the text section.

That label will be the entrypoiint, so make the comment to that effect.

Also, the 1<<15 seems magic.  I would like to see it as a constant in
reg.h, but to use that you would have to pass it as an i parameter, so
I'm not sure it would improve.

milton

             reply	other threads:[~2007-04-30 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 16:15 Milton Miller [this message]
2007-04-30 18:19 ` [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Mark A. Greer
2007-05-01  4:10   ` Milton Miller
2007-05-07 18:23     ` Mark A. Greer
2007-05-01 17:06   ` Milton Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-05-12  0:46 [PATCH 0/13] powerpc: Add support for Marvell/mv64x60 and prpmc2800 Mark A. Greer
2007-05-12  0:58 ` [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Mark A. Greer
2007-05-10 20:02 [PATCH 0/13] powerpc: Add support for Marvell/mv64x60 and prpmc2800 Mark A. Greer
2007-05-10 20:09 ` [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Mark A. Greer
2007-04-25 23:46 [PATCH 0/13] powerpc: Add support for Marvell/mv64x60 and prpmc2800 Mark A. Greer
2007-04-26  0:02 ` [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Mark A. Greer

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=35d250938c0c5d7dae6a8735343059b7@bga.com \
    --to=miltonm@bga.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.com \
    --cc=paulus@samba.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).