On 11/18/2013 11:38 AM, Jason Cooper wrote:
> Unlike other build products in the Linux kernel, the devicetree blobs
> are simply the name of their source file, s/dts/dtb/. There is also no
> 'make *install' mechanism to put them in a standard place with a
> standard naming structure.
>
> Unfortunately, users have begun scripting pulling the needed dtbs from
> within the kernel tree, thus hardcoding the dtbs names. In turn, this
> means any changes to the dts filenames breaks these scripts.
>
> This patch is an attempt to fix this problem. Akin to 'make install',
> this creates a new make target, dtbs_install. The script that gets
> called defers to a vendor or distribution supplied installdtbs binary,
> if found in the system. Otherwise, the default action is to install a
> given dtb into
>
> /lib/modules/${kernel_version}/devicetree/${board_compat}.dtb
Is co-mingling the DTs in the same (top-level) directory as modules a
good idea. I guess there is an explicit devicetree/ sub-directory so
they're easy to pull out of the source tree, but even so, they're
certainly not modules. I would assume that distros would put them into
e.g. /boot/dtbs/${kernelversion} or something more like that. Would it
make sense for the install target to use a path more like that, or
perhaps at least /dtbs/${kernelversion} to keep it separate from modules?
Sorry for the bikeshedding.
> diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> +dtbs_install: dtbs
> + $(CONFIG_SHELL) $(srctree)/$(boot)/installdtbs.sh $(KERNELRELEASE) \
> + "$(MODLIB)/devicetree" "$(srctree)/$(boot)/dts"
Architectures besides ARM use device trees. Shouldn't "make
dtbs_install" work for them too?
> diff --git a/arch/arm/boot/installdtbs.sh b/arch/arm/boot/installdtbs.sh
> +for dtb in `find "$3" -name "*.dtb"`; do
> + # we use dtc to parse the dtb, get the board compatible string,
> + # and then copy the dtb to $2/${board_compatible}.dtb
> + compat="`$DTC -I dtb -O compat "$dtb"`"
> +
> + if [ -e "$2/${compat}.dtb" ]; then
> + echo "Install $dtb: $2/${compat}.dtb already exists!" 1>&2
> + exit 1
> + else
> + cp "$dtb" "$2/${compat}.dtb"
> + fi
> +done
This only appears to create ${compat}.dtb, and not ${dtb} too. So, it
doesn't seem to address part of the cover letter, "In addition, some
vendors have done a diligent job naming their devicetree source files
appropriately and we don't want to break their setups." Was that
deliberate? If so, I guess I need to send some patches to U-Boot.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
