From: Wolfgang Denk <wd@denx.de>
To: "Thamarai Selvan" <Thamarai.Selvan@lntinfotech.com>
Cc: "RamanaYV" <venkataramana_y@mic.co.in>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPCBOOT in customised MPC860T board
Date: Fri, 20 Feb 2004 10:01:52 +0100 [thread overview]
Message-ID: <20040220090157.76C89C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 20 Feb 2004 10:23:47 +0530." <OF6966D76E.A0BB8139-ON65256E40.001AB153@lntinfotech.com>
In message <OF6966D76E.A0BB8139-ON65256E40.001AB153@lntinfotech.com> you wrote:
>
> check out the following link
> http://www.uclinux.org/~bkuhn/Platforms/Coldfire/tarifa/20020526/README
> if ur still interested with ppcboot this will give u a good idea ;-)-
This is very, very misleading information.
First, the link points to a very old document. Many things have
changed in the last 2 years.
Second, the ColdFire is still one of the "new" processors which are
supported by U-Boot, and obviously it was much worse two years ago.
On the other hand, the MPC860 was the very first processor ever
supported by U-Boot and it's predecessor PPCBoot.
If you're looking for up-to-date information about U-Boot you should
rather read the manual at
http://www.denx.de/twiki/bin/view/DULG/Manual
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
grep me no patterns and I'll tell you no lines.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-20 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 4:53 PPCBOOT in customised MPC860T board Thamarai Selvan
2004-02-20 9:01 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 4:11 RamanaYV
2004-02-19 19:09 ` Dennis Khoo
2004-02-19 19:48 ` Wolfgang Denk
2004-02-19 19:43 ` Wolfgang Denk
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=20040220090157.76C89C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=Thamarai.Selvan@lntinfotech.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=venkataramana_y@mic.co.in \
/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).