From: Wolfgang Denk <wd@denx.de>
To: Bob Beck <beck@assurtech.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Booting Linux on a Custom PPC Board
Date: Wed, 03 Mar 2004 00:51:44 +0100 [thread overview]
Message-ID: <20040302235149.72299C0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "02 Mar 2004 12:58:54 +1400." <1078181934.4198.20.camel@budweiser>
In message <1078181934.4198.20.camel@budweiser> you wrote:
>
> We are writing our own boot loader code for a couple of reasons.
>
> o U-Boot does not support our ethernet chip or serial chip.
And you really think that developing a complete new bootloader
(including drivers for your ethernet and serial chips) is less effort
or easier that just adding these drivers to U-Boot?
C'me on!
> o VxWorks is in flash and we cannot change that in the near future.
> o The VxWorks boot loader initializes the hardware and
> we run our custom boot loader from its shell.
U-Boot can boot VxWorks just fine.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Space is big. You just won't believe how vastly, hugely, mind-
bogglingly big it is. I mean, you may think it's a long way down the
road to the drug store, but that's just peanuts to space.
-- The Hitchhiker's Guide to the Galaxy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-02 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Iq959772845498.03218@webmail1.inner-21cn.com>
2004-02-26 17:24 ` ADS860 - unable to load kernel- Bad magic number Bob Beck
2004-02-27 16:32 ` Marius Groeger
2004-02-26 22:22 ` Bob Beck
2004-02-27 17:29 ` Marius Groeger
2004-02-26 22:38 ` Bob Beck
2004-02-27 19:32 ` Dan Malek
2004-02-27 1:32 ` Bob Beck
2004-02-27 21:05 ` Dan Malek
2004-03-01 22:58 ` Booting Linux on a Custom PPC Board Bob Beck
2004-03-02 23:51 ` Wolfgang Denk [this message]
2004-03-02 17:45 ` Bob Beck
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=20040302235149.72299C0655@atlas.denx.de \
--to=wd@denx.de \
--cc=beck@assurtech.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).