From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 2/4] gpu-viv-bin-mx6q: is a libgl provider
Date: Sat, 4 Apr 2015 18:48:03 +0200 [thread overview]
Message-ID: <20150404184803.31434bd7@free-electrons.com> (raw)
In-Reply-To: <1421839408-15839-3-git-send-email-jezz@sysmic.org>
Dear J?r?me Pouiller,
On Wed, 21 Jan 2015 12:23:26 +0100, J?r?me Pouiller wrote:
> -GPU_VIV_BIN_MX6Q_PROVIDES = libegl libgles libopenvg
> +GPU_VIV_BIN_MX6Q_DEPENDENCIES = opengl-registry
> +GPU_VIV_BIN_MX6Q_PROVIDES = libgl libegl libgles libopenvg
> GPU_VIV_BIN_MX6Q_LIB_TARGET = $(call qstrip,$(BR2_PACKAGE_GPU_VIV_BIN_MX6Q_OUTPUT))
In the end, opengl-registry was never added, we preferred using the
mesa3d headers instead, through the mesa3d-headers package.
Can you respin this patch and resend a new version accordingly?
In the mean time, I've marked your patch as Changes Requested in
patchwork.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-04 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 11:23 [Buildroot] [RFC 0/4] Try to clean up proprietary OpenGL drivers Jérôme Pouiller
2015-01-21 11:23 ` [Buildroot] [RFC 1/4] nvidia-driver: Add gl.pc Jérôme Pouiller
2015-01-21 11:23 ` [Buildroot] [RFC 2/4] gpu-viv-bin-mx6q: is a libgl provider Jérôme Pouiller
2015-04-04 16:48 ` Thomas Petazzoni [this message]
2015-04-05 9:10 ` Jérôme Pouiller
2015-04-05 9:28 ` Thomas Petazzoni
2015-01-21 11:23 ` [Buildroot] [RFC 3/4] opengl-registry: Also provide DRI interface Jérôme Pouiller
2015-01-21 11:23 ` [Buildroot] [RFC 4/4] xorg-server: Depends on libgl to enable DRI/GLX Jérôme Pouiller
2015-01-23 10:57 ` [Buildroot] [RFC 0/4] Try to clean up proprietary OpenGL drivers Yann E. MORIN
2015-01-24 17:02 ` Yann E. MORIN
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=20150404184803.31434bd7@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 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.