From: Tom Armistead <Tom_Armistead@phx•mcd.mot.com>
To: Tom Rini <trini@kernel•crashing.org>
Cc: ???? <yuj@mail•ndsc.com.cn>, linuxppc-embedded@lists•linuxppc.org
Subject: Re: motorola lopec mpc7410
Date: Thu, 14 Nov 2002 10:02:13 -0700 [thread overview]
Message-ID: <3DD3D715.8BA00B56@phx.mcd.mot.com> (raw)
In-Reply-To: 20021114151038.GA14431@opus.bloom.county
> On Thu, Nov 14, 2002 at 04:50:34PM +0800, ???? wrote:
>
> > I'm porting mvista linux 2.1 for the motorola lopec mpc7410 board.And I noticed that there are some differences between the board version described by mvista and motorola.Also,the version of PPCBug is different.I'm wondering why?
>
> For support for an MontaVista product, please contact your mvista sales
> rep (or perhaps your manager knows) to find out how to contact support.
>
> Having said that, I _believe_ the LoPEC I have running right now has
> PPC6Bug, so perhaps you should contact Motorola to find out how to
> upgrade the firmware.
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
>
PPC5Bug is the firmware for Lopec. The last released version for Lopec is PPC5Bug 1.4 RM02 but it is unlikely that upgrading the firmware (from 1.3) would have any effect on the described problem. I don't know much about Linux but my
guess is that something is misconfigured in your kernel (console IO would be the first thing I'd check...).
The PPC6Bug series was for the Hawk based products (MCPN765, MVME5100, PPMC750, etc..). I don't think any version of PPC6Bug will work at all on Lopec.
Tom Armistead
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-14 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 8:50 motorola lopec mpc7410 于婧
2002-11-14 15:10 ` Tom Rini
2002-11-14 17:02 ` Tom Armistead [this message]
2002-11-14 17:35 ` Tom Rini
2002-11-14 20:29 ` Tom Armistead
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 1:01 于婧
2002-11-18 15:01 ` Matt Porter
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=3DD3D715.8BA00B56@phx.mcd.mot.com \
--to=tom_armistead@phx$(echo .)mcd.mot.com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=trini@kernel$(echo .)crashing.org \
--cc=yuj@mail$(echo .)ndsc.com.cn \
/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