From: Felipe Balbi <balbi@ti.com>
To: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>
Cc: <linux@arm.linux.org.uk>, <devicetree@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Felipe Balbi <balbi@ti.com>
Subject: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Wed, 12 Mar 2014 10:48:50 -0500 [thread overview]
Message-ID: <1394639330-1288-1-git-send-email-balbi@ti.com> (raw)
Currently, even when building keystone only
kernel builds, DTB won't get build because
we lack a Makefile rule to get it compiled.
This patch adds that rule so mainline kernel
users have a chance to use up-to-date DTB on
keystone 2 platforms.
Signed-off-by: Felipe Balbi <balbi@ti.com>
---
note that I just tried this on top of linux-next
(commit 69d5cdda16b3c9767b82d80b07edb9bb056448e3)
and, even though dtb builds fine, I still couldn't
get keystone_defconfig uImage to boot fine.
It's probably my LOADADDR which is wrong.
Santosh, what's the LOADADDR I should be using
for keystone boots ?
arch/arm/boot/dts/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index ae208a6..52c5231 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -82,6 +82,7 @@ dtb-$(CONFIG_ARCH_HIGHBANK) += highbank.dtb \
ecx-2000.dtb
dtb-$(CONFIG_ARCH_INTEGRATOR) += integratorap.dtb \
integratorcp.dtb
+dtb-$(CONFIG_ARCH_KEYSTONE) += k2hk-evm.dtb
kirkwood := \
kirkwood-b3.dtb \
kirkwood-cloudbox.dtb \
--
1.9.0.167.g384364b
next reply other threads:[~2014-03-12 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:48 Felipe Balbi [this message]
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:53 ` Felipe Balbi
2014-03-21 14:40 ` Santosh Shilimkar
2014-03-21 14:43 ` Felipe Balbi
2014-03-25 13:21 ` Santosh Shilimkar
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=1394639330-1288-1-git-send-email-balbi@ti.com \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.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
all inboxes | Powered by JetHome®