On Tue, 5 Feb 2019 21:57:40 +
"Strasser, Kevin" wrote:
> Pekka Paalanen wrote:
> > On Mon, 4 Feb 2019 22:10:00 + "Strasser, Kevin"
> > wrote:
> > > That is what I was trying to achieve, offering applications fp16 scan
> > > out buffers. I'm not aware of any explicit requirement for add
Pekka Paalanen wrote:
> On Mon, 4 Feb 2019 22:10:00 + "Strasser, Kevin"
> wrote:
> > That is what I was trying to achieve, offering applications fp16 scan
> > out buffers. I'm not aware of any explicit requirement for adding the
> > wl_shm format outside of Mesa's Walyand egl driver, which inc
On Mon, 4 Feb 2019 22:10:00 +
"Strasser, Kevin" wrote:
> Pekka Paalanen wrote:
> > is there a reason you need these in the wl_shm format list? That is,
> > essentially for software rendered stuff?
> >
> > The zwp_linux_dmabuf extension which GL and Vulkan implementations are
> > using only sa
Pekka Paalanen wrote:
> is there a reason you need these in the wl_shm format list? That is,
> essentially for software rendered stuff?
>
> The zwp_linux_dmabuf extension which GL and Vulkan implementations are
> using only says the format is a drm_fourcc format, so there is no need
> to explicitly
On Fri, 1 Feb 2019 13:54:39 -0800
Kevin Strasser wrote:
> I'm sharing this as an RFC while the kernel [1] patches are still under
> review.
> On the Mesa mailing list some doubts [2] were raised as to whether we would be
> able to land these without fp16 support in Pixman, so I'd like some inpu
