From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 0/4] Try to clean up proprietary OpenGL drivers
Date: Fri, 23 Jan 2015 11:57:42 +0100 [thread overview]
Message-ID: <20150123105742.GB8089@free.fr> (raw)
In-Reply-To: <1421839408-15839-1-git-send-email-jezz@sysmic.org>
J?r?me, All,
On 2015-01-21 12:23 +0100, J?r?me Pouiller spake thusly:
> Until now, xorg-xserver depends on mesa3d to compile with GLX/DRI support.
> However, there was problem with proprietary OpenGL drivers. These ones depends
> on GLX/DRI support (so, they depends on mesa3d) and overwrite files provided by
> mesa3d (so, they conflict with mesa3d).
>
> Thanks to opengl-registry, it is possible to change proprietary OpenGL drivers
> in real LibGL provider and compile GLX/DRI support using proprietary drivers
> instead of mesa3d.
>
> Notice this series aim to highlight the problem described above. It does not
> aim to be upstreamed. It apply on top of Yann series about nvidia driver and
> my series about imx6 gpu driver.
>
> J?r?me Pouiller (4):
> nvidia-driver: Add gl.pc
> gpu-viv-bin-mx6q: is a libgl provider
> opengl-registry: Also provide DRI interface
> xorg-server: Depends on libgl to enable DRI/GLX
So, I have some comments about this series.
First, I have included your patch to add gl.pc to nvidia-driver. Thanks!
:-)
Second, the imx6 stuff does not apply since your series has not yet been
applied. I'll leave it to you to cary thos two patches. ;-)
Finally, I am not too fond of bundling the dri header, neither in the
OpenGL registry package, nor in any other package.
I know I bundled the gl.h header, but I did so on the assumption that
was the only header we'd have to carry. Turns out I was wrong, and we
need another header. That's unfortunate. :-(
I would really like to see a proper solution for that, but I have no
good idea... :-/
The only I can come up with is to change the mesa3d package to only
install those missing headers, and have the registry depend on it.
But I do not find this option very nice...
An alternative would be to provide a prompt-less, stripped mesa3d
package that woudl install only headers; package that we may call
something like mesa3d-headers and that the registry would select.
However, I do not find this to be much any more appealing that the
alternatives... :-(
I'm open for comments...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-01-23 10:57 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
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 ` Yann E. MORIN [this message]
2015-01-24 17:02 ` [Buildroot] [RFC 0/4] Try to clean up proprietary OpenGL drivers 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=20150123105742.GB8089@free.fr \
--to=yann.morin.1998@free.fr \
--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