Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] dtc: add patches for raspberry pi overlay support
Date: Mon, 12 Jan 2015 21:50:52 +0100	[thread overview]
Message-ID: <20150112215052.48005c8d@free-electrons.com> (raw)
In-Reply-To: <1421000166-24963-4-git-send-email-ps.report@gmx.net>

Dear Peter Seiderer,

On Sun, 11 Jan 2015 19:16:06 +0100, Peter Seiderer wrote:
> See [1] for documentation of raspberry pi kernel dt overlay support.
> 
> The following patches (see original download urls) where adjusted to dtc-1.4.1:
> 
> - 0003-dtc-Dynamic-symbols-fixup-support.patch
> https://github.com/RobertCNelson/dtc/commit/dd6a0533e846e8d5e690a618fa35cc15a6103efb.patch
> 
> - 0004-dtc-v-takes-no-argument-drop-extra.patch
> https://github.com/RobertCNelson/dtc/commit/f345d9e48c9e1169edf047de742da142cc5687bc.patch
> 
> [1] https://github.com/raspberrypi/documentation/blob/master/configuration/device-tree.md
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  .../0003-dtc-Dynamic-symbols-fixup-support.patch   | 581 +++++++++++++++++++++
>  .../0004-dtc-v-takes-no-argument-drop-extra.patch  |  44 ++
>  2 files changed, 625 insertions(+)
>  create mode 100644 package/dtc/0003-dtc-Dynamic-symbols-fixup-support.patch
>  create mode 100644 package/dtc/0004-dtc-v-takes-no-argument-drop-extra.patch

We normally don't really like to include patches adding new features:
those should be included upstream first. However, for the case of the
DT overlay mechanism, it's now being more and more widely used for the
BeagleBone Black and the Raspberry Pi, so maybe we should make an
exception for this.

Opinion of other Buildroot developers on this is welcome.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-01-12 20:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 18:16 [Buildroot] [PATCH v2 1/4] dtc: fix project and download url Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 2/4] dtc: bump version to 1.4.1 Peter Seiderer
2015-01-12 20:07   ` Thomas Petazzoni
2015-01-12 22:13     ` Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 3/4] dtc: add host build Peter Seiderer
2015-01-12 20:42   ` Thomas Petazzoni
2015-01-12 22:31     ` Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 4/4] dtc: add patches for raspberry pi overlay support Peter Seiderer
2015-01-12 13:57   ` Matthew Weber
2015-01-12 16:01     ` Peter Seiderer
2015-01-12 20:50   ` Thomas Petazzoni [this message]
2015-01-12 22:39     ` Peter Seiderer
2015-01-12 20:39 ` [Buildroot] [PATCH v2 1/4] dtc: fix project and download url Thomas Petazzoni
2015-01-12 22:15   ` Peter Seiderer

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=20150112215052.48005c8d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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