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 S1751291AbcFDVjf (ORCPT <rfc822;w@1wt.eu>);
	Sat, 4 Jun 2016 17:39:35 -0400
Received: from mout.kundenserver.de ([217.72.192.73]:62785 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750896AbcFDVjc (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 4 Jun 2016 17:39:32 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh+dt@kernel.org>, Gerd Hoffmann <kraxel@redhat.com>,
        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>,
        Scott Branden <sbranden@broadcom.com>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Kumar Gala <galak@codeaurora.org>, Will Deacon <will.deacon@arm.com>,
        Russell King <linux@armlinux.org.uk>,
        open list <linux-kernel@vger.kernel.org>,
        Eric Anholt <eric@anholt.net>, Pawel Moll <pawel.moll@arm.com>,
        linux-rpi-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
        "open list:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..." 
	<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v2 7/9] ARM: bcm2835: Add devicetree for the Raspberry Pi 3.
Date: Sat, 04 Jun 2016 23:39:30 +0200
Message-ID: <3356677.OOi30D5YDa@wuerfel>
User-Agent: KMail/5.1.3 (Linux/4.4.0-22-generic; KDE/5.18.0; x86_64; ; )
In-Reply-To: <CAL_JsqL2RgTLq9R3v4LDiV6Wa7totbzJBgmzVDgUv_keoS52vA@mail.gmail.com>
References: <1464934708-24769-1-git-send-email-kraxel@redhat.com> <1464950355.24775.143.camel@redhat.com> <CAL_JsqL2RgTLq9R3v4LDiV6Wa7totbzJBgmzVDgUv_keoS52vA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:tbu3AYWV0vaAoSu7qAiS1dZ9JJECD/B39svQRjN8i9ij/cJQNc4
 FoH5IBpPx6lZfoWbVdgz4N8T5uB40CH+M3SgVA58mEW3bVvVZ2rUMuKF6kHWcky510CZHxE
 lH27ImLEn8Mt52geJ6e+akfHt5yzrRNOUOanlFOKKZ94jjfGa5d8Te9lhgqwxTnf6MKoPJO
 DiCJGRBRiiDns9LElkcIA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:OkVbwDdVDTc=:H2pV4/2oz3E+t4Jk45MMWv
 B5e3zdZvokcULeAL55ApqBPjLOOkYPlSf1E5FZ7IGAnOKNN14cLQ07ttYCDshMgCis2EXmm/r
 oH2vHW/Pfa7BEpB5Tv5LTba1CBTV8sawKBkbqIGwjsS88qvW6yhfR9oCRi5V491o9jscLqMOK
 Uisfqs+wdpj63bSI9Y+edWcI2TsPyGX9364K2FkKfIXJAb13/+I5aPqzogprCrdg9sNzbrR17
 tMG/OhrZroLejZ2l0BxXDGl6ulibfWccT2Dh8Ek4PiiRSOhtGcUfkU6ygCcAYqT0YXuY7W+kZ
 OzqF36fM5ihXiZ8xsz68xzdDsFxYrf+bvMEvYFrEf8lpSbyRgmFgrIgSBH+syIObsBWXpMf/n
 TtYynrRaFqRixjnjyJYI61mLvZko0eGDwo43XQvsfsAp/r4A3jlnFrKcRkZ5wWMykZyhvRrTS
 pHzErZEmS0H3oGsqQknjUZnpOv+zwxbCMKvDZlXgpDiJIv0VfUc2N1+qEXd9J9EhnvYfM9BR0
 SAIi0HL2wgC6hLMkyEhGVFW5eooWdgJmHTtYa2SudCWUJgACucdxPk0bje+NFcCEbxcmbIj+X
 FPtJLeB1JeTElmttyZgeGt/iVZwhaRQ1gvzZSlKubYw6t/d42EdGGp5N/yPQZ+hxX8lrtCpj6
 6Oq4vSpEE+fTjtVoAJWR60wFCLK3btEPo4ZF8g1zB3gnx7h7gRbPUbMm9geB0oazqUrFHndYc
 C8IgL8H7/zkyHhpr
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Friday, June 3, 2016 11:17:51 AM CEST 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/.

I think having the dtb in $(objdir)arch/arm64/boot/dts/broadcom is fine, however
installing the  'make dtbs_install' rule copy it to
/boot/dts/../../../arm64/boot/dts/broadcom is not.

	Arnd