From: kraxel@redhat.com (Gerd Hoffmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESENT PATCH] ARM: bcm2835: Add devicetree for the Raspberry Pi 3, for arm (32)
Date: Wed, 01 Feb 2017 13:20:53 +0100 [thread overview]
Message-ID: <1485951653.1076.54.camel@redhat.com> (raw)
In-Reply-To: <1485944672.1076.50.camel@redhat.com>
> > 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.
Yep, dtbs_install fails:
[ ... ]
INSTALL arch/arm/boot/dts/bcm2835-rpi-b-plus.dtb
INSTALL arch/arm/boot/dts/bcm2835-rpi-a-plus.dtb
INSTALL arch/arm/boot/dts/bcm2836-rpi-2-b.dtb
INSTALL
cp: missing destination file operand after '/boot/dtbs/4.10.0-rc5+'
Try 'cp --help' for more information.
/root/linux/scripts/Makefile.dtbinst:41: recipe for target
'bcm2837-rpi-3-b.dts' failed
make[3]: *** [bcm2837-rpi-3-b.dts] Error 1
arch/arm/Makefile:348: recipe for target 'dtbs_install' failed
make[2]: *** [dtbs_install] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make: *** [__sub-make] Error 2
cheers,
Gerd
next prev parent reply other threads:[~2017-02-01 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 17:04 [RESENT PATCH] ARM: bcm2835: Add devicetree for the Raspberry Pi 3, for arm (32) Gerd Hoffmann
2017-01-21 18:42 ` Eric Anholt
2017-01-31 21:59 ` Eric Anholt
2017-02-01 10:24 ` Gerd Hoffmann
2017-02-01 12:20 ` Gerd Hoffmann [this message]
2017-02-02 8:37 ` Michael Zoran
2017-02-02 9:50 ` Stefan Wahren
2017-02-02 10:16 ` Michael Zoran
2017-02-08 22:40 ` Eric Anholt
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=1485951653.1076.54.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).