From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41wmds20z6zF0gv for ; Thu, 23 Aug 2018 11:14:09 +1000 (AEST) Message-ID: <3335cff2cc999c1dda58d75949ab3d12185fca79.camel@kernel.crashing.org> Subject: Re: DT case sensitivity From: Benjamin Herrenschmidt To: Rob Herring , Stephen Rothwell , Grant Likely , Michael Ellerman , Kumar Gala , David Gibson , Frank Rowand , devicetree-spec@vger.kernel.org, devicetree@vger.kernel.org, linuxppc-dev Date: Thu, 23 Aug 2018 11:03:28 +1000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2018-08-22 at 19:47 -0500, Rob Herring wrote: > The default DT string handling in the kernel is node names and > compatibles are case insensitive and property names are case sensitive > (Sparc is the the only variation and is opposite). It seems only PPC > (and perhaps only Power Macs?) needs to support case insensitive > comparisons. It was probably a mistake to follow PPC for new arches > and we should have made everything case sensitive from the start. So I > have a few questions for the DT historians. :) Open Firmware itself is insensitive. > What PPC systems are case insensitive? Can we limit that to certain systems? All PowerMacs at least, the problem is that I don't have DT images or access to all the historical systems (and yes some people occasionally still use them) to properly test a change in that area. > AFAICT, dtc at least (if not anything FDT based) has always been case > sensitive at least for node and property names. I'm not sure about > compatible strings? > > Anyone see potential issues with switching all platforms except PPC > and Sparc to case sensitive comparisons? Cheers, Ben.