From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Rowand Subject: Re: case sensitivity for devicetree node names Date: Sun, 12 Jun 2016 11:39:37 -0700 Message-ID: <575DAC69.5010804@gmail.com> References: <575B1D84.2010703@gmail.com> <575C68A1.1020701@gmail.com> <1465682743.19533.18.camel@kernel.crashing.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=7mNz6VDY7Tc9KjOYVWHZh8hQrZV8Pl2RiOgN46kQ7g0=; b=PPQn4ScGqUz9xAOJTQOSpt8O0swZcDsVr/kaP84AVO/4GV69ZmP8AeIuj4XJFhj241 ONG9Nt+GvwbWkGenHy18aeFsylnsGZMf0RFrDWzel99hIsVTXByj/Fz32HW/skiJ3ur/ bsTjaZDYmF20u+v4OlZZ+gF5+Ip4k8IHyh9RsVQQwJr2ut1QnLqSZv71FAWJqgiNaGQw 6A/0ZS9WfK7ldqglqXYDtfcr5IIB2F2JJLd7BQw7rawdpltRcsycg4Lh9OthHjhbWDo4 i3JPOvuWBrVcompDyjaveB1ta4RNYrK+dAMFvbq7lCdNkWf9vTkl06SpGKf9Q0uDq6xI aXhA== In-Reply-To: <1465682743.19533.18.camel-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org> Sender: devicetree-spec-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Benjamin Herrenschmidt Cc: Rob Herring , Grant Likely , David Gibson , "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Paul Mackerras , Michael Ellerman , linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org On 06/11/16 15:05, Benjamin Herrenschmidt wrote: > On Sat, 2016-06-11 at 12:38 -0700, Frank Rowand wrote: >> I chased through the history and found a 2.6.0-test5 announcement >> which noted the patch from you which adds: >> >> of_find_node_by_path() >> of_find_node_by_name() >> of_find_node_by_type() >> of_find_compatible_node() >> >> (And the patch is commit 394edd852a14 in the git recreation >> of bitkeeper days, which is found at >> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git) >> >> That version of the functions uses a case insensitive compare for >> devicetree node names. >> >> Do you remember why you chose to not use a case sensitive compare? > >>>From memory, there were inconsistency in case on various earlier > machines (notably old macs). I think that's the main reason. > > Cheers, > Ben. Is there a kernel config option (or a small set of config options) that would identify the affected machines? It would be ok if the option(s) also included some non-affected machines. That way we could use the case insensitive compare for a small set of machines.