From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot.dtb vs. dts/dt.dtb output filename, also O= vs BUILD_DIR=
Date: Mon, 24 Feb 2014 10:44:04 -0700 [thread overview]
Message-ID: <530B84E4.1080006@wwwdotorg.org> (raw)
Masahiro,
Prior the to kbuild conversion, U-Boot used to produce file u-boot.dtb
in the root of the object tree. Now it doesn't, but I think puts the
same file in dts/dt.dtb instead. Was this a deliberate change?
We have some flashing utilities that build U-Boot, then copy this result
file. This utility no longer works because the file it's looking for no
longer exists. I'd rather fix the U-Boot build process so its output
filenames don't change, than fix the utility to look for a variety of
different output filenames. Are you OK with a patch reverting the output
filename change?
Related, I also found that pre-Kbuild, I could "make BUILD_DIR=...", but
now I have to "make O=...". That's also an external change in behaviour.
Was that intentional?
next reply other threads:[~2014-02-24 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:44 Stephen Warren [this message]
2014-02-24 19:58 ` [U-Boot] u-boot.dtb vs. dts/dt.dtb output filename, also O= vs BUILD_DIR= Tom Rini
2014-02-25 0:38 ` Masahiro Yamada
2014-02-25 18:19 ` Stephen Warren
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=530B84E4.1080006@wwwdotorg.org \
--to=swarren@wwwdotorg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox