Thanks for your reply.
I tried using the resulted vmlinux.32 and got the
After looking into it, I found out that t0 is loaded
with 0x0 while it should load _edata value which
should be 0xffffffff80310000 (according to the
System.map). in the 32 bit version (which I build
using a different toolchain), edata is loaded to t0
register as it should.
It looks to me like it is a toolchain problem.
1. where can I download a pre built, prooven working
64 bit toolchain?
2. Is there anything else that can cause this problem?
--- "Maciej W. Rozycki" <firstname.lastname@example.org> wrote:
> On Tue, 17 May 2005, Michael Belamina wrote:
> > I have built a 64 bit kernel for BCM1250.
> > When the kernel is loaded and control is passed
> > kernel_entry there is an exception:
> > CFE> boot -elf LinuxServer:vmlinux.64
> I'm assuming vmlinux.64 is a 64-bit ELF file. If
> so, then, well,
> depending on the version of CFE you have, this may
> or may not work. The
> workaround is to always use 32-bit ELF files. You
> should get one after
> your Linux build -- if not (which may depend on how
> you do builds), then
> try `make vmlinux.32' and use the result.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around