From: Wolfgang Denk <wd@denx.de>
To: "enorm" <enorm@126.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problem about porting u-boot 1.1.4 to MPC8560
Date: Mon, 04 Sep 2006 14:48:47 +0200 [thread overview]
Message-ID: <20060904124847.9AED33525AB@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 04 Sep 2006 19:08:39 +0800." <003f01c6d012$79fa8dd0$a309a8c0@cdf28e684a26482>
In message <003f01c6d012$79fa8dd0$a309a8c0@cdf28e684a26482> you wrote:
>
> After prog u-boot image to 8560. We get output as follows:
You are off topic here. Also, it is very impolite to post the same
question on several mailing lists. Your questions have already been
answered on u-boot-users.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Mr. Cole's Axiom:
The sum of the intelligence on the planet is a constant;
the population is growing.
prev parent reply other threads:[~2006-09-04 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:08 Problem about porting u-boot 1.1.4 to MPC8560 enorm
2006-09-04 12:48 ` Wolfgang Denk [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=20060904124847.9AED33525AB@atlas.denx.de \
--to=wd@denx.de \
--cc=enorm@126.com \
--cc=linuxppc-embedded@ozlabs.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