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 [thread overview]
Message-ID: <3356677.OOi30D5YDa@wuerfel> (raw)
In-Reply-To: <CAL_JsqL2RgTLq9R3v4LDiV6Wa7totbzJBgmzVDgUv_keoS52vA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-06-04 21:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464934708-24769-1-git-send-email-kraxel@redhat.com>
2016-06-03 6:18 ` [PATCH v2 1/9] pinctrl: walk into bcm subdir unconditionally Gerd Hoffmann
2016-06-08 8:12 ` Linus Walleij
2016-06-10 0:16 ` Eric Anholt
2016-06-13 7:26 ` Linus Walleij
2016-06-14 17:37 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 2/9] irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 3/9] arm64: Allow for different DMA and CPU bus offsets Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 4/9] arm64: Add platform selection for BCM2835 Gerd Hoffmann
2016-06-03 11:27 ` Catalin Marinas
2016-06-04 19:55 ` Eric Anholt
2016-06-08 9:12 ` Catalin Marinas
2016-06-10 0:21 ` Eric Anholt
2016-06-10 9:56 ` Catalin Marinas
2016-06-15 6:48 ` Eric Anholt
2016-06-15 8:07 ` Catalin Marinas
2016-06-15 21:57 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 5/9] arm64: Add BCM2835 support to the defconfig Gerd Hoffmann
2016-06-03 7:36 ` Arnd Bergmann
2016-06-03 8:50 ` Gerd Hoffmann
2016-06-03 8:58 ` Arnd Bergmann
2016-06-03 9:53 ` Gerd Hoffmann
2016-06-07 22:16 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 6/9] dt-bindings: Add root properties for Raspberry Pi 3 Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 7/9] ARM: bcm2835: Add devicetree for the " Gerd Hoffmann
2016-06-03 7:38 ` Arnd Bergmann
2016-06-03 8:45 ` Gerd Hoffmann
2016-06-03 8:55 ` Arnd Bergmann
2016-06-03 10:39 ` Gerd Hoffmann
2016-06-03 11:15 ` Arnd Bergmann
2016-06-03 16:17 ` Rob Herring
2016-06-04 21:39 ` Arnd Bergmann [this message]
2016-06-06 7:20 ` Gerd Hoffmann
2016-06-06 7:28 ` Arnd Bergmann
2016-06-06 7:47 ` Gerd Hoffmann
2016-06-03 9:04 ` Stefan Wahren
2016-06-03 6:18 ` [PATCH v2 8/9] ARM: bcm2835: dt: Add the ethernet to the device trees Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 9/9] ARM: bcm2837: " Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3356677.OOi30D5YDa@wuerfel \
--to=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).