From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Tue, 03 Dec 2013 10:37:28 -0700 Subject: [PATCH V6] kbuild: dtbs_install: new make target In-Reply-To: <1385942188-21831-1-git-send-email-jason@lakedaemon.net> References: <1384201760-16785-1-git-send-email-jason@lakedaemon.net> <1385942188-21831-1-git-send-email-jason@lakedaemon.net> Message-ID: <529E16D8.3060608@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 12/01/2013 04:56 PM, Jason Cooper wrote: > Unlike other build products in the Linux kernel, there is no 'make > *install' mechanism to put devicetree blobs in a standard place. > > 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 distribution or user supplied installdtbs binary, > if found in the system. Otherwise, the default action is to install the > built dtbs into > > /lib/devicetrees/${kernel_version}/${dts_filename}.dtb > > This is done to keep dtbs from different kernel versions separate until > things have settled down. Once the dtbs are stable, and not so strongly > linked to the kernel version, the devicetree files will most likely move > to their own repo. Users will need to upgrade install scripts at that > time. > > /lib has been selected over /boot since /boot is often a FAT filesystem > and a majority of the dts filenames are longer than 8+3. > > Signed-off-by: Jason Cooper > --- > Note: Stephen, I haven't added your Ack because I wanted to make sure you were > Ok with the change to /lib in light of /boot partitions formatted to FAT This script shouldn't be installing directly to the filesystem, but rather some staging area that then gets copied to the desired location by distro-/use-specific scripts. As such, the filesystem in /boot isn't relevant. But that said, I won't try and NAK it because of that. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH V6] kbuild: dtbs_install: new make target Date: Tue, 03 Dec 2013 10:37:28 -0700 Message-ID: <529E16D8.3060608@wwwdotorg.org> References: <1384201760-16785-1-git-send-email-jason@lakedaemon.net> <1385942188-21831-1-git-send-email-jason@lakedaemon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1385942188-21831-1-git-send-email-jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jason Cooper , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Olof Johansson Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org On 12/01/2013 04:56 PM, Jason Cooper wrote: > Unlike other build products in the Linux kernel, there is no 'make > *install' mechanism to put devicetree blobs in a standard place. > > 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 distribution or user supplied installdtbs binary, > if found in the system. Otherwise, the default action is to install the > built dtbs into > > /lib/devicetrees/${kernel_version}/${dts_filename}.dtb > > This is done to keep dtbs from different kernel versions separate until > things have settled down. Once the dtbs are stable, and not so strongly > linked to the kernel version, the devicetree files will most likely move > to their own repo. Users will need to upgrade install scripts at that > time. > > /lib has been selected over /boot since /boot is often a FAT filesystem > and a majority of the dts filenames are longer than 8+3. > > Signed-off-by: Jason Cooper > --- > Note: Stephen, I haven't added your Ack because I wanted to make sure you were > Ok with the change to /lib in light of /boot partitions formatted to FAT This script shouldn't be installing directly to the filesystem, but rather some staging area that then gets copied to the desired location by distro-/use-specific scripts. As such, the filesystem in /boot isn't relevant. But that said, I won't try and NAK it because of that. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html