diff options
author | Matthijs Kooijman <matthijs@stdin.nl> | 2013-05-08 12:59:04 +0200 |
---|---|---|
committer | Michal Marek <mmarek@suse.cz> | 2013-05-23 10:14:34 +0200 |
commit | ad06156876c0e55a01e13e1f2dd5c7f9262b1dfa (patch) | |
tree | 772848743c8a7fc12fee4f40e7a3f994469bc7f1 /fs/char_dev.c | |
parent | f66ba560943ae21f5d1e505bad0a3591823b2b37 (diff) | |
download | blackbird-op-linux-ad06156876c0e55a01e13e1f2dd5c7f9262b1dfa.tar.gz blackbird-op-linux-ad06156876c0e55a01e13e1f2dd5c7f9262b1dfa.zip |
kbuild: Don't assume dts files live in arch/*/boot/dts
In commit b40b25ff (kbuild: always run gcc -E on *.dts, remove cmd_dtc_cpp),
dts building was changed to always use the C preprocessor. This meant
that the .dts file passed to dtc is not the original, but the
preprocessed one.
When compiling with a separate build directory (i.e., with O=), this
preprocessed file will not live in the same directory as the original.
When the .dts file includes .dtsi files, dtc will look for them in the
build directory, not in the source directory and compilation will fail.
The commit referenced above tried to fix this by passing arch/*/boot/dts
as an include path to dtc. However, for mips, the .dts files are not in
this directory, so dts compilation on mips breaks for some targets.
Instead of hardcoding this particular include path, this commit just
uses the directory of the .dts file that is being compiled, which
effectively restores the previous behaviour wrt includes. For most .dts
files, this path is just the same as the previous hardcoded
arch/*/boot/dts path.
This was tested on a mips (rt3052) and an arm (bcm2835) target.
Signed-off-by: Matthijs Kooijman <matthijs@stdin.nl>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'fs/char_dev.c')
0 files changed, 0 insertions, 0 deletions