From: Jon Loeliger <jdl@freescale.com>
To: maxime louvel <m.louvel@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6.24 for mpc8458amc
Date: Tue, 19 Feb 2008 08:24:51 -0600 [thread overview]
Message-ID: <47BAE6B3.7090000@freescale.com> (raw)
In-Reply-To: <dda529d0802190359r526dc959y8117185e1834e9f4@mail.gmail.com>
maxime louvel wrote:
> Hi,
>
> I am trying to make a 2.6.24 vanilla kernel boot (an work fine in a
> second time) on a mpc8548amc board.
> I have add the platform specific stuff from the sources of the current
> kernel running on the cards.
> What I have basically add is:
> - a folder mpc8548amc, in the config/platform directory, which allow to
> select the mpc8548amc as the supported platform
> - add the following files:
> - arch/ppc/configs/mpc8548amc_defconfig
> - arch/ppc/configs/platforms/85xx/mpc_8548_amc.h and .c
> - I have used the dts of an another platform (mpc8548cds) which seems
> quite the same, but I haven't got any confirmation of that yet.
Uh, let's clear up minor confusion here. Are you using
ARCH=ppc or ARCH=powerpc? I'm surprised to see that there
is mention of arch/ppc/... above. Are you sure this is an
ARCH=ppc build? You won't need a DTS file at all then.
But if you are using a DTS file, and I suspect you should,
then this is ARCH=powerpc.
> When I am booting the kernel image I get:
>
> AMC=> dhcp 0x1000000 uImage.amc.2.6.24
> Speed: 1000, full duplex
> BOOTP broadcast 1
> DHCP client bound to address 10.255.255.2 <http://10.255.255.2/>
> Using eTSEC0 device
> TFTP from server 0.0.0.0 <http://0.0.0.0/>; our IP address is
> 10.255.255.2 <http://10.255.255.2/>; sending through gateway 10.1.1.1
> <http://10.1.1.1/>
> Filename 'uImage.amc.2.6.24'.
> Load address: 0x1000000
> Loading: ##############################
> ###################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ###########################
> done
> Bytes transferred = 1802102 (1b7f76 hex)
> 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...
>
> Does someone has an idea ?
>
> thanks,
> Maxime
>
Did you download a DTB file and use it on the bootm
command? Nope.
This is really a FAQ failure mode. Are you sure
you have the console set up properly? Any chance
you can get to the __log_buf with a BDI-2000?
Thanks,
jdl
next prev parent reply other threads:[~2008-02-19 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:59 2.6.24 for mpc8458amc maxime louvel
2008-02-19 12:19 ` raul.moreno
2008-02-20 5:19 ` Kumar Gala
2008-02-20 13:00 ` maxime louvel
2008-02-20 13:53 ` Kumar Gala
2008-02-25 10:42 ` maxime louvel
2008-02-19 14:24 ` Jon Loeliger [this message]
2008-02-19 14:42 ` maxime louvel
2008-02-19 14:57 ` Jon Loeliger
2008-02-19 16:38 ` maxime louvel
2008-02-19 17:53 ` Scott Wood
2008-02-19 20:17 ` Josh Boyer
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=47BAE6B3.7090000@freescale.com \
--to=jdl@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=m.louvel@gmail.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).