From: Ruedi.Hofer@ascom.ch
To: linuxppc-embedded@lists.linuxppc.org
Subject: initrd
Date: Thu, 03 Feb 2000 16:39:30 +0100 (CET) [thread overview]
Message-ID: <0FPD00LDV2DPNM@pmdf-it.hasler.ascom.ch> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1396 bytes --]
Hi
Is there something wrong with the mapping???
Boot message in case of failure..
loaded at: 0011C000 001271BC
relocated to: 00100000 0010B1BC
board data at: 00FF0000 00FF001C
relocated to: 00200100 0020011C
zimage at: 00122000 00182FEC
initrd at: 00182FEC 00236655
avail ram: 00237000 01000000
Did you change something in this part of the Makefile (in mbxboot) to get it working?
zvmlinux.initrd: zvmlinux
$(LD) $(ZLINKFLAGS) -o zvmlinux.initrd.tmp $(OBJECTS)
$(OBJCOPY) $(OBJCOPY_ARGS) -R .comment \
--add-section=initrd=ramdisk.image.gz \
--add-section=image=../coffboot/vmlinux.gz \
zvmlinux.initrd.tmp zvmlinux.initrd
$(CC) $(CFLAGS) -DINITRD_OFFSET=`sh offset $(OBJDUMP)
zvmlinux.initrd initrd` \
-DINITRD_SIZE=`sh size $(OBJDUMP) zvmlinux.initrd
initrd` \
-DZIMAGE_OFFSET=`sh offset $(OBJDUMP) zvmlinux.initrd
image` \
-DZIMAGE_SIZE=`sh size $(OBJDUMP) zvmlinux.initrd image`
\
-c -o misc.o misc.c
$(LD) $(ZLINKFLAGS) -o zvmlinux.initrd.tmp $(OBJECTS)
$(OBJCOPY) $(OBJCOPY_ARGS) -R .comment \
--add-section=initrd=ramdisk.image.gz \
--add-section=image=../coffboot/vmlinux.gz \
zvmlinux.initrd.tmp $@
rm zvmlinux.initrd.tmp
Any ideas?
TIA
\Ruedi
next reply other threads:[~2000-02-03 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-03 15:39 Ruedi.Hofer [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-22 9:53 Initrd Sébastien Chrétien
2008-08-21 13:02 Initrd Sébastien Chrétien
2000-12-12 22:27 INITRD Nicu Popovici
2000-02-04 7:30 initrd Ruedi.Hofer
2000-02-03 15:18 initrd Ruedi.Hofer
2000-02-04 6:41 ` initrd Dan Malek
1998-07-03 6:47 initrd Alex deVries
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=0FPD00LDV2DPNM@pmdf-it.hasler.ascom.ch \
--to=ruedi.hofer@ascom.ch \
--cc=linuxppc-embedded@lists.linuxppc.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 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.