Roland Scheidegger <srol...@vmware.com> writes: > Am 06.08.2014 22:33, schrieb Eric Anholt:
>> + * When building using the simulator (on x86), we advertise ourselves as the
>> + * i965 driver so that you can just make a directory with a link from
>> + * i965_dri.so to the built vc4_dri.so, and point LIBGL_DRIVERS_PATH to that
>> + * on your i965-using host to run the driver under simulation.
>> + *
>> + * This is, of course, incompatible with building with the ilo driver, but
>> you
>> + * shouldn't be building that anyway.
>> + */
>> +PUBLIC const __DRIextension **__driDriverGetExtensions_i965(void)
>> +{
>> + globalDriverAPI = &galliumdrm_driver_api;
>> + return galliumdrm_driver_extensions;
>> +}
>> +#endif
> I have no idea how that simulator works, but this looks like a fairly
> gross hack to me. Couldn't you use something similar to how the software
> based drivers are loaded or anything like that?
I need a DRI fd and normal DRI buffer management from a host x server
(which I interact with using the dumb ioctls). Are you thinking of
something that would provide that in a simpler way?
pgpHs5t3f30AY.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
