To help the transition period when DRI loaders are being updated
to support the newer __driDriverExtensions_foo mechanism,
we populate __DRIextension with the extensions returned
by __driDriverExtensions_foo during a library contructor
function.
We find the driver foo's name by using the dladdr
On Fri, Dec 6, 2013 at 2:35 AM, Jordan Justen jordan.l.jus...@intel.com wrote:
To help the transition period when DRI loaders are being updated
to support the newer __driDriverExtensions_foo mechanism,
we populate __DRIextension with the extensions returned
by __driDriverExtensions_foo during
Jordan Justen jljus...@gmail.com writes:
We find the driver foo's name by using the dladdr function
which gives the path of the dynamic library's name that
was being loaded.
That sounds like all kinds of win for existing X servers. Thanks for
doing it up in style, so that a megadrivers build
On 12/06/2013 01:12 PM, Jordan Justen wrote:
On Fri, Dec 6, 2013 at 2:35 AM, Jordan Justen jordan.l.jus...@intel.com
wrote:
To help the transition period when DRI loaders are being updated
to support the newer __driDriverExtensions_foo mechanism,
we populate __DRIextension with the
On Fri, Dec 6, 2013 at 3:50 PM, Ian Romanick i...@freedesktop.org wrote:
On 12/06/2013 01:12 PM, Jordan Justen wrote:
On Fri, Dec 6, 2013 at 2:35 AM, Jordan Justen jordan.l.jus...@intel.com
wrote:
To help the transition period when DRI loaders are being updated
to support the newer
