Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2893568pxb; Tue, 19 Jan 2021 08:32:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJy5lBV2JRfNcgo5PMuFDbF5fBSrP3BmC7Z0P+AV3KEdwrNccvX+fi01P2UVvD1rYPpMPNo5 X-Received: by 2002:a17:906:b215:: with SMTP id p21mr3435839ejz.407.1611073955165; Tue, 19 Jan 2021 08:32:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611073955; cv=none; d=google.com; s=arc-20160816; b=j7PjKyFiemKo2FB4W3ZnmkCuZk+3z1m6Q5ZlczPPhsfLD8tcZu1sVAxAqh9GUa3Ax4 7y3e6I0GnJ9MF0SquMU45gErI7FMikEdjBNJmdiYAmscqJePFxYKV1NzVlKAa2eJHi3r a8BRdzNjADxuYkIczLNHts8h3FxbCt9S1MJVhFD0vR3FTOrWeyWmMyGY2IOR60tT8hcl e6n1A+XE4CauWAakIrRUR3YkHdP2qNDmpEzGkkkHJfd5wHDhit0VI8Q3hsDw1UoAd7dp jxvAJCRRPCJ0hfs6l5A8ujYTgnIGxO0ZOvp5ew99ajIEHniBnRn3CwrvdGvoLLQvd/3u pzPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=EW8XrT7JtMKJbnFCv1YRnev1AQPs+Hl+bUMfJys3xoQ=; b=h2RpVVa6Be6d6vn3Xbl8hBpUmektvYndEYLGpw3sHGjdP/pJhfx8MsFPG+Ro4s1z1E CcQsE46qi5enrxFeJ/IRtU3gYt3Qm/Flhaj1I0jTw9J3E4ooDGiHqwfQ53FL1Mj4MDjc 13PXUOmJtALJago0C0HXp1M77tpJV3obXaTtDZghn196v6lsmSadojUHfUB91+wE72qr ZTecoGsnzQ6JjR2jKLSfK27fn+XVs22m0rZz+k5CzIXrOr9hqnB2cgxHdVr2c96ZkDN9 GyiVqyWDWSYAA3aIdKa8nOdluyJRc5Qqo6yGapbZQRz4txCzOMS6Y4KgDW/47ZDftdRQ kkrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=UZCzTkkj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g16si2915491edv.364.2021.01.19.08.32.11; Tue, 19 Jan 2021 08:32:35 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=UZCzTkkj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731977AbhASQ3D (ORCPT + 99 others); Tue, 19 Jan 2021 11:29:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50082 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731236AbhASQ2t (ORCPT ); Tue, 19 Jan 2021 11:28:49 -0500 Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9A95C061574; Tue, 19 Jan 2021 08:28:08 -0800 (PST) Received: by mail-qk1-x730.google.com with SMTP id 143so22335379qke.10; Tue, 19 Jan 2021 08:28:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=EW8XrT7JtMKJbnFCv1YRnev1AQPs+Hl+bUMfJys3xoQ=; b=UZCzTkkjsjT1pA7Mv+p6MiXPbtyHr40esKXDMjjQ1R6ykbEp/T3m//LtX1e11hiyT6 +Lve7769zBfr7HumVckVtxLJiuAIgdw5ITIRFkPxNFC9YiQuC7gEY7KSmurB02FgyEJj m6QcY9ssG+XskJvwK3j4fTrV5MzZp1FjQjowKY4aD/hIHja9QRuRLXZ+r/noRpGEcVLz c3wVXt/nyqqtAvNgbOeUGGHHWOgs5gAv7FZcxj08QPwAq8pHRb+iG7ENhrqF+rA6Pc6o r9O/wpbg+Cft0VBECoeh105uhM/PUNVW/Oik6EqlvTSeIh5IPzdTzh7/56X9GuDFlbL+ pOqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EW8XrT7JtMKJbnFCv1YRnev1AQPs+Hl+bUMfJys3xoQ=; b=tCXlSEjsS/mrqC//6501M/AUyk9g+Bp68uw45GfP0bVhaT+DdNEUR1+QHM4lzfseLq IVKD8ydPnVHCJzcPzJugqIYMJeCQTv3yWF5grtqWndcOPbZ+a5v0SluekMiH9cprsceP zrVfaLYRAS2xkkB1im7PzxK8qBi04xdWzYeRQaOMWB7oSwcLG64q4jgeMhigwIYVBUFs 75V8Z7M3wb+YQ7MVXDyK3gmxNUCZKRYHA2acV1Ex/V9KIcZDzL1qYgDgohIKSssNxEYW rxKpVOyhCWcl40/skxHr7ASNTHk8g0UuFOBnkIUykuQlQ+ZINDQk/mOnck8/jwyraFTQ t56Q== X-Gm-Message-State: AOAM530CfphrUvNvFuhJpHVQlxIpYJr4TrSnzh7abaRlsYK217iCzm21 bojEpBc4YIn3KQnr6m4wDYTQGX1EVgiu8g== X-Received: by 2002:a37:ad0d:: with SMTP id f13mr5119460qkm.355.1611073686981; Tue, 19 Jan 2021 08:28:06 -0800 (PST) Received: from [192.168.1.49] (c-67-187-90-124.hsd1.tn.comcast.net. [67.187.90.124]) by smtp.gmail.com with ESMTPSA id x25sm12963742qkx.88.2021.01.19.08.28.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Jan 2021 08:28:06 -0800 (PST) Subject: Re: [PATCH V2 2/2] scripts: dtc: Build fdtoverlay and fdtdump tools To: Viresh Kumar , Pantelis Antoniou , Rob Herring Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, Vincent Guittot , Bill Mills , anmar.oueja@linaro.org, Frank Rowand References: From: Frank Rowand Message-ID: <8e6395db-6ae4-f231-22fb-910eb2208477@gmail.com> Date: Tue, 19 Jan 2021 10:28:05 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/6/21 11:15 PM, Viresh Kumar wrote: > We will start building overlays for platforms soon in the kernel and > would need these tools going forward. Lets start building them. > > Signed-off-by: Viresh Kumar > --- > scripts/dtc/Makefile | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/scripts/dtc/Makefile b/scripts/dtc/Makefile > index 4852bf44e913..c607980a5c17 100644 > --- a/scripts/dtc/Makefile > +++ b/scripts/dtc/Makefile > @@ -1,12 +1,18 @@ > # SPDX-License-Identifier: GPL-2.0 > # scripts/dtc makefile > > -hostprogs-always-$(CONFIG_DTC) += dtc > +hostprogs-always-$(CONFIG_DTC) += dtc fdtdump fdtoverlay > hostprogs-always-$(CHECK_DT_BINDING) += dtc > > dtc-objs := dtc.o flattree.o fstree.o data.o livetree.o treesource.o \ > srcpos.o checks.o util.o > dtc-objs += dtc-lexer.lex.o dtc-parser.tab.o > +fdtdump-objs := fdtdump.o util.o > + # The upstream project builds libfdt as a separate library. We are choosing to # instead directly link the libfdt object files into fdtoverly > +libfdt_dir = libfdt > +libfdt-objs := fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o fdt_empty_tree.o fdt_addresses.o fdt_overlay.o > +libfdt = $(addprefix $(libfdt_dir)/,$(libfdt-objs)) > +fdtoverlay-objs := $(libfdt) fdtoverlay.o util.o > > # Source files need to get at the userspace version of libfdt_env.h to compile > HOST_EXTRACFLAGS += -I $(srctree)/$(src)/libfdt > In general, I am a proponent of using shared libraries (which the upstream project builds by default) because if a security bug in the library is fixed, it is fixed for all users of the library. In this specific case, I actually prefer the implementation that the patch provides (directly linking the library object files into fdtoverlay, which uses the library) because it is the only user of the library _and_ fdtoverlay will not inadvertently use the system wide libfdt if it happens to be installed (as it is on my system). Any thoughts on this Rob? -Frank