From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: enable DRI drivers for xorg-less configurations
Date: Tue, 29 Mar 2016 20:26:09 +0200 [thread overview]
Message-ID: <20160329202609.1610b4cd@free-electrons.com> (raw)
In-Reply-To: <1459201695-30709-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Mon, 28 Mar 2016 18:48:15 -0300, Gustavo Zacarias wrote:
> mesa3d can in fact build the DRI infrastructure/drivers just fine
> without lingering x11 libs around, it just needs libdrm & friends which
> are already accounted for.
>
> So make the libGL (full OpenGL) providing abilities dependant on x11
> being present.
>
> It serves it's purpose for EGL+GLES hardware acceleration, and can in
> fact be built without them, but it's probably not very useful (still,
> leave the option for people inclined to do so).
>
> Simple test defconfig:
>
> BR2_arm=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_PACKAGE_MESA3D=y
> BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST=y
> BR2_PACKAGE_MESA3D_DRI_DRIVER_NOUVEAU=y
> BR2_PACKAGE_MESA3D_DRI_DRIVER_RADEON=y
> BR2_PACKAGE_MESA3D_OPENGL_EGL=y
> BR2_PACKAGE_MESA3D_OPENGL_ES=y
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/mesa3d/Config.in | 9 +++------
> package/mesa3d/mesa3d.mk | 3 +++
> 2 files changed, 6 insertions(+), 6 deletions(-)
Applied to master, thanks. I'm pretty sure it's going to trigger some
cases that were not accounted for, but the only way to know is to get
the autobuilders to play with this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-29 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 21:48 [Buildroot] [PATCH] mesa3d: enable DRI drivers for xorg-less configurations Gustavo Zacarias
2016-03-29 18:26 ` Thomas Petazzoni [this message]
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=20160329202609.1610b4cd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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