From: Ralf Baechle <ralf@linux-mips.org>
To: Ed Martini <martini@c2micro.com>
Cc: linux-mips@linux-mips.org, Steve Stone <stone@c2micro.com>
Subject: Re: initrd problem
Date: Mon, 14 Mar 2005 11:01:01 +0000 [thread overview]
Message-ID: <20050314110101.GF7759@linux-mips.org> (raw)
In-Reply-To: <4230DB4C.7090103@c2micro.com>
On Thu, Mar 10, 2005 at 03:42:04PM -0800, Ed Martini wrote:
> 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.
I guess that was an act of desperation - YAMON needs SRECs to be happy
but doesn't know anything about SRECs.
> 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?
make vmlinux.srec; the resulting file will be in arch/mips/boot/vmlinux.srec.
> Should I put CONFIG_EMBEDDED_RAMDISK and its ilk back into my kernel, or
> write an ELF version of addinitrd? Other ideas?
Things vanish for a reason ... Try CONFIG_INITRAMFS_SOURCE instead.
Ralf
next prev parent reply other threads:[~2005-03-14 11:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 23:42 initrd problem Ed Martini
2005-03-11 0:41 ` Kumba
2005-03-14 11:01 ` Ralf Baechle [this message]
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-17 0:37 ` 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
2019-01-24 9:37 Alexander Shiyan
2019-01-30 6:08 ` Sascha Hauer
2019-01-30 8:03 ` Alexander Shiyan
2019-01-30 8:19 ` Alexander Shiyan
2019-01-30 9:14 ` Sascha Hauer
2019-01-30 9:20 ` Alexander Shiyan
2019-01-30 9:35 ` Sascha Hauer
2019-01-31 9:03 ` Alexander Shiyan
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=20050314110101.GF7759@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=martini@c2micro.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.