Received: by 10.223.185.116 with SMTP id b49csp5477365wrg; Wed, 7 Mar 2018 12:26:46 -0800 (PST) X-Google-Smtp-Source: AG47ELuzVSnZhKih1E1RUW4l3DB4PDmGywDSeZBSKoKWkB0xfUboQbbqBgT3MYk+ukglcAfjF7x8 X-Received: by 10.98.189.24 with SMTP id a24mr18804317pff.125.1520454406002; Wed, 07 Mar 2018 12:26:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520454405; cv=none; d=google.com; s=arc-20160816; b=MQVG6kuw/Vhq1PCfXrB95nXf7x5hb3PUnJ3cAj5Xc206bWB6DncypAYKMMB/9R1aEo wfGySdfdfawAfhrRz3Khtd4ggvhDUjsdYMfrlQrtDqNipFLZKLeKsqfBvz3wZOTm3sSU aeneaaqbejEklMOnZI6hS+IEI0kYeQbQW0duziLH5XhN/qoL9Wm+rjmhbV2jNmJMfnZT bdcDtEC3XR1SRYC5wGqKa7BCcyn/uJfH46dZ7BwdcicP4HY0gDUzVxR65y3fhPiN1QdC C4KorDR0n3EcNygzhcU1R3eKlzruyo2sjb4UtrZIOwF417WIW8AQ8RwJBgvDgNrdRyeo duEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:arc-authentication-results; bh=ph+NdbTJbCLJYDlz/vRGYZw9EfyefBk9lhqUG+U8zYI=; b=oz6tuU4WbHDix4RrwoVQHTvFMhQt8PfbcePRqQA1VtxYGzQBJNdI1mGY6BocpMmeY+ 0l6GNLW3xkoaqQ9VOI4dHSmyyU8KjE8eTGf4ir9LXJ77ioXnc8yjds4NAAZOchLikW3X oXDo+YFk/GPZuHUE+84O9ZNP8qMOLz29XYh/QqBsjDy1w7QVRRUWxz6/i2Yyjb2TUHws XYkrYd+Sx92POjREidDPZMGF0MvwYExiB4kWvDxAsD67W8XL1ma3EhwkkI3Bnts27pgd KXzPuSoBmS4UW+flY0xYMnJOabxAP8KNPnEUkq6qQWpxFMOYuNZHNNXs4BgDXKV31P99 lXrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q11si14472503pfi.35.2018.03.07.12.26.31; Wed, 07 Mar 2018 12:26:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965031AbeCGUZ0 (ORCPT + 99 others); Wed, 7 Mar 2018 15:25:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:56812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964922AbeCGUZY (ORCPT ); Wed, 7 Mar 2018 15:25:24 -0500 Received: from saruman (jahogan.plus.com [212.159.75.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C51AA2172D; Wed, 7 Mar 2018 20:25:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C51AA2172D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=jhogan@kernel.org Date: Wed, 7 Mar 2018 20:25:14 +0000 From: James Hogan To: Frank Rowand Cc: linux-kbuild@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Masahiro Yamada , Michal Marek , Ralf Baechle , Florian Fainelli , Kevin Cernekee , linux-mips@linux-mips.org, stable@vger.kernel.org Subject: Re: [PATCH] kbuild: Handle builtin dtb files containing hyphens Message-ID: <20180307202511.GT4197@saruman> References: <20180307140633.26182-1-jhogan@kernel.org> <7ecea7ca-2931-16bc-a110-1ecdaf17f0f2@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ck3np9Ek/EMsFxRu" Content-Disposition: inline In-Reply-To: <7ecea7ca-2931-16bc-a110-1ecdaf17f0f2@gmail.com> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ck3np9Ek/EMsFxRu Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 07, 2018 at 12:11:41PM -0800, Frank Rowand wrote: > I initially misread the patch description (and imagined an entirely > different problem). >=20 >=20 > On 03/07/18 06:06, James Hogan wrote: > > On dtb files which contain hyphens, the dt_S_dtb command to build the> = dtb.S files (which allow DTB files to be built into the kernel) results> in= errors like the following:> > bcm3368-netgear-cvg834g.dtb.S: Assembler mes= sages:> bcm3368-netgear-cvg834g.dtb.S:5: Error: : no such section> bcm3368-= netgear-cvg834g.dtb.S:5: Error: junk at end of line, first unrecognized cha= racter is `-'> bcm3368-netgear-cvg834g.dtb.S:6: Error: unrecognized opcode = `__dtb_bcm3368-netgear-cvg834g_begin:'> bcm3368-netgear-cvg834g.dtb.S:8: Er= ror: unrecognized opcode `__dtb_bcm3368-netgear-cvg834g_end:'> bcm3368-netg= ear-cvg834g.dtb.S:9: Error: : no such section> bcm3368-netgear-cvg834g.dtb.= S:9: Error: junk at end of line, first unrecognized character is `-' > Please replace the following section: >=20 > > This is due to the hyphen being used in symbol names. Replace all > > hyphens=20 > > with underscores in the dt_S_dtb command to avoid this problem. > >=20 > > Quite a lot of dts files have hyphens, but its only a problem on MIPS > > where such files can be built into the kernel. For example when > > CONFIG_DT_NETGEAR_CVG834G=3Dy, or on BMIPS kernels when the dtbs target= is > > used (in the latter case it admitedly shouldn't really build all the > > dtb.o files, but thats a separate issue). >=20 > with: >=20 > cmd_dt_S_dtb constructs the assembly source to incorporate a devicetree > FDT (that is, the .dtb file) as binary data in the kernel image. > This assembly source contains labels before and after the binary data. > The label names incorporate the file name of the corresponding .dtb > file. Hyphens are not legal characters in labels, so transform all > hyphens from the file name to underscores when constructing the labels. Thanks, that is clearer. I'll keep the paragraph about MIPS and the example configuration though, as I think its important information to reproduce the problem, and to justify why it wouldn't be appropriate to just rename the files (which was my first reaction). > Reviewed-by: Frank Rowand Thanks James --ck3np9Ek/EMsFxRu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEd80NauSabkiESfLYbAtpk944dnoFAlqgSqEACgkQbAtpk944 dno+qg/+OVG/O0znyZup1R3l0Cs07bQYye+qoIv2byyBKi2HJtRKIRA/9oUww8L6 b0/aBIY0NpayhhsC0/EziivmKMwTF1aQROnbN5AS1Z1B+vVnFX38jw2yc7C0RMd3 bezjC4/qxZ3Tt5Q24ITliAc8IS36fo7448F1nCRhjqHkF4wOEmZ8GzGYY7SoOIaf u1NS/Cjl/gwEGN6XlLVVY7S6pdtNYYjOSS04UWTPBYsjqESLznkHYDeHvoS2kpsf HOnVTAqYv5Vv03iA3g+Rfse6sOuzIA9cL79Y7y7RQgbh/eqtXQzXbYdOrboFr7ZI cUn0p2YLSQvpbJe4wuXndmkJGotJIomhsgFZGs1B3FEyE1Hg7f/PIRzp3MTXnbDd pvDKQ7Y3n9K0dm4XIKcp0b3BH7sLNuxOnb2l/DVbf9uSLtcnfSbRyNDwGlqqHyEH JHvyo5odx80kL5+0w74ABX5hDOuK7bPqhF8slID+xv8zsnAt2vMIkVqx2TmIYqBo GL6RJI3xZPZk/oDA+rN3zw4TssFdQ5JBOs9B3q3iAtkGqd0/CIKMj4P5IItxqw2E tnucDBhc0cvbNCYpWw5X6wCiMzhhM8MdVTxnGvzKn/DAk+EWnGh6dfgvoY/Sl3r5 O3g7tS2zfrFqvdm6Wecbro58Mzs+WcctRqK2h2LTXorEjBIRjig= =+//s -----END PGP SIGNATURE----- --ck3np9Ek/EMsFxRu--