On Wed, 2019-12-04 at 01:48 -0500, Marek Olšák wrote:
> On Wed., Dec. 4, 2019, 01:20 Tapani Pälli,
> wrote:
> > Hi;
> >
> > On 12/4/19 2:39 AM, Marek Olšák wrote:
> > > Hi,
> > >
> > > Here are 2 proposals to simplify and better optimize the GL-
> > >Gallium
> > > translation.
> > >
> > > 1) M
On Wed., Dec. 4, 2019, 01:20 Tapani Pälli, wrote:
> Hi;
>
> On 12/4/19 2:39 AM, Marek Olšák wrote:
> > Hi,
> >
> > Here are 2 proposals to simplify and better optimize the GL->Gallium
> > translation.
> >
> > 1) Move classic drivers to a fork of Mesa, and remove them from master.
> > Classic driv
Hi;
On 12/4/19 2:39 AM, Marek Olšák wrote:
Hi,
Here are 2 proposals to simplify and better optimize the GL->Gallium
translation.
1) Move classic drivers to a fork of Mesa, and remove them from master.
Classic drivers won't share any code with master. glvnd will load them,
but glvnd is not
On Tue, Dec 3, 2019 at 8:19 PM Dave Airlie wrote:
> On Wed, 4 Dec 2019 at 10:39, Marek Olšák wrote:
> >
> > Hi,
> >
> > Here are 2 proposals to simplify and better optimize the GL->Gallium
> translation.
> >
> > 1) Move classic drivers to a fork of Mesa, and remove them from master.
> Classic dr
Hi,
FYI, this is a pretty big change, so I'm posting it here as well:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2956
Only the GL state tracker will keep its name. All other state trackers will
be called "API implementations".
Marek
___
me
On Wed, 4 Dec 2019 at 10:39, Marek Olšák wrote:
>
> Hi,
>
> Here are 2 proposals to simplify and better optimize the GL->Gallium
> translation.
>
> 1) Move classic drivers to a fork of Mesa, and remove them from master.
> Classic drivers won't share any code with master. glvnd will load them, bu
+Boyuan
From: Marek Olšák
Sent: December 3, 2019 7:21:23 PM
To: Sahu, Satyajit ; Liu, Leo
Cc: ML Mesa-dev ; Sharma, Deepak
Subject: Re: [Mesa-dev] [PATCH] radeonsi: Add support for midstream bitrate
change in encoder
+Leo
On Mon, Dec 2, 2019 at 11:31 PM Satya
Hi,
Here are 2 proposals to simplify and better optimize the GL->Gallium
translation.
1) Move classic drivers to a fork of Mesa, and remove them from master.
Classic drivers won't share any code with master. glvnd will load them, but
glvnd is not ready for this yet.
2) Keep classic drivers. Fork
+Leo
On Mon, Dec 2, 2019 at 11:31 PM Satyajit Sahu wrote:
> Added support for bitrate change in between encoding.
>
> Signed-off-by: Satyajit Sahu
>
> diff --git a/src/gallium/drivers/radeon/radeon_vce.c
> b/src/gallium/drivers/radeon/radeon_vce.c
> index 84d3c1e2fa4..7d7a2fa4eb3 100644
> --- a
Meant to Cc Mark too :)
On 03/12/2019 21:24, Lionel Landwerlin wrote:
Hi all,
Our Windows drivers ships with a particular query in
GL_INTEL_performance_query called Intel_Null_Hardware_Query.
The query doesn't report any counter. The query isn't even listed if
you go through the list using gl
Hi all,
Our Windows drivers ships with a particular query in
GL_INTEL_performance_query called Intel_Null_Hardware_Query.
The query doesn't report any counter. The query isn't even listed if you
go through the list using glGetNextPerfQueryIdINTEL().
It's only returned using glGetPerfQueryIdByN
>
> well that's the very first APU generation and unfortunately nobody is
> working on that old hardware any more.
>
Agreed, definitely old hardware. Unfortunately we have 10,000 of these
things in production and they have been playing hardware accelerated mpeg2
fine until we upgraded to Ubuntu 16
>
> Are you sure that the Gentoo based setup isn't software decoding based?
>
Yes 100% confident. We configured VLC to use VA-API decoding with software
based deinterlacing. The VA-API implementation is using the VDPAU backend
shim as shown in the vainfo output: *vainfo: Driver version:
Splitted-D
>
> What regression was that? The difference between VDPAU and VA-API is only
> marginal for codec support.
>
The regression revolved around deinterlacing the content. If we had to
deinterlace 1080i for instance, the playback was very choppy and dropped
frames.
Well how was the stack configured t
14 matches
Mail list logo
