From: Ralf Baechle <ralf@cobaltmicro.com>
To: adevries@engsoc.carleton.ca (Alex deVries)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: make zImage, and initrd...
Date: Fri, 10 Oct 1997 17:58:48 -0700 (PDT) [thread overview]
Message-ID: <199710110058.RAA14665@dull.cobaltmicro.com> (raw)
In-Reply-To: <Pine.LNX.3.95.971010192929.364D-100000@lager.engsoc.carleton.ca> from "Alex deVries" at Oct 10, 97 07:41:19 pm
> I'm working on adding the ramdisk and initrd features to the kernel. It
> compiles, which is pretty good for my first kernel patch.
>
> But, I have no way to actually test it. The kernel needs to find the
> offset of the ramdisk in the first 11 bits of one of the boot headers, so
> the kernel needs to be less than 2047k.
Dunno what you're trying to do, but it sounds extremly weired ...
> This wouldn't normally be a problem, but doing a 'make zImage' tells me
> that:
> ./mkboot zImage.tmp zImage
> Input file isn't a little endian ELF file
> make[1]: *** [zImage] Error 1
>
> What would be required to make mkboot handle zImage, or bzImage?
Don't do it. mkboot is used for the boxes that use Milo for booting to
convert the ELF executable into an a.out file that Milo accepts. Milo
again is necessary because the ARC firmware is so incredibly buggy and I
don't want to have more ARC stuff in the kernel than absolutly necessary.
What I suggest instead is to load the ramdisk file using the ARCS
Open, Read, Write, Close and Seek functions from any ARC supported media.
That includes tapes, CDROM, EFS, XFS and even tftp. Take the information
what file to read from the ARC command line.
> In the meantime, I will try to strip down a kernel to below 2047k. My
> current one is 2347.
Why limiting the kernel size? 640kb are enough for everybody?
> Any other ideas?
Yes, time to leave for Sushi with Miguel :-)
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@cobaltmicro.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: make zImage, and initrd...
Date: Fri, 10 Oct 1997 17:58:48 -0700 (PDT) [thread overview]
Message-ID: <199710110058.RAA14665@dull.cobaltmicro.com> (raw)
Message-ID: <19971011005848.egxI_08k6ngAP2szU4sMr1joLR09dgj7JHPKb2I_QzQ@z> (raw)
In-Reply-To: <Pine.LNX.3.95.971010192929.364D-100000@lager.engsoc.carleton.ca> from "Alex deVries" at Oct 10, 97 07:41:19 pm
> I'm working on adding the ramdisk and initrd features to the kernel. It
> compiles, which is pretty good for my first kernel patch.
>
> But, I have no way to actually test it. The kernel needs to find the
> offset of the ramdisk in the first 11 bits of one of the boot headers, so
> the kernel needs to be less than 2047k.
Dunno what you're trying to do, but it sounds extremly weired ...
> This wouldn't normally be a problem, but doing a 'make zImage' tells me
> that:
> ./mkboot zImage.tmp zImage
> Input file isn't a little endian ELF file
> make[1]: *** [zImage] Error 1
>
> What would be required to make mkboot handle zImage, or bzImage?
Don't do it. mkboot is used for the boxes that use Milo for booting to
convert the ELF executable into an a.out file that Milo accepts. Milo
again is necessary because the ARC firmware is so incredibly buggy and I
don't want to have more ARC stuff in the kernel than absolutly necessary.
What I suggest instead is to load the ramdisk file using the ARCS
Open, Read, Write, Close and Seek functions from any ARC supported media.
That includes tapes, CDROM, EFS, XFS and even tftp. Take the information
what file to read from the ARC command line.
> In the meantime, I will try to strip down a kernel to below 2047k. My
> current one is 2347.
Why limiting the kernel size? 640kb are enough for everybody?
> Any other ideas?
Yes, time to leave for Sushi with Miguel :-)
Ralf
next prev parent reply other threads:[~1997-10-11 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-09 22:57 Arch specific initramdisk? Alex deVries
1997-10-10 1:27 ` Ralf Baechle
1997-10-10 1:27 ` Ralf Baechle
1997-10-10 23:41 ` make zImage, and initrd Alex deVries
1997-10-11 0:58 ` Ralf Baechle [this message]
1997-10-11 0:58 ` Ralf Baechle
1997-10-11 6:11 ` Warner Losh
1997-10-11 6:11 ` Warner Losh
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=199710110058.RAA14665@dull.cobaltmicro.com \
--to=ralf@cobaltmicro.com \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.engr.sgi.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