From: LiuTao <tliu@ict•ac.cn>
To: Dan Malek <dmalek@jlc•net>
Cc: linuxppc <linuxppc-dev@lists•linuxppc.org>
Subject: Re: need suggestions
Date: Tue, 23 Nov 1999 11:46:54 +0800 [thread overview]
Message-ID: <383A0E2E.9A261E81@ict.ac.cn> (raw)
In-Reply-To: 383A0E2D.CFACF894@jlc.net
Hi Dan:
Thanks for your advice.
The bootloader that I am using with vxWorks uses FTP but not TFTP.
And I don't have the source code of that bootloader. I think there
are maybe some problems to use it download and boot linux. So I hope
to find a TFTP source code and program a bootloader by myself.
Of course, if anybody has a presented bootloader source code,
that's great.
LiuTao
Dan Malek wrote:
>
> 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: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 1:42 need suggestions LiuTao
1999-11-23 3:46 ` Dan Malek
1999-11-23 3:46 ` LiuTao [this message]
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
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=383A0E2E.9A261E81@ict.ac.cn \
--to=tliu@ict$(echo .)ac.cn \
--cc=dmalek@jlc$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/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