From: Ed Martini <martini@c2micro.com>
To: linux-mips@linux-mips.org, Steve Stone <stone@c2micro.com>
Subject: initrd problem
Date: Thu, 10 Mar 2005 15:42:04 -0800 [thread overview]
Message-ID: <4230DB4C.7090103@c2micro.com> (raw)
Background:
I'm trying to get 2.6.11 to run on a MIPS Malta board with Yamon. The
kernel that comes with the board is 2.4.18 with an embedded ramdisk that
runs some scripts to install RPMS via NFS or CD-ROM. The kernel is
converted to s-records via objcopy(1), and loaded into memory via tftp.
I want to do something similar with 2.6.latest.
Problem:
On or about Nov 21 of last year, the CONFIG_EMBEDDED_RAMDISK disappeared.
http://www.linux-mips.org/archives/linux-mips/2004-11/msg00135.html
In it's place it is suggested to use the tools in arch/mips/boot, so I
tried it. I can cross-compile the kernel, and I get an ELF vmlinux. I
can convert it to ecoff with elf2ecoff, and attach an initrd image with
addinitrd. The problem begins here. I end up with an ecoff format
kernel which is not recognized by objcopy(1), and therefore no s-records.
It seems there is a program called gensrec that would do the job, but
google doesn't want to tell me where to get it. Some IRIX binary perhaps?
Solution?
Should I put CONFIG_EMBEDDED_RAMDISK and its ilk back into my kernel, or
write an ELF version of addinitrd? Other ideas?
Thanks in advance.
next reply other threads:[~2005-03-10 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 23:42 Ed Martini [this message]
2005-03-11 0:41 ` initrd problem Kumba
2005-03-14 11:01 ` Ralf Baechle
2005-03-15 22:37 ` Ed Martini
2005-03-16 12:06 ` Ralf Baechle
2005-03-17 0:23 ` initrd/initramfs problem Ed Martini
2005-03-25 19:24 ` Observations on LLSC and SMP Ed Martini
2005-03-25 19:37 ` Daniel Jacobowitz
2005-03-25 22:46 ` Ed Martini
2005-03-25 22:53 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 6:31 initrd problem colin
2005-04-15 6:31 ` colin
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=4230DB4C.7090103@c2micro.com \
--to=martini@c2micro.com \
--cc=linux-mips@linux-mips.org \
--cc=stone@c2micro.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