From: Frank McPherson <frank@mitre.org>
To: Jim Chapman <jim.chapman@iname.com>
Cc: LiuTao <tliu@ict.ac.cn>,
LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: need suggestions
Date: Tue, 23 Nov 1999 15:54:54 -0500 [thread overview]
Message-ID: <383AFEF9.1EFCB317@mitre.org> (raw)
In-Reply-To: 383AF067.2B8EB961@iname.com
Jim and others,
We did some work last summer with a Dy4-177 VMEbus board which came to
us with the VxWorks bootrom intact, and used a similar solution to
yours.
> The
> binary-to-assembly convertor is a simple perl script which does almost
> the same thing as vxWorks' binToAsm tool.
We are using a piggyback.c (different from the one in chrpboot) to
produce the assembly. It's probably no better or worse than the perl
script you've got.
> The initrd stuff would need similar treatment, but since I don't use
> initrd, I haven't implemented it.
We DID find it useful to have initrd support, so our Makefiles can use
piggyback to make a tftp/vxworks loadable Linux kernel. If this is
something you could use, please let me know.
Cheers,
Frank
--
Frank H. McPherson IV
W118 Embedded Solutions Team
The MITRE Corporation
703-883-5404
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-23 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 19:52 need suggestions Jim Chapman
1999-11-23 20:54 ` Frank McPherson [this message]
1999-11-24 8:25 ` LiuTao
-- strict thread matches above, loose matches on Subject: below --
2000-04-14 18:23 Need suggestions Ihor Lys
1999-11-23 21:57 need suggestions Brian Kuschak
1999-11-23 1:42 LiuTao
1999-11-23 3:46 ` Dan Malek
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
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=383AFEF9.1EFCB317@mitre.org \
--to=frank@mitre.org \
--cc=jim.chapman@iname.com \
--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 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).