From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] Rework support for the device tree
Date: Fri, 27 Jul 2012 21:45:14 +0200 [thread overview]
Message-ID: <5012EFCA.2080809@mind.be> (raw)
In-Reply-To: <1342528042-10038-3-git-send-email-maxime.ripard@free-electrons.com>
On 07/17/12 14:27, Maxime Ripard wrote:
> This patch introduces some support for device tree-enabled kernels.
>
> It replaces the former BR2_LINUX_KERNEL_DTS_FILE option that was
> microblaze-only, that was quite limited. This option was quite
> limited, first obviously because it was restricted to microblaze,
> but also because it targetted only external device tree source files,
> and allowed only to build simpleImages using the custom image name
> mechanism.
>
> This patch adds a much more generic one, that can work on basically
> every architecture that supports device tree. It allows to build
> both device tree source file that comes with the kernel source or to
> set the path to the device tree file to use so that one can use a
> custom device tree.
>
> Signed-off-by: Maxime Ripard<maxime.ripard@free-electrons.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Really nice!
The BR2_LINUX_KERNEL_DTB_IS_SELF_BUILT part actually belongs to
patch 4/6, but that's a minor detail.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-07-27 19:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 12:27 [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 1/6] Revert "Microblaze: build kernel with device tree" Maxime Ripard
[not found] ` <CAEBucnCan1vRHv4GkhYXGHnrb3Nrtg0rOtwiLY_fTuARuV0W2g@mail.gmail.com>
2012-07-18 7:23 ` Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 2/6] Rework support for the device tree Maxime Ripard
2012-07-27 19:45 ` Arnout Vandecappelle [this message]
2012-07-17 12:27 ` [Buildroot] [PATCH 3/6] Factorize the u-boot images code Maxime Ripard
2012-07-28 14:36 ` Arnout Vandecappelle
2012-07-17 12:27 ` [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm Maxime Ripard
2012-07-28 14:49 ` Arnout Vandecappelle
2012-07-28 19:29 ` Thomas Petazzoni
2012-07-29 15:16 ` Arnout Vandecappelle
2012-07-30 8:25 ` Fabio Porcedda
2012-07-30 8:31 ` Thomas Petazzoni
2012-07-30 10:10 ` Fabio Porcedda
2012-07-17 12:27 ` [Buildroot] [PATCH 5/6] Add cuImage(powerpc) and simpleImage(microblaze) as Linux kernel images variants Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 6/6] Update s6lx9 microblaze default configuration Maxime Ripard
2012-07-27 16:06 ` [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Fabio Porcedda
2012-07-27 18:59 ` Maxime Ripard
2012-07-30 8:33 ` Fabio Porcedda
2012-07-30 9:38 ` Maxime Ripard
2012-07-30 10:09 ` Fabio Porcedda
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 12:32 [Buildroot] [PATCHv4 " Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 2/6] Rework support for the device tree Maxime Ripard
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=5012EFCA.2080809@mind.be \
--to=arnout@mind.be \
--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