From: "Alexander Voropay" <alec@artcoms.ru>
To: "inpreet" <singh.inpreet@netsity.com>, <linux-mips@linux-mips.org>
Subject: Re: Ramdisk issue please help!!!
Date: Fri, 5 Aug 2005 18:22:31 +0400 [thread overview]
Message-ID: <013601c599c9$1fe2ca40$6cf9a8c0@ALEC> (raw)
In-Reply-To: 01a901c599a4$2f855280$3c67a8c0@netsity.com
"inpreet" <singh.inpreet@netsity.com> wrote:
>I am trying to build ramdisk image and launch bootsplash image at boot time.
>Steps I followed:
>1. get splash image initrd.splash using splash binary.
...
>8. results in initrd.gz
>
>Now while compiling kernel image I am embedding initrd.gz into it. Here is what I am doing
You don't need nothing special for *embedded *, not external "MIPS initrd" on a 2.4 kernels.
It works just fine from the CVS.
1) Prepare your "ramdisk.img" with EXT2FS/other FS
2) gzip it.
3) Put this "ramdisk.gz" into the arch/mips/ramdisk/
4) Enable in the configfile :
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_EMBEDDED_RAMDISK=y
CONFIG_EMBEDDED_RAMDISK_IMAGE="ramdisk.gz"
5) make . Kernel build system will find this image automagically.
6) Run this kernel (vmlinux) without a "root=" parameter.
There is example of my kernel bootlog:
...
Determined physical RAM map:
memory: 01800000 @ 00000000 (usable)
Initial ramdisk at: 0x801b1000 (593920 bytes)
...
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
...
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 580k freed
VFS: Mounted root (ext2 filesystem) readonly.
...
root FS is mouned now as /dev/ram0
--
-=AV=-
WARNING: multiple messages have this Message-ID (diff)
From: "Alexander Voropay" <alec@artcoms.ru>
To: inpreet <singh.inpreet@netsity.com>, linux-mips@linux-mips.org
Subject: Re: Ramdisk issue please help!!!
Date: Fri, 5 Aug 2005 18:22:31 +0400 [thread overview]
Message-ID: <013601c599c9$1fe2ca40$6cf9a8c0@ALEC> (raw)
Message-ID: <20050805142231.OOLIgsFs8r5cU5ndrFRjFLz8IrjlbQg34LAelU-Kn5M@z> (raw)
In-Reply-To: 01a901c599a4$2f855280$3c67a8c0@netsity.com
"inpreet" <singh.inpreet@netsity.com> wrote:
>I am trying to build ramdisk image and launch bootsplash image at boot time.
>Steps I followed:
>1. get splash image initrd.splash using splash binary.
...
>8. results in initrd.gz
>
>Now while compiling kernel image I am embedding initrd.gz into it. Here is what I am doing
You don't need nothing special for *embedded *, not external "MIPS initrd" on a 2.4 kernels.
It works just fine from the CVS.
1) Prepare your "ramdisk.img" with EXT2FS/other FS
2) gzip it.
3) Put this "ramdisk.gz" into the arch/mips/ramdisk/
4) Enable in the configfile :
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_EMBEDDED_RAMDISK=y
CONFIG_EMBEDDED_RAMDISK_IMAGE="ramdisk.gz"
5) make . Kernel build system will find this image automagically.
6) Run this kernel (vmlinux) without a "root=" parameter.
There is example of my kernel bootlog:
...
Determined physical RAM map:
memory: 01800000 @ 00000000 (usable)
Initial ramdisk at: 0x801b1000 (593920 bytes)
...
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
...
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 580k freed
VFS: Mounted root (ext2 filesystem) readonly.
...
root FS is mouned now as /dev/ram0
--
-=AV=-
next prev parent reply other threads:[~2005-08-05 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 9:58 Ramdisk issue please help!!! inpreet
2005-08-05 9:58 ` inpreet
2005-08-05 14:22 ` Alexander Voropay [this message]
2005-08-05 14:22 ` Alexander Voropay
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='013601c599c9$1fe2ca40$6cf9a8c0@ALEC' \
--to=alec@artcoms.ru \
--cc=linux-mips@linux-mips.org \
--cc=singh.inpreet@netsity.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