Re: 2.6.24 for mpc8458amc

["maxime louvel" <m.louvel@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]

Hi,

I have updated the uboot on the cards and get the same result

AMC=> bootm 0x1000000
## Booting image at 01000000 ...
  Image Name:   Linux-2.6.24
  Image Type:   PowerPC Linux Kernel Image (gzip compressed)
  Data Size:    1802038 Bytes =  1.7 MB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
  Uncompressing Kernel Image ... OK

No further messages...

However I have try to boot an image (2.6.23-rc6 from freescale) which has
been patched for my platform and it works.
Thus the problem is not coming from the uboot anymore, but from something
else.
I can't get the source from freescale to see what they have changed because
their is some other stuff (unrelated with my problem or even my platform)
that are confidential to them...

So what I am looking for here is a hint of where to look, an idea of what I
might have done wrong...

regards,
Maxime

On Wed, Feb 20, 2008 at 1:53 PM, Kumar Gala <galak@kernel.crashing.org>
wrote:

>
> On Feb 20, 2008, at 7:00 AM, maxime louvel wrote:
>
> > Hi,
> >
> > yes It has something like 16550 UART.
> > the compiler version is gcc-3.4.3 with some specific stuff for the
> > platform.
> > I also have a gcc-4.1.2 vanilla which has been compiled with the
> > previous one. The 4.1.2 works if you tell it to emulate the floating
> > point instructions.
> >
> > thanks Scott,
> > without the treeboot-walnut it compiled
> >
> > I have still my first problem though:
> >
> > AMC=> bootm 0x1000000
> > ## Booting image at 01000000 ...
> >   Image Name:   Linux-2.6.24
> >   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >   Data Size:    1802038 Bytes =  1.7 MB
> >   Load Address: 00000000
> >   Entry Point:  00000000
> >   Verifying Checksum ... OK
> >   Uncompressing Kernel Image ... OK
> >
> > and nothing else...
> >
> > Any idea ?
> >
> > This may become from the fact that the uboot installed on the cards
> > is old and it apparently doesn't support the newer version of the
> > kernel image... (I have got that from an another mailing list)
>
> Yes, you'll either need to look at updating u-boot and including
> support for the device tree in it or look at the cuImage wrappers in
> arch/powerpc/boot as a mechanism to boot a kernel w/an old fw.
>
> - k
>



-- 
Maxime Louvel
0044 7964 5555 80
43 Allen road
Whitemore reans
WV60AW Wolverhampton
United Kingdom

[-- Attachment #2: Type: text/html, Size: 3125 bytes --]