[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1485944672.1076.50.camel@redhat.com>
Date: Wed, 01 Feb 2017 11:24:32 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Eric Anholt <eric@...olt.net>
Cc: linux-rpi-kernel@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"moderated list:ARM PORT" <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RESENT PATCH] ARM: bcm2835: Add devicetree for the Raspberry
Pi 3, for arm (32)
> >> - bcm2835-rpi-zero.dtb
> >> + bcm2835-rpi-zero.dtb \
> >> + ../../../arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dtb
> Unfortunately, I just remembered yesterday that one of the requirements
> is that we not use these sorts of ../../../ references in the DT tree.
> Instead we have to use symlinks -- see arch/arm64/boot/dts/broadcom/ for
> how we did the last round of this.
Yes, we did that with the *.dtsi include files.
Not fully sure this is a requirement for the Makefile too.
> I think just having links from
> arch/arm64/boot/dts/broadcom/bcm2837*.dts* to arch/arm/boot/dts/ would
> be the solution, then this Makefile could just reference
> bcm2837-rpi-3-b.dtb.
I suspect it is not that easy, last time I tried it didn't work.
Will try again though.
cheers,
Gerd
Powered by blists - more mailing lists