This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Loading linux image through redboot.
- From: Ian Campbell <icampbell at arcomcontrols dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: 11 Oct 2002 13:08:12 +0100
- Subject: RE: [ECOS] Loading linux image through redboot.
- References: <850597605E79D21182830008C7A4B9CF1EB4246A@COMM1>
> Isn't the 'kernel' file you generate this way identical to
> 'vmlinuz' that is produced by the build process anyway?
I don't think so. The build process produces vmlinux (with an x) which
is an ELF executable. Often when you install a kernel you rename bzImage
to vmlinuz (with a z).
vmlinux gets turned into a raw binary, compressed and linked as data
with arch/i386/boot/compressed/head.S (the decompresser) to produce
bvmlinux, which is again an ELF executable. This is then made into a raw
binary called bvmlinux.out which is the protected mode starting point,
which is what the code I posted requires.
bvmlinux.out is then concatenated with the real-mode header to produce
the final bzImage. The dd command basically just strips of the real mode
part and leaves what was bvmlinux.out. You could equally well (and I do)
just use the bvmlinux.out directly.
Ian.
--
Ian Campbell
Design Engineer
Arcom Control Systems Ltd,
Clifton Road,
Cambridge CB1 7EA
United Kingdom
Tel: +44 (0)1223 403465
E-Mail: icampbell@arcomcontrols.com
Web: http://www.arcomcontrols.com
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss