From: Dan Malek <dmalek@jlc.net>
To: LiuTao <tliu@ict.ac.cn>
Cc: linuxppc <linuxppc-dev@lists.linuxppc.org>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: need suggestions
Date: Mon, 22 Nov 1999 22:46:53 -0500 [thread overview]
Message-ID: <383A0E2D.CFACF894@jlc.net> (raw)
In-Reply-To: 3839F122.3BF6FEDF@ict.ac.cn
LiuTao wrote:
> ........ The board
> is running well with vxWorks now.
> I want to make a bootloader on the board.
How do you load vxWorks? I have worked on several vxWorks projects,
and all of the systems had the vxWorks TFTP loader in the rom. Use
the same thing (whatever that is) to load the Linux/PPC image.
The zImage is linked such that you can just treat it as a bag o' bits
to dump into memory. Even with non-standard boot loaders, all you
need to do is write a simple program to strip the 64K ELF header, place
your own header on the top, make sure it gets loaded above 0x180000
and jump to the start of the image.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-23 3:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 1:42 need suggestions LiuTao
1999-11-23 3:46 ` Dan Malek [this message]
1999-11-23 3:46 ` LiuTao
1999-11-23 6:14 ` Dan Malek
1999-11-23 18:47 ` Geert Uytterhoeven
1999-11-24 8:34 ` LiuTao
1999-11-24 10:26 ` Magnus Damm
1999-11-24 8:56 ` Neil Russell
-- strict thread matches above, loose matches on Subject: below --
1999-11-23 19:52 Jim Chapman
1999-11-23 20:54 ` Frank McPherson
1999-11-24 8:25 ` LiuTao
1999-11-23 21:57 Brian Kuschak
2000-04-14 18:23 Need suggestions Ihor Lys
2018-07-14 16:04 Need Suggestions Athul Joy
2018-07-14 16:27 ` ozgur at goosey.org
2018-07-14 17:31 ` Cindy-Sue Causey
2018-07-14 18:07 ` ozgur at goosey.org
2018-07-15 13:39 ` valdis.kletnieks at vt.edu
2018-07-18 0:35 ` Richard Siegfried
2018-07-18 0:43 ` Richard Siegfried
2018-07-18 4:10 ` Dave Stevens
2018-07-18 4:41 ` valdis.kletnieks at vt.edu
2018-07-18 5:00 ` Dave Stevens
2018-07-18 4:39 ` inventsekar
2018-07-18 21:19 ` Daniel.
2018-07-18 21:29 ` Dave Stevens
2018-07-18 23:10 ` valdis.kletnieks at vt.edu
2018-07-19 1:16 ` Daniel.
2018-07-19 2:37 ` valdis.kletnieks at vt.edu
2018-07-19 2:42 ` Daniel.
2018-07-25 21:37 ` Himanshu Jha
2018-07-25 22:10 ` valdis.kletnieks at vt.edu
2018-08-01 21:29 ` Ruben Safir
2018-08-02 4:36 ` Himanshu Jha
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=383A0E2D.CFACF894@jlc.net \
--to=dmalek@jlc.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tliu@ict.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.