From: Matthew McClintock <msm@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: krish <radhakrishna.p@gmail.com>, kexec@lists.infradead.org
Subject: Re: kexec for powerpc mpc85xx processors
Date: Sat, 10 Jul 2010 02:23:20 -0500 [thread overview]
Message-ID: <1278746600.20846.1.camel@localhost> (raw)
In-Reply-To: <20100710063701.GA12280@verge.net.au>
On Sat, 2010-07-10 at 15:37 +0900, Simon Horman wrote:
> On Sat, Jul 10, 2010 at 10:14:25AM +0530, krish wrote:
> > Hi,
> >
> > I am using linux-2.6.34.1 version for both mpc83xx and mpc85xx processors.
> > This version of kernel supports kexec for both 83xx and 85xx processors.
> > I have been using ELDK toolchain for PowerPC processors.
> > I am using u-boot as boot loader and uImage & dtb images as Linux images.
> >
> > I have downloaded 2.0.2-rc1 package and tried to compile for mpc83xx.
> > I have used following command to configure kexec-tools for ppc.
> > ./configure --prefix=/home/krishna/work/kexec-tools-6dd624d/
> > CC=/opt/ELDK41/usr/bin/ppc_6xx-gcc LD=/opt/ELDK41/usr/bin/ppc_6xx-ld
> > BUILD_CC=/usr/bin/gcc --target=ppc --host=i686
> > CC=/opt/ELDK41/usr/bin/ppc_6xx-gcc
> > TARGET_CC=/opt/ELDK41/usr/bin/ppc_6xx-gcc;
> >
> > The compilation was broken for PPC.
>
> Could you provide the compile errors that you are seeing?
>
Also, how do you know your kernel supports kexec?
-Matthew
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-07-10 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 6:09 kexec for powerpc mpc85xx processors krish
2010-07-09 6:28 ` Matthew McClintock
2010-07-09 6:43 ` Simon Horman
2010-07-10 4:44 ` krish
2010-07-10 6:37 ` Simon Horman
2010-07-10 7:23 ` Matthew McClintock [this message]
2010-07-10 9:08 ` krish
2010-07-11 16:53 ` Matthew McClintock
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=1278746600.20846.1.camel@localhost \
--to=msm@freescale.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=radhakrishna.p@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.