All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] dts: re-write dts/Makefile more simply with Kbuild
Date: Tue, 18 Feb 2014 21:45:12 -0800	[thread overview]
Message-ID: <CAPnjgZ19uBT3-5J5F+KTZJBmoWEndT4bq-6_AmZWwJYVH-b_EA@mail.gmail.com> (raw)
In-Reply-To: <20140218182707.A132.AA925319@jp.panasonic.com>

Hi Masahiro,

On 18 February 2014 01:27, Masahiro Yamada <yamada.m@jp.panasonic.com> wrote:
> Hello Simon,
>
>
>
>> > 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
>>
>> I'd rather have the former and delete the latter temporary file as
>> part of the build. u-boot.dtb is currently a build output.
>
>
> This is what I have said in the thread
> Re: [PATCH] dts: re-write dts/Makefile more simply with Kbuild
>
> We must keep dts/dt.dtb to suppress the re-generation of dts/dt.dtb.

OK. From memory when I did this, it was just a temporary file which
was used to create dts/dt.o. Make deleted it at the end of the build,
I think. But I may remember wrong, and it doesn't matter anyway.

>
> 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.

Regards,
Simon

  reply	other threads:[~2014-02-19  5:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04  9:38 [U-Boot] [PATCH v2 0/3] Simplify dts/Makefile and support multiple DTBs generation Masahiro Yamada
2014-02-04  9:38 ` [U-Boot] [PATCH v2 1/3] dts: re-write dts/Makefile more simply with Kbuild Masahiro Yamada
2014-02-15 23:38   ` Simon Glass
2014-02-18  9:27     ` Masahiro Yamada
2014-02-19  5:45       ` Simon Glass [this message]
2014-02-19  6:06         ` Masahiro Yamada
2014-02-19  6:12           ` Simon Glass
2014-02-04  9:38 ` [U-Boot] [PATCH v2 2/3] dts: move device tree sources to arch/$(ARCH)/dts/ Masahiro Yamada
2014-02-05 21:47   ` Simon Glass
2014-02-06  5:50     ` Masahiro Yamada
2014-02-15 23:46       ` Simon Glass
2014-02-18  9:43         ` Masahiro Yamada
2014-02-19  6:06           ` Simon Glass
2014-02-18 14:32       ` Tom Rini
2014-02-18 14:59         ` Michal Simek
2014-02-07 18:26     ` Scott Wood
2014-02-04  9:38 ` [U-Boot] [PATCH v2 3/3] dts: generate multiple device tree blobs Masahiro Yamada
2014-02-15 23:39   ` Simon Glass

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=CAPnjgZ19uBT3-5J5F+KTZJBmoWEndT4bq-6_AmZWwJYVH-b_EA@mail.gmail.com \
    --to=sjg@chromium.org \
    --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.