From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Fri, 21 Mar 2014 10:40:00 -0400 [thread overview]
Message-ID: <532C4F40.5010903@ti.com> (raw)
In-Reply-To: <53208CDD.7030106@ti.com>
On Wednesday 12 March 2014 12:35 PM, Santosh Shilimkar wrote:
> On Wednesday 12 March 2014 11:48 PM, Felipe Balbi wrote:
>> 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>
>> ---
>>
> We have been building dtbs with explicit command
> instead of dtbs since it was just one dtb so far
> supported. Was planning to add the rule once more
> boards get added. Now with Lamarr and Edision in
> for next merge window, will do that post 3.15-rc1.
>
Just to close the loop, I added a patch as part
of my 3.15 fixes which builds all keystone dt
blobs.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
To: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
Cc: linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux ARM Kernel Mailing List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Fri, 21 Mar 2014 10:40:00 -0400 [thread overview]
Message-ID: <532C4F40.5010903@ti.com> (raw)
In-Reply-To: <53208CDD.7030106-l0cyMroinI0@public.gmane.org>
On Wednesday 12 March 2014 12:35 PM, Santosh Shilimkar wrote:
> On Wednesday 12 March 2014 11:48 PM, Felipe Balbi wrote:
>> 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-l0cyMroinI0@public.gmane.org>
>> ---
>>
> We have been building dtbs with explicit command
> instead of dtbs since it was just one dtb so far
> supported. Was planning to add the rule once more
> boards get added. Now with Lamarr and Edision in
> for next merge window, will do that post 3.15-rc1.
>
Just to close the loop, I added a patch as part
of my 3.15 fixes which builds all keystone dt
blobs.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Felipe Balbi <balbi@ti.com>, <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>
Subject: Re: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Fri, 21 Mar 2014 10:40:00 -0400 [thread overview]
Message-ID: <532C4F40.5010903@ti.com> (raw)
In-Reply-To: <53208CDD.7030106@ti.com>
On Wednesday 12 March 2014 12:35 PM, Santosh Shilimkar wrote:
> On Wednesday 12 March 2014 11:48 PM, Felipe Balbi wrote:
>> 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>
>> ---
>>
> We have been building dtbs with explicit command
> instead of dtbs since it was just one dtb so far
> supported. Was planning to add the rule once more
> boards get added. Now with Lamarr and Edision in
> for next merge window, will do that post 3.15-rc1.
>
Just to close the loop, I added a patch as part
of my 3.15 fixes which builds all keystone dt
blobs.
Regards,
Santosh
next prev parent reply other threads:[~2014-03-21 14:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:48 [PATCH] arm: boot: dts: build keystone devicetree blob Felipe Balbi
2014-03-12 15:48 ` Felipe Balbi
2014-03-12 15:48 ` Felipe Balbi
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:53 ` Felipe Balbi
2014-03-12 16:53 ` Felipe Balbi
2014-03-12 16:53 ` Felipe Balbi
2014-03-21 14:40 ` Santosh Shilimkar [this message]
2014-03-21 14:40 ` Santosh Shilimkar
2014-03-21 14:40 ` Santosh Shilimkar
2014-03-21 14:43 ` Felipe Balbi
2014-03-21 14:43 ` Felipe Balbi
2014-03-21 14:43 ` Felipe Balbi
2014-03-25 13:21 ` Santosh Shilimkar
2014-03-25 13:21 ` Santosh Shilimkar
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=532C4F40.5010903@ti.com \
--to=santosh.shilimkar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.