xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir@xen.org>, David Vrabel <david.vrabel@citrix.com>
Subject: [PATCH 3/8] libfdt: add to build
Date: Mon, 13 Feb 2012 13:18:46 +0000	[thread overview]
Message-ID: <1329139131-27554-4-git-send-email-david.vrabel@citrix.com> (raw)
In-Reply-To: <1329139131-27554-1-git-send-email-david.vrabel@citrix.com>

From: David Vrabel <david.vrabel@citrix.com>

Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Acked-by: Tim Deegan <tim@xen.org>
Cc: Keir Fraser <keir@xen.org>
---
 xen/arch/arm/Rules.mk      |    2 ++
 xen/common/Makefile        |    1 +
 xen/common/libfdt/Makefile |    5 +++++
 3 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 xen/common/libfdt/Makefile

diff --git a/xen/arch/arm/Rules.mk b/xen/arch/arm/Rules.mk
index 336e209..14082dd 100644
--- a/xen/arch/arm/Rules.mk
+++ b/xen/arch/arm/Rules.mk
@@ -6,6 +6,8 @@
 # 'make clean' before rebuilding.
 #
 
+HAS_DEVICE_TREE := y
+
 CFLAGS += -fno-builtin -fno-common -Wredundant-decls
 CFLAGS += -iwithprefix include -Werror -Wno-pointer-arith -pipe
 CFLAGS += -I$(BASEDIR)/include
diff --git a/xen/common/Makefile b/xen/common/Makefile
index 9249845..4b1e6f2 100644
--- a/xen/common/Makefile
+++ b/xen/common/Makefile
@@ -59,3 +59,4 @@ subdir-$(x86_64) += hvm
 subdir-$(ia64) += hvm
 
 subdir-y += libelf
+subdir-$(HAS_DEVICE_TREE) += libfdt
diff --git a/xen/common/libfdt/Makefile b/xen/common/libfdt/Makefile
new file mode 100644
index 0000000..0e65bc0
--- /dev/null
+++ b/xen/common/libfdt/Makefile
@@ -0,0 +1,5 @@
+include Makefile.libfdt
+
+obj-y += $(LIBFDT_OBJS)
+
+CFLAGS += -I.
-- 
1.7.2.5

  parent reply	other threads:[~2012-02-13 13:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 13:18 [PATCH 0/8] arm: initial device tree support (#3) David Vrabel
2012-02-13 13:18 ` [PATCH 1/8] libfdt: add version 1.3.0 David Vrabel
2012-02-13 13:18 ` [PATCH 2/8] libfdt: fixup libfdt_env.h for xen David Vrabel
2012-02-13 13:18 ` David Vrabel [this message]
2012-02-13 13:18 ` [PATCH 4/8] arm: link a device tree blob into the xen image David Vrabel
2012-02-17 17:13   ` Ian Campbell
2012-02-17 17:22     ` David Vrabel
2012-02-20 17:20       ` Ian Campbell
2012-02-22 14:34         ` Ian Campbell
2012-02-13 13:18 ` [PATCH 5/8] arm: map device tree blob in initial page tables David Vrabel
2012-02-13 13:18 ` [PATCH 6/8] arm: add early_printk() David Vrabel
2012-02-13 13:18 ` [PATCH 7/8] arm, device tree: parse the DTB for RAM location and size David Vrabel
2012-02-13 14:51   ` Ian Campbell
2012-02-13 15:46     ` David Vrabel
2012-02-13 16:53       ` Ian Campbell
2012-02-13 17:41         ` Ian Jackson
2012-03-14 10:53           ` Ian Campbell
2012-02-13 13:18 ` [PATCH 8/8] arm: setup MM using information from the device tree David Vrabel
2012-02-13 15:27 ` [PATCH 0/8] arm: initial device tree support (#3) Ian Campbell
2012-02-13 15:49   ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2012-02-10 13:03 [PATCH 0/8] arm: initial device tree support (#2) David Vrabel
2012-02-10 13:03 ` [PATCH 3/8] libfdt: add to build David Vrabel

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=1329139131-27554-4-git-send-email-david.vrabel@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).