public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: igeiser@devonit.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] mesa-dri: add extra dri drivers
Date: Wed, 30 Jan 2013 08:26:11 -0500	[thread overview]
Message-ID: <1359552371-27121-1-git-send-email-igeiser@devonit.com> (raw)

From: Ian Reinhart Geiser <igeiser@devonit.com>

On x86 the ATI and NVidia drm drivers are valid to build.
Currently there are _append_x86 and _append_x64 lines that
explicitly add i915 and i965.  For consistency I think that
the ATI and NVidia drm driver should be added. In classic
these were tunable via the machine configuration files. I
would argue we should go back to that so we should make
the DRIDRIVERS field something that can be defined there.

* Made the DRIDRIVERS field overridable.
* Add ATI and NVidia DRI drivers to the build list for
  x86 and x86_64.

Signed-off-by: Ian Reinhart Geiser <igeiser@devonit.com>
---
 meta/recipes-graphics/mesa/mesa-dri.inc |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-graphics/mesa/mesa-dri.inc b/meta/recipes-graphics/mesa/mesa-dri.inc
index 1f6ec78..12e9dd5 100644
--- a/meta/recipes-graphics/mesa/mesa-dri.inc
+++ b/meta/recipes-graphics/mesa/mesa-dri.inc
@@ -1,9 +1,9 @@
 DEPENDS += "libdrm expat udev"
 X11_DEPS += "dri2proto"
 
-DRIDRIVERS = "swrast"
-DRIDRIVERS_append_x86 = ",i915,i965"
-DRIDRIVERS_append_x86-64 = ",i915,i965"
+DRIDRIVERS ?= "swrast"
+DRIDRIVERS_append_x86 = ",i915,i965,nouveau,r200,radeon"
+DRIDRIVERS_append_x86-64 = ",i915,i965,nouveau,r200,radeon"
 
 EXTRA_OECONF += "--disable-gallium --without-gallium-drivers"
 EXTRA_OECONF += "--enable-dri --with-dri-drivers=${DRIDRIVERS}"
-- 
1.7.9.5




             reply	other threads:[~2013-01-30 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 13:26 igeiser [this message]
2013-01-30 15:16 ` [PATCH] mesa-dri: add extra dri drivers Burton, Ross
2013-01-30 16:38   ` Ian Geiser
2013-01-30 17:41     ` Burton, Ross

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=1359552371-27121-1-git-send-email-igeiser@devonit.com \
    --to=igeiser@devonit.com \
    --cc=openembedded-core@lists.openembedded.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