>
> On Tue, Jul 19, 2016 at 09:41:22AM -0400, Frediano Ziglio wrote:
> > > I don't think we have strong reasons to support software encoding, video
> > > encoding is really expensive, and that mmap/copy is not going to be
> > > marginal, so even less these 2 syscalls.
> > >
> >
> > Using HW
On Tue, Jul 19, 2016 at 09:41:22AM -0400, Frediano Ziglio wrote:
> > I don't think we have strong reasons to support software encoding, video
> > encoding is really expensive, and that mmap/copy is not going to be
> > marginal, so even less these 2 syscalls.
> >
>
> Using HW encoding is not easy
> Hi
>
> - Original Message -
> > >
> > > Hi
> > >
> > > - Original Message -
> > > > Forgot to add RFC to the subject
> > > >
> > >
> > > What's the rationale? if you share the texture id, you must share the GL
> > > context too, right? Why not use a lower level dmabuf fd
Hi
- Original Message -
> >
> > Hi
> >
> > - Original Message -
> > > Forgot to add RFC to the subject
> > >
> >
> > What's the rationale? if you share the texture id, you must share the GL
> > context too, right? Why not use a lower level dmabuf fd that can be
> > imported
>
>
> Hi
>
> - Original Message -
> > Forgot to add RFC to the subject
> >
>
> What's the rationale? if you share the texture id, you must share the GL
> context too, right? Why not use a lower level dmabuf fd that can be imported
> by the server gl context (which is also what the
Hi
- Original Message -
> Forgot to add RFC to the subject
>
What's the rationale? if you share the texture id, you must share the GL
context too, right? Why not use a lower level dmabuf fd that can be imported by
the server gl context (which is also what the protocol require anyway)?
