linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Charles Lepple <clepple@linus.mitre.org>
To: Scott Wood <scott@broadlink.com>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: RPX Lite kernel
Date: Wed, 07 Jul 1999 08:33:28 -0400	[thread overview]
Message-ID: <199907071233.IAA10468@linus.mitre.org> (raw)
In-Reply-To: Your message of "Tue, 06 Jul 1999 10:40:01 PDT." <37823F71.2BD5AF5F@broadlink.com>


>[...] or written a utility to convert an ELF kernel into SREC format?  

Have you looked at objcopy? Unless I'm mistaken, you should be able to do a

  'objcopy -O srec vmlinux vmlinux.s19'

One issue that may crop up is the load address. objdump will let you look at
the ELF headers to make sure that you aren't trying to load the kernel at
at an address which does not map to RAM.

--Charles Lepple
clepple@mitre.org

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-07-07 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37823F71.2BD5AF5F@broadlink.com>
     [not found] ` <3782515B.471DCEBE@broadlink.com>
1999-07-07 11:59   ` RPX Lite kernel Marcus Sundberg
1999-07-07 19:10     ` Scott Wood
1999-07-07 21:35       ` Matt Porter
1999-07-07 22:03         ` Daniel Jacobowitz
1999-07-08 20:34         ` Scott Wood
1999-07-07 12:33 ` Charles Lepple [this message]
     [not found] <378248CD.E3174193@broadlink.com>
     [not found] ` <3784C7D7.2EC6C451@jlc.net>
1999-07-08 20:40   ` Scott Wood

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=199907071233.IAA10468@linus.mitre.org \
    --to=clepple@linus.mitre.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=scott@broadlink.com \
    /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).