From: Scott Wood <scottwood@freescale•com>
To: Shawn Jin <shawnxjin@gmail•com>
Cc: ppcdev <linuxppc-dev@ozlabs•org>
Subject: Re: mpc870 support in the powerpc arch?
Date: Fri, 25 Jun 2010 14:39:55 -0500 [thread overview]
Message-ID: <4C25060B.2040903@freescale.com> (raw)
In-Reply-To: <AANLkTinTSyGBRuWrjEzl9gAzLMt-qNZkwpjhxsqr5_5f@mail.gmail.com>
On 06/25/2010 04:08 AM, Shawn Jin wrote:
> On Mon, May 17, 2010 at 12:54 PM, Scott Wood<scottwood@freescale•com> wrote:
>> On Fri, May 14, 2010 at 02:41:29PM -0700, Shawn Jin wrote:
>>> Hi,
>>>
>>> Is mpc870 fully supported in the powerpc arch? I know it's an old
>>> processor but 8xx is still one of platforms in the powerpc arch. If
>>> it's not supported, how much effort will it be to resurrect mpc870 in
>>> the new arch considering we have substantial 8xx support?
>>
>> It should work, with appropriate board support -- MPC875 and MPC885 have
>> been used with arch/powerpc, and MPC870 is very similar (albeit with fewer
>> devices).
>
> Thanks Scott. I found your implementation in the kernel. I use
> adder875 as my base to port my board support. But I'm having a problem
> in the last step to create the cuImage. You may know what I did wrong.
> The error message is as follows.
>
> WRAP arch/powerpc/boot/cuImage.my870
> ppc_8xx-ld: arch/powerpc/boot/cuboot-my870.o: No such file: No such
> file or directory
> make[1]: *** [arch/powerpc/boot/cuImage.my870] Error 1
You need to update the case statement arch/powerpc/boot/wrapper to
recognize your board and select cuboot-8xx.o, as is done for adder875.
Otherwise it defaults to looking for a file for your specific board.
-Scott
prev parent reply other threads:[~2010-06-25 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 21:41 mpc870 support in the powerpc arch? Shawn Jin
2010-05-17 19:54 ` Scott Wood
2010-06-25 9:08 ` Shawn Jin
2010-06-25 19:39 ` Scott Wood [this message]
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=4C25060B.2040903@freescale.com \
--to=scottwood@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=shawnxjin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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