From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752073AbcFFH2c (ORCPT <rfc822;w@1wt.eu>);
	Mon, 6 Jun 2016 03:28:32 -0400
Received: from mout.kundenserver.de ([217.72.192.73]:53697 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751755AbcFFH2a (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 6 Jun 2016 03:28:30 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Rob Herring <robh+dt@kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
        linux-rpi-kernel@lists.infradead.org,
        Mark Rutland <mark.rutland@arm.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Scott Branden <sbranden@broadcom.com>, Pawel Moll <pawel.moll@arm.com>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Ray Jui <rjui@broadcom.com>, Will Deacon <will.deacon@arm.com>,
        Russell King <linux@armlinux.org.uk>,
        open list <linux-kernel@vger.kernel.org>,
        Eric Anholt <eric@anholt.net>,
        "open list:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..." 
	<bcm-kernel-feedback-list@broadcom.com>,
        Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v2 7/9] ARM: bcm2835: Add devicetree for the Raspberry Pi 3.
Date: Mon, 06 Jun 2016 09:28:55 +0200
Message-ID: <3265668.gGTUMSyXWi@wuerfel>
User-Agent: KMail/5.1.3 (Linux/4.4.0-22-generic; KDE/5.18.0; x86_64; ; )
In-Reply-To: <1465197612.24775.190.camel@redhat.com>
References: <1464934708-24769-1-git-send-email-kraxel@redhat.com> <CAL_JsqL2RgTLq9R3v4LDiV6Wa7totbzJBgmzVDgUv_keoS52vA@mail.gmail.com> <1465197612.24775.190.camel@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:vHPXvfFBVW6i85/E1RBO2Ru1MS8BnZJjI5nCtTkAMVUjydoQIp9
 FmDLaIjWIXZQA+SVucSZAdr+vn9aeroFfsI2Y1fsbU6ZDKTuhNJbFQzGVsJ2v6V9JYf3Nxy
 r694spjkaqfRkaFmune3JDt+XOn2G0CHJGXjZ+N30Etw0yfrAM4oVwg5wr8Xamv2oAVOz5f
 ROqyvJfnAlgFOil1tmFsw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:/KB3PJeopFA=:Jj70N3BUaErGeDMDc1fKC7
 KRjMsVU5F8VTMsEs7wzepe1cHkI0EnMAiJa91ODzrvsa41TBSAxF+rUrwUR3SS13oa8BNr5tg
 yNt/oYbuTXMv/FUAada73k/I0Qqu5thDNLw3UNJ0ftPU7uQffdjt8wN72NyVes6aw14ubXJos
 XClTrO08v2fEZk1yJ4RVZqTnz+7yNjWeLwMnljO1zQMaENosudNIDKleH327QeTrpy/V7i1Of
 EEpOzBYYIbcBsMhEerZqJQm1lMzIVgY7Rphdw12nSOmE5CL8cm2X4SdnoFUn6S9Z/FXaRxayH
 EZz3OcBSYGDUaXvN1/SdTqQxw97N2skCdcYSHU+ZsU/iKLDWBWM7KbhGydK0MVUTIqcYATBIR
 SD+L05Tf8nifu88CvjTL0HRVIQCLo6A3kFq8ka9GQg2luzY9FAhVEKIrzIFjYXasczJ1YJEcz
 ZQCWl1mAA9imGKzfXtAYZ2iVBMRVK0ufDS4dxIp59zSz6hvB9oBZOxjn0wnwq4TB9b24nftLi
 letHrij/fDH9PvlQWF7s0ntRYyRbNKwEZPQbEqsRbpo3NGHlMTORrco2Njr7z+0AqFnB1Icl8
 qtDWWK/h+y0HSw27ZdpPwplXcJmK5eIIqFeg8/dDjy6A/0eZknpOLiX3xsFdcqAuDv6AdFOfv
 Bl6J0lXYALlmvHZL/4KlyIGyj5dlGQe3eUnLXDZ2T/ITDviNeqgvgEidbsYjuJecIi/eXelMh
 ivMGpxc7eEh6UaTx
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Monday, June 6, 2016 9:20:12 AM CEST Gerd Hoffmann wrote:
> On Fr, 2016-06-03 at 11:17 -0500, Rob Herring wrote:
> > On Fri, Jun 3, 2016 at 5:39 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > >   Hi,
> > >
> > >> I tried
> > >>
> > >> subdir-y += ../../../arm64/boot/dts/broadcom
> > >
> > > Hmm, works for me too now, probably had a typo somewhere.
> > 
> > What directory does the dtb end up in? Because as it was, it ended up
> > in arch/arm64/boot/dts/broadcom. I'm not sure all this hackery is
> > worth it if the dtb doesn't end up in arch/arm/boot/dts/.
> 
> With the 2/7 patch at the start of this subthread the dtb ends up in
> arch/arm64/boot/dts/broadcom for both arm and arm64 builds.
> 
> make "dtbs_install" places it in /boot/dtbs/$version/ for arm builds and
> in /boot/dtbs/$version/broadcom/ for arm64 builds.

Ok, let's stay with that for now then, and solve it better when we
need to do more of the same. Are you aware of any other boards using
bcm2837?

	Arnd