From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 2/3] dts: move device tree sources to arch/$(ARCH)/dts/
Date: Thu, 20 Feb 2014 18:22:20 +0900 [thread overview]
Message-ID: <20140220182220.A192.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <20140219211117.GR19081@bill-the-cat>
Hello Tom, Simon
> > Unlike Linux Kernel, U-Boot historically had *.dts files under
> > board/$(VENDOR)/dts/ and *.dtsi files under arch/$(ARCH)/dts/.
> >
> > I think arch/$(ARCH)/dts dicretory is a better location
> > to store both *.dts and *.dtsi files.
> >
> > For example, before this commit, board/xilinx/dts directory
> > had both Microblaze dts (microblaze-generic.dts) and
> > ARM dts (zynq-*.dts), which are totally unrelated.
> >
> > This commit moves *.dts to arch/$(ARCH)/dts/ directories,
> > allowing us to describe nicely mutiple DTBs generation in the next commit.
> >
> > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
>
> Applied to u-boot/master, thanks!
>
> --
> Tom
This series was applied sooner than I had expected.
Simon and I were still discussing this series.
So I am afraid Simon is really not happy about it
because he was opposed to moving *.dts files
from vendor directories to arch directories.
Tom also mentioned as follows:
> This, I think is backwards. Xilinx has (and Freescale and others are or
> will be joining them) a lot of things shared between them as IP blocks
> get reused from non-ARM to ARM CPUs. So there's a level of DT sharing
> for these blocks between the CPUs.
I'd like to know Tom's option about the device tree structure.
Let me confirm if my patch is doing right thing.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-02-20 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 2:28 [U-Boot] [PATCH v3 0/3] Simplify dts/Makefile and support multiple DTBs generation Masahiro Yamada
2014-02-05 2:28 ` [U-Boot] [PATCH v3 1/3] dts: re-write dts/Makefile more simply with Kbuild Masahiro Yamada
2014-02-15 23:41 ` Simon Glass
2014-02-19 21:11 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-02-20 9:30 ` Masahiro Yamada
2014-02-20 13:39 ` Tom Rini
2014-05-27 18:32 ` [U-Boot] [PATCH v3 " York Sun
2014-05-28 0:54 ` Masahiro Yamada
2014-06-01 16:34 ` Simon Glass
2014-06-02 6:18 ` Michal Simek
2014-02-05 2:28 ` [U-Boot] [PATCH v3 2/3] dts: move device tree sources to arch/$(ARCH)/dts/ Masahiro Yamada
2014-02-19 21:11 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-02-20 9:22 ` Masahiro Yamada [this message]
2014-02-20 13:43 ` Tom Rini
2014-02-05 2:28 ` [U-Boot] [PATCH v3 3/3] dts: generate multiple device tree blobs Masahiro Yamada
2014-02-15 23:41 ` Simon Glass
2014-02-19 21:11 ` [U-Boot] [U-Boot, v3, " 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=20140220182220.A192.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.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 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.