linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dave Strout <dstrout@linuxfoundary.com>
To: Donald White <dbwhite@asu.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can compile, now on to booting
Date: Thu, 06 Jun 2002 09:00:33 -0400	[thread overview]
Message-ID: <3CFF5CF1.8080204@linuxfoundary.com> (raw)
In-Reply-To: 3CFEDFC1.9080603@asu.edu


Ahhh -- I was hoping that somebody would have some thoughts like that.
 Could someone send me a copy of vxhack.c ?  The link in the FAQ (
ftp://ftp.mvista.com/pub/Area51/ppc-8xx/vxhack.c  ) doesn't have
anything anymore....

thanks,
dave.


Donald White wrote:

>
> I did this once on a mpc860 board.  It involved running the uncompressed
> kernel image through vxhack.c from Dan Malek with a few fixes since the
> segments seemed to have moved around.  The VxWorks loader would then
> load the hacked image through bootp or tftp.  I also had to have one of
> the Linux bootloader files initialize a bd_t structure.  I was able to
> poke around in memory and find where the VxWorks loader was keeping the
> environment.
>
> Don


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-06-06 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 17:36 Basics -- what tools for Walnut? Dave Strout
2002-06-05 17:43 ` Mark Hatle
2002-06-05 17:49 ` Frank Rowand
2002-06-05 18:14   ` Dan Malek
2002-06-05 18:24     ` Dave Strout
2002-06-05 19:16 ` Wolfgang Denk
2002-06-05 20:16   ` Can compile, now on to booting Dave Strout
2002-06-06  4:06     ` Donald White
2002-06-06 13:00       ` Dave Strout [this message]

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=3CFF5CF1.8080204@linuxfoundary.com \
    --to=dstrout@linuxfoundary.com \
    --cc=dbwhite@asu.edu \
    --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).