From: Bob Beck <beck@assurtech.com>
To: mgroeger@sysgo.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ADS860 - unable to load kernel- Bad magic number
Date: 27 Feb 2004 12:22:12 +1400 [thread overview]
Message-ID: <1077834132.4625.2.camel@budweiser> (raw)
In-Reply-To: <Pine.LNX.4.56.0402271730001.24044@mag.sysgo.com>
On Sat, 2004-02-28 at 06:32, Marius Groeger wrote:
> On Thu, 27 Feb 2004, Bob Beck wrote:
>
> > What is the difference between vmlinux and zImage.embedded ?
>
> vmlinux is the plain kernel ELF image. You can use it to analyse the kernel
> code or symbols, but you cannot boot it as-is.
>
> zImage.embedded is the compressed kernel image plus some glue code used as a
> bridge between the firmware and the kernel.
>
On my proprietary board (PPC 603). I do not have access to flash
so I am loading vmlinux into RAM and jumping to 0x10000. It is
running into problems in mmu_off.
Should I be loading zImage.embedded instead ?
Bob
I can see
> Regards,
> Marius
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-26 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Iq959772845498.03218@webmail1.inner-21cn.com>
2004-02-26 17:24 ` ADS860 - unable to load kernel- Bad magic number Bob Beck
2004-02-27 16:32 ` Marius Groeger
2004-02-26 22:22 ` Bob Beck [this message]
2004-02-27 17:29 ` Marius Groeger
2004-02-26 22:38 ` Bob Beck
2004-02-27 19:32 ` Dan Malek
2004-02-27 1:32 ` Bob Beck
2004-02-27 21:05 ` Dan Malek
2004-03-01 22:58 ` Booting Linux on a Custom PPC Board Bob Beck
2004-03-02 23:51 ` Wolfgang Denk
2004-03-02 17:45 ` Bob Beck
2004-02-27 4:34 ADS860 - unable to load kernel- Bad magic number m.venkatraj
2004-02-27 4:45 ` John Zhou
2004-02-27 8:07 ` song sam
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 8:27 Demke, Torsten
2004-02-27 9:14 m.venkatraj
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=1077834132.4625.2.camel@budweiser \
--to=beck@assurtech.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgroeger@sysgo.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;
as well as URLs for NNTP newsgroup(s).