public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: [PATCH v2 0/3] Improve DRI handling support flexibility
Date: Tue, 29 Jan 2013 09:57:44 -0200	[thread overview]
Message-ID: <1359460667-26291-1-git-send-email-otavio@ossystems.com.br> (raw)

There're some processors which provide binary blobs for DRI and GPU
support which need to be build in BSP; to avoid some dirt and ugly
hacks in BSP we ought to be flexible.

We splitted the glx and dri PACKAGECONFIG options and added a
virtual/dri provider so BSP can override it, if need.

Otavio Salvador (3):
  mesa: Add virtual/dri provides
  xserver-xorg: Split 'glx' and 'dri' PACKAGECONFIG options
  default-providers.inc: Set 'virtual/dri' as default for 'mesa-dri'

 meta/conf/distro/include/default-providers.inc      |  1 +
 meta/recipes-graphics/mesa/mesa-common.inc          |  4 ++--
 meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 13 ++++++++-----
 3 files changed, 11 insertions(+), 7 deletions(-)

-- 
1.8.1




             reply	other threads:[~2013-01-29 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 11:57 Otavio Salvador [this message]
2013-01-29 11:57 ` [PATCH v2 1/3] mesa: Add virtual/dri provides Otavio Salvador
2013-01-29 11:57 ` [PATCH v2 2/3] xserver-xorg: Split 'glx' and 'dri' PACKAGECONFIG options Otavio Salvador
2013-01-29 11:57 ` [PATCH v2 3/3] default-providers.inc: Set 'virtual/dri' as default for 'mesa-dri' Otavio Salvador
2013-01-30 16:13 ` [PATCH v2 0/3] Improve DRI handling support flexibility Burton, Ross
2013-01-31 12:17   ` Otavio Salvador

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=1359460667-26291-1-git-send-email-otavio@ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --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