Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 07/15] xdriver_xf86-video-imx-viv: new package
Date: Wed, 21 Jan 2015 09:41:58 +0100	[thread overview]
Message-ID: <2046060.LHRJYafqiX@aquila> (raw)
In-Reply-To: <20150119222043.GF4217@free.fr>

Hello All,

On Monday 19 January 2015 23:20:43 Yann E. MORIN wrote:
> J?r?me, All,
> 
> On 2015-01-17 01:11 +0100, J?r?me Pouiller spake thusly:
> > On Friday 16 January 2015 17:15:33 Thomas Petazzoni wrote:
> > > Dear J?r?me Pouiller,
> > > 
> > > On Fri, 16 Jan 2015 17:04:20 +0100, J?r?me Pouiller wrote:
> > > 
> > > > > The world of OpenGL stuff will always surprise me. Why on earth does a
> > > > > X.org driver that uses a proprietary OpenGL implementation needs
> > > > > Mesa3D ?!?
> > > > 
> > > > In fact, xf86-video-imx-viv does not depends directly on mesa3d. However, it 
> > > > depend on xorg server compiled with --enable-dri --enable-glx. But, these 
> > > > options are enabled only if BR2_PACKAGE_MESA3D_DRI_DRIVER is enabled.
> > > 
> > > Maybe this should be changed, so that other drivers can enable it,
> > > without referencing Mesa related options, no?
> > > 
> > > Also, the code in the xserver package does:
> > > 
> > > ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER),y)
> > > XSERVER_XORG_SERVER_CONF_OPTS += --enable-dri --enable-glx
> > > XSERVER_XORG_SERVER_DEPENDENCIES += mesa3d xproto_xf86driproto
> > > else
> > > XSERVER_XORG_SERVER_CONF_OPTS += --disable-dri --disable-glx
> > > endif
> > > 
> > > So it really builds mesa as well. Is this needed ?
> > We cannot use gpu-viv-bin-mx6q to compile Xorg with DRI and GLX since 
> > it does not provide all necessary files. Especially, OpenGL headers 
> > (GL/gl.h, GL/glx.h, ...) are missing[1]. We may solve this issue using
> > "opengl-registry" posted by Yann a few months ago. It may be 
> > sufficient.
> 
> For the records, I've posted an updated series:
>     http://lists.busybox.net/pipermail/buildroot/2015-January/117642.html
> 
> Care to see if it is posible to update your series to use the Khronos
> registry/ies? If so, it would great if you could review/ack the patches
> so they get applied soon, so you can in turn repost an updated series of
> yours! ;-)

I am able to build xorg-xserver w/ --enable-dri --enable-glx and 
without mesa3d. Instead of mesa3d, I built opengl-registry and a libGL
provider (I used gpu-viv-bin-mx6q, but it should also work with 
nvidia-driver).

In add, I need to manually add gl.pc, dri.pc and GL/internal/dri_interface.h
(picked from mesa3d)

I will try to generate a cleaner patch in order to begin a discussion 
about this issue.

However, I think this work is an improvement of dri/glx support and is
not really related to "Xorg support for iMX6" series.

[...]
-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  reply	other threads:[~2015-01-21  8:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 13:46 [Buildroot] [PATCH v5 00/15] Add Xorg support for iMX6 Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 01/15] mesa3d: Give possibility to external backends to enable DRI/Gallium Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 02/15] gpu-viv-bin-mx6q: use self-extractible helper Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 03/15] gpu-viv-bin-mx6q: fix compiling issues with EGL_API_FB Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 04/15] gpu-viv-bin-mx6q: fix GLESv2 support Jérôme Pouiller
2014-12-27 20:34   ` Thomas Petazzoni
2014-12-09 13:46 ` [Buildroot] [PATCH v5 05/15] gpu-viv-bin-mx6q: make fb/x11 choice explicit Jérôme Pouiller
2014-12-27 20:36   ` Thomas Petazzoni
2014-12-09 13:46 ` [Buildroot] [PATCH v5 06/15] gpu-viv-bin-mx6q: change output selection mechanism Jérôme Pouiller
2014-12-27 20:38   ` Thomas Petazzoni
2014-12-09 13:46 ` [Buildroot] [PATCH v5 07/15] xdriver_xf86-video-imx-viv: new package Jérôme Pouiller
2014-12-27 20:43   ` Thomas Petazzoni
2015-01-16 16:04     ` Jérôme Pouiller
2015-01-16 16:15       ` Thomas Petazzoni
2015-01-17  0:11         ` Jérôme Pouiller
2015-01-19 22:20           ` Yann E. MORIN
2015-01-21  8:41             ` Jérôme Pouiller [this message]
2014-12-09 13:46 ` [Buildroot] [PATCH v5 08/15] libdrm: fix support for xserver with Vivante drivers Jérôme Pouiller
2014-12-27 20:49   ` Thomas Petazzoni
2014-12-09 13:46 ` [Buildroot] [PATCH v5 09/15] qt5base: apply new patch naming policy Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 10/15] qt5base: fix Vivante x11/EGL configuration Jérôme Pouiller
2014-12-09 13:58   ` Thomas Petazzoni
2014-12-09 13:46 ` [Buildroot] [PATCH v5 11/15] Vivante drivers: bump to version 3.10.17-1.0.1 Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 12/15] nitrogen6x_defconfig: bump kernel to 3.10.17_1.0.1_ga Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 13/15] freescale_imx6*_defconfig: " Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 14/15] qmx6_defconfig: update Jérôme Pouiller
2014-12-09 13:46 ` [Buildroot] [PATCH v5 15/15] qmx6_qt5_demo_defconfig: new defconfig Jérôme Pouiller
2014-12-20  1:41 ` [Buildroot] [PATCH v5 00/15] Add Xorg support for iMX6 Gary Bisson
2014-12-20 14:27   ` Jérôme Pouiller
2014-12-26 18:39     ` Gary Bisson

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=2046060.LHRJYafqiX@aquila \
    --to=jezz@sysmic.org \
    --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