dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: airlied@linux.ie, dri-devel@lists.freedesktop.org
Subject: [PATCH 12/12] gma500: Now connect up to the DRM build to finish the job
Date: Thu, 03 Nov 2011 18:22:48 +0000	[thread overview]
Message-ID: <20111103182248.29503.26875.stgit@bob.linux.org.uk> (raw)
In-Reply-To: <20111103182046.29503.60288.stgit@bob.linux.org.uk>

From: Alan Cox <alan@linux.intel.com>

Signed-off-by: Alan Cox <alan@linux.intel.com>
---

 drivers/gpu/drm/Kconfig  |    3 +++
 drivers/gpu/drm/Makefile |    1 +
 2 files changed, 4 insertions(+), 0 deletions(-)


diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index b493663..7c1cb0d 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -158,3 +158,6 @@ config DRM_SAVAGE
 	help
 	  Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
 	  chipset. If M is selected the module will be called savage.
+
+source "drivers/gpu/drm/gma500/Kconfig"
+
diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile
index 89cf05a..2d1fbc1 100644
--- a/drivers/gpu/drm/Makefile
+++ b/drivers/gpu/drm/Makefile
@@ -35,4 +35,5 @@ obj-$(CONFIG_DRM_SAVAGE)+= savage/
 obj-$(CONFIG_DRM_VMWGFX)+= vmwgfx/
 obj-$(CONFIG_DRM_VIA)	+=via/
 obj-$(CONFIG_DRM_NOUVEAU) +=nouveau/
+obj-$(CONFIG_DRM_GMA500) += gma500/
 obj-y			+= i2c/

  parent reply	other threads:[~2011-11-03 18:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 18:20 [PATCH 01/12] gma500: Move the basic driver out of staging Alan Cox
2011-11-03 18:20 ` [PATCH 02/12] gma500: GEM and GEM glue Alan Cox
2011-11-03 19:27   ` Daniel Vetter
2011-11-03 18:21 ` [PATCH 03/12] gma500: introduce the GTT and MMU handling logic Alan Cox
2011-11-03 20:12   ` Daniel Vetter
2011-11-03 22:25     ` Alan Cox
2011-11-03 22:32       ` Daniel Vetter
2011-11-03 18:21 ` [PATCH 04/12] gma500: introduce the framebuffer support code Alan Cox
2011-11-03 18:21 ` [PATCH 05/12] gma500: Add device framework Alan Cox
2011-11-03 18:21 ` [PATCH 06/12] gma500: Add the glue to the various BIOS and firmware interfaces Alan Cox
2011-11-03 18:21 ` [PATCH 07/12] gma500: Add the i2c bus support Alan Cox
2011-11-03 18:22 ` [PATCH 08/12] gma500: Add the core DRM files and headers Alan Cox
2011-11-16 12:04   ` Dave Airlie
2011-11-16 14:47     ` Alan Cox
2011-11-03 18:22 ` [PATCH 09/12] gma500: Add Poulsbo support Alan Cox
2011-11-03 18:22 ` [PATCH 10/12] gma500: Add Oaktrail support Alan Cox
2011-11-03 18:22 ` [PATCH 11/12] gma500: Add support for Cedarview Alan Cox
2011-11-03 18:22 ` Alan Cox [this message]
2011-11-03 20:18 ` [PATCH 01/12] gma500: Move the basic driver out of staging Thomas Hellstrom
2011-11-03 22:27   ` Alan Cox

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=20111103182248.29503.26875.stgit@bob.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox