From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Improve DRI handling support flexibility
Date: Fri, 25 Jan 2013 23:07:21 +0000 [thread overview]
Message-ID: <1359155241.13917.22.camel@ted> (raw)
In-Reply-To: <1359153142-13425-1-git-send-email-otavio@ossystems.com.br>
On Fri, 2013-01-25 at 20:32 -0200, Otavio Salvador wrote:
> 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 (2):
> mesa: Add virtual/dri provides
> xserver-xorg: Split 'glx' and 'dri' PACKAGECONFIG options
>
> meta/recipes-graphics/mesa/mesa-common.inc | 4 ++--
> meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 13 ++++++++-----
> 2 files changed, 10 insertions(+), 7 deletions(-)
I didn't see the patches here but this would suggest the xserver and
mesa plus anything that depends on them becomes machine specific.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-25 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 22:32 [PATCH 0/2] Improve DRI handling support flexibility Otavio Salvador
2013-01-25 22:32 ` [PATCH 1/2] mesa: Add virtual/dri provides Otavio Salvador
2013-01-28 16:08 ` Burton, Ross
2013-01-25 22:32 ` [PATCH 2/2] xserver-xorg: Split 'glx' and 'dri' PACKAGECONFIG options Otavio Salvador
2013-01-25 23:07 ` Richard Purdie [this message]
2013-01-26 15:16 ` [PATCH 0/2] Improve DRI handling support flexibility 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=1359155241.13917.22.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.