From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild,tegra124: add dummy obj- for Kbuild
Date: Thu, 20 Feb 2014 08:25:03 -0500 [thread overview]
Message-ID: <20140220132503.GY19081@bill-the-cat> (raw)
In-Reply-To: <20140220172227.A186.AA925319@jp.panasonic.com>
On Thu, Feb 20, 2014 at 05:22:27PM +0900, Masahiro Yamada wrote:
> Hello Tom,
> (ccing Simon and Stephan)
>
>
>
> > > Tom,
> > > Please apply this along with the Kbuild series.
> >
> > So with this, I then get:
> > Configuring for venice2 board...
> > make[2]: *** [arch/arm/dts/tegra124-venice2.dtb] Error 1
> > make[1]: *** [dts/dt.dtb] Error 2
> > make: *** [sub-make] Error 2
> > text data bss dec hex filename
> > 260562 15030 309960 585552 8ef50 venice2/u-boot
> > 18527 421 72 19020 4a4c venice2/spl/u-boot-spl
> >
> > Device Tree Source is not correctly specified.
> > Please define 'CONFIG_DEFAULT_DEVICE_TREE'
> > or build with 'DEVICE_TREE=<device_tree>' argument
> >
> > make[2]: *** [arch/arm/dts/tegra124-venice2.dtb] Error 1
> > make[1]: *** [dts/dt.dtb] Error 2
> > make: *** [sub-make] Error 2
> >
> > --------------------- SUMMARY ----------------------------
> > Boards compiled: 1
> > Boards with errors: 1 ( venice2 )
> > ----------------------------------------------------------
> >
> > What's going on as the config file sets CONFIG_DEFAULT_DEVICE_TREE
> >
>
>
>
> Commit 5ab502cb89 has been applied and the build system
> now expects device tree sources should reside under arch/$(ARCH)/dts/.
>
> But the device tree of venice2 board is still remaining
> in board/nvidia/dts/.
> This is the cause of the build error.
> (Commit 5ab502cb89 had been posted before venice2 board
> support was merged. So there happened an unvisible conflict.)
>
> Actually I did not expect dts series was applied so soon
> because Simon and I was still discussing that series.
> And I guess Simon is not happy about Commit 5ab502cb89.
>
> Anyway, we need to do something with venice2's build error
> immediately.
>
> I think we have two options.
>
> [1] Move also venice2 device tree to arch/arm/dts directory.
> I have posted a patch:
> http://patchwork.ozlabs.org/patch/322082/
>
> [2] revert the following commits in this order
> 3284c8b8ca (dts: generate multiple device tree blobs)
> 5ab502cb89 (dts: move device tree sources to arch/$(ARCH)/dts/)
>
>
> If we like to gather all device trees to arch/$(ARCH)/dts,
> the choice will be [1].
>
> On the other hand, if we like to put *.dtsi to arch/$(ARCH)/dts
> whilst *.dts to board/$(VENDOR)/dts, the choice will be [2].
Well, I think our long term plan here is (a) mirror the kernel today and
since their long term plan is "move device trees out of tree, then deal
with it there" once they've got a plan there, we can follow (and indeed
should be contributing to the conversation).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140220/4a0d5033/attachment.pgp>
next prev parent reply other threads:[~2014-02-20 13:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 13:26 [U-Boot] [PATCH] kbuild,tegra124: add dummy obj- for Kbuild Masahiro Yamada
2014-02-19 14:46 ` Albert ARIBAUD
2014-02-19 16:36 ` Stephen Warren
2014-02-19 20:40 ` Tom Rini
2014-02-19 20:44 ` Stephen Warren
2014-02-20 8:35 ` Masahiro Yamada
2014-02-20 8:24 ` Masahiro Yamada
2014-02-20 16:15 ` Stephen Warren
2014-02-21 11:45 ` Masahiro Yamada
2014-02-21 16:33 ` Stephen Warren
2014-02-20 8:23 ` Masahiro Yamada
2014-02-20 9:06 ` Albert ARIBAUD
2014-02-19 20:51 ` Tom Rini
2014-02-20 8:22 ` Masahiro Yamada
2014-02-20 13:25 ` Tom Rini [this message]
2014-02-19 21:12 ` Tom Rini
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=20140220132503.GY19081@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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