From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 1/3] dts: re-write dts/Makefile more simply with Kbuild
Date: Thu, 20 Feb 2014 18:30:44 +0900 [thread overview]
Message-ID: <20140220183043.A196.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <20140219211111.GQ19081@bill-the-cat>
Hello Tom, Simon,
On Wed, 19 Feb 2014 16:11:11 -0500
Tom Rini <trini@ti.com> wrote:
> On Wed, Feb 05, 2014 at 11:28:25AM +0900, Masahiro Yamada wrote:
>
> > Useful rules in scripts/Makefile.lib allows us to easily
> > generate a device tree blob and wrap it in assembly code.
> >
> > We do not need to parse a linker script to get output format and arch.
> >
> > This commit deletes ./u-boot.dtb since it is a copy of dts/dt.dtb.
> >
> > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
>
> Applied to u-boot/master, thanks!
>
> --
> Tom
Ditto.
Possibly it was missed because Simon and I were discussing
in version 2 thread.
> > >
> > > Besides, dts/dt.dtb is a prerequisite of dts/dt.dtb.S
> > > when CONFIG_OF_EMBED is enabled.
> > >
> > > I believe keeping dts/dt.dtb is reasonable enough.
> > >
> > > Better to keep both?
> >
> > Yes I think so.
>
>
> OK.
> I will revive ./u-boot.dtb and post a new version.
>
> And I will send it as a single patch
> dropping 2/3 and 3/3.
> Do you think it's better?
>
> Many kbuild-related patches are being stuck on patchwork
> and my local branch is getting messed up.
> I don't want to delay this patch any more.
I was planning to post a new version.
But before that, version 3 was applied.
So, what should I do?
Shall I post a follow-up patch to revive a
device tree at the top directory (./u-boot.dtb) ?
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-02-20 9:30 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 [this message]
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
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=20140220183043.A196.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.