From: "atul srivastava" <atulsrivastava9@rediffmail.com>
To: linux-mips@linux-mips.org
Subject: ramdisk loading scheme...
Date: 24 Oct 2002 13:43:22 -0000 [thread overview]
Message-ID: <20021024134322.16414.qmail@webmail24.rediffmail.com> (raw)
which is better scheme..
either to include compressed ramdisk in kernel image image itself
identified by binary_ramdisk_gz_start symbol
or load ramdisk seperately.
I am using compressed ramdisk image as part
of vmlinux and later converting it into a binary image
as reqd. by bootloader.
in this piece of System.map file it shows that
ramdisk is included at the end of data section(_edata).
000000800f3f08 D prom_console_driver
00000000800f4000 D __rd_start
00000000800f4000 D _binary_ramdisk_gz_
0000000080187960 D __rd_end
0000000080187960 D _binary_ramdisk_gz_
0000000080188000 A __bss_start
0000000080188000 A _edata
this is done by following Makefile and ld.script
in Makefile i have
ramdisk.o: ramdisk.gz ld.script
$(LD) -no-warn-mismatch -T ld.script -b binary - o
$@ ramdisk.gz
in ld.script I have ,
OUTPUT_FORMAT("elf32-bigmips")
OUTPUT_ARCH(mips)
SECTIONS
{
.initrd :
{
*(.data)
}
}
one question is that is it necessary to include comprese ramdisk
at the end of data section ..?
rd_image_load is zero which i think is alright as it indicates the
offset in ram (device that holds initrd).
i am facing problems in execving the /bin/sh in main.c as it
accesses some wrong address in do_page_fault
i doubt there may be some issues when i am uncompressing the
ramdisk and all though i am being reported for corect length and
crc for ramdisk in boot messages.
Best Regards,
Atul
__________________________________________________________
Give your Company an email address like
ravi @ ravi-exports.com. Sign up for Rediffmail Pro today!
Know more. http://www.rediffmailpro.com/signup/
reply other threads:[~2002-10-24 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021024134322.16414.qmail@webmail24.rediffmail.com \
--to=atulsrivastava9@rediffmail.com \
--cc=linux-mips@linux-mips.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