On 9 February 2018 at 16:02, Daniel Stone wrote:
> Hi Emil,
>
> On 8 February 2018 at 21:56, Emil Velikov wrote:
>> On 8 February 2018 at 14:05, Daniel Stone wrote:
>>> Extend the visual map from only containing names and bitmasks, to also
>>> carrying the three format enums we need. These are t
Hi Emil,
On 8 February 2018 at 21:56, Emil Velikov wrote:
> On 8 February 2018 at 14:05, Daniel Stone wrote:
>> Extend the visual map from only containing names and bitmasks, to also
>> carrying the three format enums we need. These are the DRIImage format
>> tokens for internal allocation, Four
On 8 February 2018 at 14:05, Daniel Stone wrote:
> Extend the visual map from only containing names and bitmasks, to also
> carrying the three format enums we need. These are the DRIImage format
> tokens for internal allocation, FourCC codes for wl_drm and dmabuf
> protocol, and wl_shm codes for s
Extend the visual map from only containing names and bitmasks, to also
carrying the three format enums we need. These are the DRIImage format
tokens for internal allocation, FourCC codes for wl_drm and dmabuf
protocol, and wl_shm codes for swrast drivers.
We will later use these formats to elimina
Extend the visual map from only containing names and bitmasks, to also
carrying the three format enums we need. These are the DRIImage format
tokens for internal allocation, FourCC codes for wl_drm and dmabuf
protocol, and wl_shm codes for swrast drivers.
We will later use these formats to elimina
