From: Peter Korsgaard <jacmet@sunsite.dk>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: cuImage generation
Date: Wed, 19 Sep 2007 16:53:14 +0200 [thread overview]
Message-ID: <87ps0elnad.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20070919141953.GB8023@ld0162-tx32.am.freescale.net> (Scott Wood's message of "Wed\, 19 Sep 2007 09\:19\:53 -0500")
>>>>> "Scott" == Scott Wood <scottwood@freescale.com> writes:
Scott> On Wed, Sep 19, 2007 at 09:28:31AM +0200, Gerhard Pircher wrote:
>> I tried to compile a 2.6.23-rc6 kernel yesterday, but wasn't able to get a
>> cuImage.<platform) out of it (only the uImage file was generated). My
>> platform config defines DEFAULT_UIMAGE and WANT_DEVICE_TREE. Do I need to
>> generate it manually or is there a makefile where I have to specify it?
>> Naturally I added my cuboot wrapper code to the arch/powerpc/boot/Makefile.
I have the same problem here..
Scott> Did you specify a device tree to use in CONFIG_DEVICE_TREE?
Yes.
% grep TREE .config
CONFIG_PROC_DEVICETREE=y
CONFIG_WANT_DEVICE_TREE=y
CONFIG_DEVICE_TREE="mpc8349emitx.dts"
How is it supposed to work now cuImage no longer is in BOOT_TARGETS?
What make target are you supposed to work. It works if I add
cuImage.83xx to BOOT_TARGETS and call make cuImage.83xx, but that can
hardly be the correct way?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2007-09-19 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 7:28 cuImage generation Gerhard Pircher
2007-09-19 14:19 ` Scott Wood
2007-09-19 14:53 ` Peter Korsgaard [this message]
2007-09-19 15:01 ` Scott Wood
2007-09-19 15:20 ` Peter Korsgaard
2007-09-19 15:25 ` Gerhard Pircher
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=87ps0elnad.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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.