On Tue 20 Jun 2017, Jason Ekstrand wrote:
> On Wed, Jun 7, 2017 at 4:45 PM, Chad Versace <[1]chadvers...@chromium.org>
> wrote:
>
> On Tue 06 Jun 2017, Daniel Stone wrote:
> > Hi Chad,
> >
> > On 6 June 2017 at 21:36, Chad Versace <[2]chadvers...@chromium.org>
> wrote:
> >
On Wed, Jun 7, 2017 at 4:45 PM, Chad Versace
wrote:
> On Tue 06 Jun 2017, Daniel Stone wrote:
> > Hi Chad,
> >
> > On 6 June 2017 at 21:36, Chad Versace wrote:
> > > @@ -254,8 +255,22 @@ create_mt_for_dri_image(struct brw_context *brw,
> > >
Hi Chad,
On 8 June 2017 at 00:45, Chad Versace wrote:
> On Tue 06 Jun 2017, Daniel Stone wrote:
>> I wonder if it wouldn't be better to do this in
>> intel_create_image_from_name. That way it would be more obvious
>> up-front what's happening,
>
> I agree that the
On Tue 06 Jun 2017, Daniel Stone wrote:
> Hi Chad,
>
> On 6 June 2017 at 21:36, Chad Versace wrote:
> > @@ -254,8 +255,22 @@ create_mt_for_dri_image(struct brw_context *brw,
> > struct gl_context *ctx = >ctx;
> > struct intel_mipmap_tree *mt;
> > uint32_t
Hi Chad,
On 6 June 2017 at 21:36, Chad Versace wrote:
> @@ -254,8 +255,22 @@ create_mt_for_dri_image(struct brw_context *brw,
> struct gl_context *ctx = >ctx;
> struct intel_mipmap_tree *mt;
> uint32_t draw_x, draw_y;
> + mesa_format format =
This enables support for importing RGBX EGLImage textures on
Skylake.
Chrome OS needs support for RGBX EGLImage textures because because
the Android framework produces HAL_PIXEL_FORMAT_RGBX winsys
surfaces, which the Chrome OS compositor consumes as dma_bufs. On
hardware for which