From: Milton Miller <miltonm@bga.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform
Date: Mon, 30 Apr 2007 23:10:08 -0500 [thread overview]
Message-ID: <d47bc8a8db1e8b703595cd7dca25b33a@bga.com> (raw)
In-Reply-To: <20070430181954.GB7673@mag.az.mvista.com>
On Apr 30, 2007, at 1:19 PM, Mark A. Greer wrote:
> On Mon, Apr 30, 2007 at 11:15:23AM -0500, Milton Miller wrote:
>> 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.
>>> + 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.
> How about "host-bridge" or is that too generic?
That would be ok but that could be precompiled, vs set in code.
I was thinking you wanted to expose the vpd determined specific
bridge to the kernel / user.
>>> +/* 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\
>>> +");
>>>
>
> Yes, its a poorly worded comment.
>
>> Also, the 1<<15 seems magic. I would like to see it as a constant in
>> reg.h,
>
> It probably makes sense to add some MSR definitions to reg.h.
>
>> but to use that you would have to pass it as an i parameter, so
>
> I don't follow. What's wrong with '#define MSR_EE (1<<15)'
> in reg.h and 'rlwinm 10,10,0,~MSR_EE'?
I think you will find that cpp doesn't replace the define inside
the string. And by the time you stop the string, stringify the
define, and restart the string, you might as well pass it as a
parameter. Also, in C we sometimes add things like ULL that
aren't valid in assembler, although that's more of a 64 bit issue.
milton
next prev parent reply other threads:[~2007-05-02 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 16:15 [PATCH 12/13] powerpc: Add bootwrapper support for Motorola PrPMC2800 platform Milton Miller
2007-04-30 18:19 ` Mark A. Greer
2007-05-01 4:10 ` Milton Miller [this message]
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=d47bc8a8db1e8b703595cd7dca25b33a@bga.com \
--to=miltonm@bga.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mgreer@mvista.com \
/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).