blem.
The following bug contains a test that reproduces the problem
by running a couple of vaapih264enc in the same process. The above
also explains why there was no pb when running them in separated
processes.
https://bugzilla.gnome.org/show_bug.cgi?id=785085
Apart from the type above, patch is
Am 25.07.2017 um 14:13 schrieb Leo Liu:
On 07/25/2017 05:19 AM, Christian König wrote:
Am 25.07.2017 um 08:27 schrieb Michel Dänzer:
On 25/07/17 02:54 AM, Leo Liu wrote:
To workaround an unknown bug.
Signed-off-by: Leo Liu <leo@amd.com>
---
src/gallium/drivers/radeon/radeon_vcn
Am 25.07.2017 um 08:27 schrieb Michel Dänzer:
On 25/07/17 02:54 AM, Leo Liu wrote:
To workaround an unknown bug.
Signed-off-by: Leo Liu
---
src/gallium/drivers/radeon/radeon_vcn_dec.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
return true;
default:
- return false;
+ switch (rscreen->info.vce_fw_version & (0xff << 24)) {
+ case FW_53:
+ return true;
+
+ default:
+
Am 20.07.2017 um 16:59 schrieb Marek Olšák:
On Jul 19, 2017 10:21 PM, "zhoucm1" > wrote:
On 2017年07月19日 23:34, Marek Olšák wrote:
On Jul 19, 2017 3:36 AM, "zhoucm1" > wrote:
Thompson <s...@jkqxz.net>
Reviewed-by: Christian König <christian.koe...@amd.com>
You still don't have write access to Mesa, don't you?
Thanks for the help,
Christian.
---
On 14/07/17 11:01, Christian König wrote:
That just looks like the inversed Z-scan order we already have in
Am 13.07.2017 um 22:38 schrieb Mark Thompson:
Mesa here requires the scaling lists in diagonal scan order, but
VAAPI passes them in raster scan order. Therefore, rearrange the
elements when copying.
Nice catch, just one note below.
(This ordering was likely inherited from
VDPAU, which does
Hi Julien,
sorry, totally missed that question.
I think the cleanest approach would be that the OpenMAX state tracker
dlopen()s the EGL and tries to export the eglImage into a dma_buf handle.
No idea how to do this, but I'm pretty sure somebody on the mailing list
should know the details
Hi Julien,
sorry, totally missed that question.
I think the cleanest approach would be that the OpenMAX state tracker
dlopen()s the EGL and tries to export the eglImage into a dma_buf handle.
No idea how to do this, but I'm pretty sure somebody on the mailing list
should know the details
Am 08.07.2017 um 00:27 schrieb Marek Olšák:
On Fri, Jul 7, 2017 at 9:37 PM, Dave Airlie <airl...@gmail.com> wrote:
On 8 July 2017 at 04:07, Christian König <deathsim...@vodafone.de> wrote:
Am 07.07.2017 um 18:51 schrieb Marek Olšák:
On Fri, Jul 7, 2017 at 11:18 AM, Christian Kön
Am 07.07.2017 um 18:51 schrieb Marek Olšák:
On Fri, Jul 7, 2017 at 11:18 AM, Christian König
<deathsim...@vodafone.de> wrote:
What tilling format have the destination textures?
Sounds like the offset is just added so that we distribute memory accesses
more equally over memory channels
What tilling format have the destination textures?
Sounds like the offset is just added so that we distribute memory
accesses more equally over memory channels.
Regards,
Christian.
Am 07.07.2017 um 09:18 schrieb Dave Airlie:
From: Dave Airlie
(this patch doesn't seem
Am 04.07.2017 um 15:13 schrieb Nicolai Hähnle:
On 01.07.2017 01:03, Andres Rodriguez wrote:
From: Dave Airlie
Signed-off-by: Andres Rodriguez
---
src/gallium/drivers/radeon/r600_pipe_common.h | 6 ++
src/gallium/drivers/radeon/r600_texture.c |
Am 26.06.2017 um 15:29 schrieb Leo Liu:
It's enabled through message buffer for UVD
Signed-off-by: Leo Liu <leo@amd.com>
Acked-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_vcn_dec.c | 1 +
src/gallium/drivers/radeon/radeon_vcn_dec.
Am 21.06.2017 um 11:05 schrieb Samuel Pitoiset:
Signed-off-by: Samuel Pitoiset <samuel.pitoi...@gmail.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/mesa/main/vdpau.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/mesa/ma
Am 14.06.2017 um 17:34 schrieb Emil Velikov:
On 14 June 2017 at 15:21, Christian König <deathsim...@vodafone.de> wrote:
Am 14.06.2017 um 15:40 schrieb Namburu, Chandu-babu:
From: Chandu Babu N <cha...@amd.com>
As encode support is added along with decode,
now max_entrypo
Am 14.06.2017 um 15:40 schrieb Namburu, Chandu-babu:
From: Chandu Babu N <cha...@amd.com>
As encode support is added along with decode,
now max_entrypoints are two.
vaMaxNumEntrypoints will return correct value.
Signed-off-by: Chandu Babu N <cha...@amd.com>
Reviewed-by: Chr
From: Christian König <christian.koe...@amd.com>
BOs larger than the minimum fragment size should have their VA
alignet to at least the fragment size for optimal performance.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/amd/common/ac_gpu_info.c
Am 05.05.2017 um 14:11 schrieb Emil Velikov:
On 5 May 2017 at 12:37, Christian König <christian.koe...@amd.com> wrote:
Am 05.05.2017 um 13:23 schrieb Emil Velikov:
On 5 May 2017 at 10:30, Christian König <christian.koe...@amd.com> wrote:
Am 04.05.2017 um 18:33 schrieb Emil Ve
Am 04.05.2017 um 18:33 schrieb Emil Velikov:
From: Emil Velikov <emil.veli...@collabora.com>
Cc: Christian König <christian.koe...@amd.com>
Signed-off-by: Emil Velikov <emil.veli...@collabora.com>
---
UNTESTED.
Looks sane to me, but what bothers me a bit is that it is un
Am 05.05.2017 um 13:23 schrieb Emil Velikov:
On 5 May 2017 at 10:30, Christian König <christian.koe...@amd.com> wrote:
Am 04.05.2017 um 18:33 schrieb Emil Velikov:
From: Emil Velikov <emil.veli...@collabora.com>
Provide a dummy stub when the user has opted w/o said platform, thus
Patches #13 - #17 are Reviewed-by: Christian König
<christian.koe...@amd.com>, but I need to take a closer look at the rest.
BTW: Can you send and commit those minor cleanups separately the next time?
Makes live much easier to have the trivial stuff in master there is
autohell or other non
he two.
Cc: Leo Liu <leo@amd.com>
Cc: "Guttula, Suresh" <suresh.gutt...@amd.com>
Cc: mesa-sta...@lists.freedesktop.org
Cc: Christian König <christian.koe...@amd.com>
Signed-off-by: Emil Velikov <emil.veli...@collabora.com>
---
Christian, others
How do you feel abou
Am 25.04.2017 um 15:17 schrieb Ilia Mirkin:
[SNIP]
Is there a patch I should test?
Patch is attached, but only compile tested.
Basically if OpenGL/VDPAU interop worked before with Kodi/MPV it should
still keep working.
Christian.
-ilia
>From
Am 21.04.2017 um 15:38 schrieb Emil Velikov:
On 21 April 2017 at 13:31, Christian König <deathsim...@vodafone.de> wrote:
Am 21.04.2017 um 14:11 schrieb Emil Velikov:
Both headers are used everywhere, plus they both provide interop
mechanism.
Since they define [consecutive] VDPAU driver
: Christian König <christian.koe...@amd.com>
Signed-off-by: Emil Velikov <emil.l.veli...@gmail.com>
NAK, the seperation is intentional. vdpau_interop.h is the old one we
sooner or later want to remove.
And vdpau_dmabuf.h is the new one we want to keep.
Regards,
Christian.
---
src/gal
f libvdpau.
With this commit we effectively revert "st/vdpau: move FormatRGBAToPipe
into the interop"
Cc: Christian König <christian.koe...@amd.com>
Signed-off-by: Emil Velikov <emil.l.veli...@gmail.com>
NAK, that would break DMA-buf based interop since we need R8, R8G8 a
Am 05.04.2017 um 15:46 schrieb Alex Deucher:
Cc: 13.0 17.0 <mesa-sta...@lists.freedesktop.org>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
include/pci_ids/radeonsi_pci_ids.h | 1 +
1 file changed, 1
.
Regards,
Christian.
As it stands with cabac on I can make (what I think is) a perfectly
legal stream with ffmpeg or gstreamer (ignoring current mesa issue).
... -c:v h264_vaapi -profile:v 77 -bf 0 ...
... max-bframes=0 ! video/x-h264, profile=main ...
Christian König wrote:
Am 04.04.2017
Am 04.04.2017 um 17:38 schrieb boyuan.zh...@amd.com:
From: Boyuan Zhang <boyuan.zh...@amd.com>
Signed-off-by: Boyuan Zhang <boyuan.zh...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_video.c | 2 +-
1 file ch
: 17.0 <mesa-sta...@lists.freedesktop.org>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/targets/omx/omx.sym | 5 +
src/gallium/targets/pipe-loader/pipe.sym | 5 +
src/gallium/targets/va/va.sym| 5 +
3 files changed,
Am 03.04.2017 um 06:35 schrieb Shaleen Jain:
---
src/gallium/state_trackers/omx/vid_dec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/state_trackers/omx/vid_dec.c
b/src/gallium/state_trackers/omx/vid_dec.c
index 9a6efb8e28..94664eba04 100644
---
Am 23.03.2017 um 15:35 schrieb Leo Liu:
Workaround an unknown bug with inside the transfer_map for certain
ASIC, also tested with un-affected ASICs, the performance actually
improved slightly.
Signed-off-by: Leo Liu <leo@amd.com>
Reviewed-by: Christian König <christian.koe..
Am 20.03.2017 um 23:42 schrieb Marek Olšák:
Hi,
This is initial Vega10 support for radeonsi. It supports everything
except geometry shaders and tessellation, so it's limited to GL 3.1.
The missing features are under way.
There is also UVD and VCE support.
The first 57 patches only update
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu <leo@amd.com>
Signed-off-by: Leo Liu <leo@amd.com>
Ah, here it is. This one and the change to version 53.17 should be
squashed with the change to 53.14.
With that done the patch is Reviewed-by: Chr
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu
Signed-off-by: Leo Liu
Acked-by: Alex Deucher
Did we ever released 53.14.4? My last status was the firmware on release
should be 53.17 or something like that.
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu <leo@amd.com>
Signed-off-by: Leo Liu <leo@amd.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/rad
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu <leo@amd.com>
As required by firmware
Signed-off-by: Leo Liu <leo@amd.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
sr
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu <leo@amd.com>
Signed-off-by: Leo Liu <leo@amd.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/r600/r600_uv
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu <leo@amd.com>
Signed-off-by: Leo Liu <leo@amd.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/
vpp and before maping va buffers to GL.
I suggest to keep it simple from a driver perspective and require
applications to use vaSyncSurface
*Gesendet:* Sonntag, 19. März 2017 um 15:28 Uhr
*Von:* "Christian König" <deathsim...@vodafone.de>
*An:* "Peter Frühberger" <
specific.
What do you think?
Best regards
Peter
2017-03-19 14:49 GMT+01:00 Christian König <deathsim...@vodafone.de
<mailto:deathsim...@vodafone.de>>:
Hi Peter,
Adding Michel and Marek for the Mesa interop side and Harry for
the display side.
How do you want u
he underlying type of hardware/driver.
Regards,
Rainer
*Gesendet:* Mittwoch, 08. März 2017 um 13:29 Uhr
*Von:* "Christian König" <deathsim...@vodafone.de
<mailto:deathsim...@vodafone.de>>
*An:* mesa-dev@lists.freedesktop.org
<mailto:mesa-dev@lis
Am 13.03.2017 um 12:48 schrieb Emil Velikov:
On 13 March 2017 at 11:47, Christian König <deathsim...@vodafone.de> wrote:
Am 13.03.2017 um 11:33 schrieb Emil Velikov:
Hi Christian,
On 8 March 2017 at 12:29, Christian König <deathsim...@vodafone.de> wrote:
From: Christian König &l
Am 13.03.2017 um 11:33 schrieb Emil Velikov:
Hi Christian,
On 8 March 2017 at 12:29, Christian König <deathsim...@vodafone.de> wrote:
From: Christian König <christian.koe...@amd.com>
Same layout as NV12, but 16bit per channel instead of 8.
--- a/src/gallium/include/pipe/p_format
From: Christian König <christian.koe...@amd.com>
Fix for "gallium: add P016 format".
---
src/gallium/drivers/svga/svga_format.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/svga/svga_format.c
b/src/gallium/drivers/svga/svga_format.c
index 948b276
Am 09.03.2017 um 13:46 schrieb Mark Thompson:
On 09/03/17 07:54, Christian König wrote:
Replaying here from the comment in your other mail as well:
Um, libav* is querying the capabilities and finding that only 8-bit output is
supported for Main10:
[SNIP]
Unable to create config to test
From: Christian König <christian.koe...@amd.com>
This makes debugging of decoding problems quite a bit easier.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 39 +
1 file changed, 35 inse
From: Christian König <christian.koe...@amd.com>
No hardware I know off can actually support P010 natively. But we can easily
support P016 and as long as nobody decodes anything into the lower 6bits it
doesn't make any difference to P010.
v2: allow P0160 for post processing as well
Sign
From: Christian König <christian.koe...@amd.com>
Just use whatever the state tracker allocated.
v2: fix msb mode
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_uvd.c | 17 ++---
src/gallium/drivers/radeon/radeon_
From: Christian König <christian.koe...@amd.com>
No need to have that twice.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 52 +
1 file changed, 27 insertions(+), 25 deletions(-)
diff --git a
From: Christian König <christian.koe...@amd.com>
Just simply the description of the planes.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/auxiliary/vl/vl_video_buffer.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/gallium/
From: Christian König <christian.koe...@amd.com>
We support P010 and P016 as targets for 10bpp video decoding.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 24 +++-
1 file changed, 15 insertions(+),
From: Christian König <christian.koe...@amd.com>
The firmware expects the value in pixel not bytes. Didn't made a difference
so far because we only used 8bpp surfaces.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_uvd.c | 2 +-
1 fil
From: Christian König <christian.koe...@amd.com>
Same layout as NV12, but 16bit per channel instead of 8.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/auxiliary/util/u_format.csv | 2 ++
src/gallium/auxiliary/util/u_format_yuv.c | 19
From: Christian König <christian.koe...@amd.com>
Advertise 10bpp support if the driver supports decoding to a P016 surface.
v2: Advertise 10bpp for the decoder as well.
Signed-off-by: Christian König <christian.koe...@amd.com>
Signed-off-by: Mark Thompson <s...@jkqxz.net>
objections merging that into my original
patch and adding your signed-of-by line?
Thanks for the help,
Christian.
Am 08.03.2017 um 22:36 schrieb Mark Thompson:
On 08/03/17 21:32, Mark Thompson wrote:
On 08/03/17 12:29, Christian König wrote:
From: Christian König <christian.koe...@amd.
From: Christian König <christian.koe...@amd.com>
This makes debugging of decoding problems quite a bit easier.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 39 +
1 file changed, 35 inse
From: Christian König <christian.koe...@amd.com>
Advertise 10bpp support if the driver supports decoding to a P016 surface.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/config.c | 15 +--
src/gallium/state_trackers/va/
From: Christian König <christian.koe...@amd.com>
No hardware I know off can actually support P010 natively. But we can easily
support P016 and as long as nobody decodes anything into the lower 6bits it
doesn't make any difference to P010.
Signed-off-by: Christian König <christian.koe..
From: Christian König <christian.koe...@amd.com>
The firmware expects the value in pixel not bytes. Didn't made a difference
so far because we only used 8bpp surfaces.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_uvd.c | 2 +-
1 fil
From: Christian König <christian.koe...@amd.com>
That allows us to switch between different
surface formats for different codecs.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/vdpau/decode.c | 11 ++-
1 file changed, 6 inse
From: Christian König <christian.koe...@amd.com>
We support P010 and P016 as targets for 10bpp video decoding.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 24 +++-
1 file changed, 15 insertions(+),
Hi guys,
I finally found time testing this and hammering out (hopefully) all the
remaining bugs. Playing a 10bit HEVC file through VAAPI with mpv/ffmpeg git
master from about two days ago now works flawlessly and has only about 15% CPU
load on one core on a Kaveri system.
The VDPAU path should
From: Christian König <christian.koe...@amd.com>
No need to have that twice.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 52 +
1 file changed, 27 insertions(+), 25 deletions(-)
diff --git a
From: Christian König <christian.koe...@amd.com>
That should make it possible to use the 16bit surfaces in OpenGL as well.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/include/state_tracker/vdpau_dmabuf.h | 2 ++
src/gallium/include/state_tracker/v
From: Christian König <christian.koe...@amd.com>
Just use whatever the state tracker allocated.
v2: fix msb mode
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/drivers/radeon/radeon_uvd.c | 17 ++---
src/gallium/drivers/radeon/radeon_
From: Christian König <christian.koe...@amd.com>
Same layout as NV12, but 16bit per channel instead of 8.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/auxiliary/util/u_format.csv | 2 ++
src/gallium/auxiliary/util/u_format_yuv.c | 19
From: Christian König <christian.koe...@amd.com>
Just simply the description of the planes.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/auxiliary/vl/vl_video_buffer.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/gallium/
From: Christian König <christian.koe...@amd.com>
No need to have that twice.
Signed-off-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/va/surface.c | 52 +
1 file changed, 27 insertions(+), 25 deletions(-)
diff --git a
output buffers are
fragments of the first frame when it is not set.
Reviewed-by: Christian König <christian.koe...@amd.com>
---
src/gallium/state_trackers/omx/vid_enc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/gallium/state_trackers/omx/vid_enc.c
b/src/g
Hi Thomas,
Am 02.03.2017 um 21:00 schrieb Thomas Hellstrom:
This patch series introduces a postprocessor abstraction. It could be promoted
to a gallium interface but for now it's implemented as a utility.
Well, first of all use a gallium interface for this. Putting this into
utility doesn't
deinterlacing.
Signed-off-by: Mark Thompson <s...@jkqxz.net>
That explains a couple of things, thanks for looking into it.
Patch is Reviewed-by: Christian König <christian.koe...@amd.com>.
Regards,
Christian.
---
src/gallium/state_trackers/va/postproc.c | 10 +-
src/gallium/state
Am 24.02.2017 um 15:40 schrieb Thomas Hellstrom:
Hi, Christian!
Are you OK with the updated Putbits patches?
https://lists.freedesktop.org/archives/mesa-dev/2017-February/145269.html
https://lists.freedesktop.org/archives/mesa-dev/2017-February/145258.html
Sorry the second patch never made
König <cthristian.koe...@amd.com>
Signed-off-by: Thomas Hellstrom <thellst...@vmware.com>
Acked-by: Christian König <christian.koe...@amd.com> for both patches.
---
src/gallium/auxiliary/util/u_video.h | 42 +
src/gallium/state_trackers/vdpau/query.c | 13 +
Am 22.02.2017 um 18:05 schrieb Thomas Hellstrom:
On 02/22/2017 05:54 PM, Christian König wrote:
Am 22.02.2017 um 17:23 schrieb Thomas Hellstrom:
On 02/22/2017 04:46 PM, Christian König wrote:
Am 22.02.2017 um 16:31 schrieb Thomas Hellstrom:
On 02/22/2017 04:00 PM, Emil Velikov wrote:
On 22
Am 22.02.2017 um 17:23 schrieb Thomas Hellstrom:
On 02/22/2017 04:46 PM, Christian König wrote:
Am 22.02.2017 um 16:31 schrieb Thomas Hellstrom:
On 02/22/2017 04:00 PM, Emil Velikov wrote:
On 22 February 2017 at 09:30, Thomas Hellstrom
<thellst...@vmware.com> wrote:
On 02/22/2017 09
Am 22.02.2017 um 16:31 schrieb Thomas Hellstrom:
On 02/22/2017 04:00 PM, Emil Velikov wrote:
On 22 February 2017 at 09:30, Thomas Hellstrom <thellst...@vmware.com> wrote:
On 02/22/2017 09:56 AM, Christian König wrote:
Am 21.02.2017 um 21:52 schrieb Thomas Hellstrom:
A couple of
Am 22.02.2017 um 14:42 schrieb Thomas Hellstrom:
mplayer likes putting YV12 data, and if there is a buffer format mismatch,
the vdpau state tracker would try to reallocate the video surface as an
YV12 surface. A virtual driver doesn't like reallocating and doesn't like YV12
surfaces, so before
Am 21.02.2017 um 21:52 schrieb Thomas Hellstrom:
A couple of fixes / improvements for things I've encountered while looking
through and testing the video code in preparation for a virtual hardware video
driver.
Reviewed-by: Christian König <christian.koe...@amd.com> for the who
le, this is most likely a bug"?
Actually I'm not sure if that is an application bug.
Trying to put a box with zero width and hight might not make much sense,
but the interface doesn't forbids that explicitly.
Anyway we need to catch this case in the state tracker and so the patch
is Reviewed-by: Chri
Am 10.02.2017 um 16:36 schrieb Nayan Deshmukh:
we anyway allow for multiple slices
v2: do not remove assert to check for buf->size
Signed-off-by: Nayan Deshmukh <nayan26deshm...@gmail.com>
Reviewed-by: Christian König <christian.koe...@amd.com>.
---
src/gallium/st
Sorry for the delay, as noted in the other mail I was on sick leave for
a while.
Am 03.02.2017 um 05:52 schrieb Nayan Deshmukh:
On Thu, Feb 2, 2017 at 3:34 PM, Christian König <deathsim...@vodafone.de> wrote:
Am 01.02.2017 um 13:59 schrieb Nayan Deshmukh:
we anyway allow for multiple
Am 01.02.2017 um 13:59 schrieb Nayan Deshmukh:
we anyway allow for multiple slices
Signed-off-by: Nayan Deshmukh
---
src/gallium/state_trackers/va/picture_mpeg12.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/gallium/state_trackers/va/picture_mpeg12.c
Am 01.02.2017 um 16:50 schrieb Thomas Hellstrom:
Hi, Again,
(No need answering while on sick leave!).
Actually I'm bored, but can't concentrate on coding when my body
temperature isn't in the normal range :(
Hui? That's not how I remembered it.
For the dma-buf part we export one layer of
Hi Thomas,
I'm on sick leave, but will try to quickly answer your questions.
But don't be disappointed if you don't hear back from me before Monday.
Am 01.02.2017 um 15:56 schrieb Thomas Hellstrom:
Hi, Christian,
I'm looking through the mesa vdpau interop code and found something that
looks
e.
Reviewed-by: Christian König <christian.koe...@amd.com> for this one as
well the mesa patch.
Regards,
Christian.
---
drivers/gpu/drm/radeon/radeon_drv.c | 3 ++-
drivers/gpu/drm/radeon/radeon_gem.c | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/r
Am 30.01.2017 um 09:17 schrieb Michel Dänzer:
On 30/01/17 12:08 AM, Andy Furniss wrote:
Christian König wrote:
That looks correct to me, but I'm not deeply enough into the H264
encoding any more.
Adding Leo and Boyuan to comment as well.
I just sent v2 to list and tried to cc Boyuan and Leo
NAK, that isn't correct.
Especially on APUs we can now use more than 256MB visible VRAM.
Christian.
Am 30.01.2017 um 01:33 schrieb Marek Olšák:
From: Marek Olšák
the value from the kernel is wrong
---
src/gallium/winsys/radeon/drm/radeon_drm_winsys.c | 2 +-
1 file
.li...@gmail.com>
---
src/gallium/state_trackers/va/picture.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
Tested, LGTM. (0.5fps works nicely now :)
Reviewed-by: Mark Thompson <s...@jkqxz.net>
Acked-by: Christian König <christian.koe...@amd.com>
Am 27.01.2017 um 20:44 schrieb Mark Thompson:
On 27/01/17 14:27, Christian König wrote:
Am 27.01.2017 um 13:51 schrieb Mark Thompson:
On 26/01/17 16:59, Christian König wrote:
[SNIP]
(For that matter, is there a list somewhere of the set of formats/layouts and
what they are used for?)
Well
Am 27.01.2017 um 13:51 schrieb Mark Thompson:
On 26/01/17 16:59, Christian König wrote:
Am 26.01.2017 um 13:14 schrieb Mark Thompson:
[SNIP]
The problem here is I need to know what will be done with the surface from the
very beginning. E.g. if you want to scan it out directly to hardware you
Reviewed-by: Christian König <christian.koe...@amd.com>.
Am 27.01.2017 um 12:02 schrieb Marek Olšák:
From: Marek Olšák <marek.ol...@amd.com>
---
src/gallium/auxiliary/vl/vl_compositor.c | 14 ++
src/gallium/auxiliary/vl/vl_compositor.h | 1 -
src/gallium/state
That looks correct to me, but I'm not deeply enough into the H264
encoding any more.
Adding Leo and Boyuan to comment as well.
Regards,
Christian.
Am 26.01.2017 um 19:26 schrieb Andy Furniss:
Tested with ffmpeg and gst-vaapi. Without this bits per
frame is set way too low.
Signed-off-by:
Am 27.01.2017 um 10:33 schrieb Samuel Pitoiset:
On 01/26/2017 12:07 PM, Christian König wrote:
Am 26.01.2017 um 12:01 schrieb Samuel Pitoiset:
On 01/26/2017 03:45 AM, Michel Dänzer wrote:
On 25/01/17 11:19 PM, Samuel Pitoiset wrote:
On 01/25/2017 03:56 AM, Michel Dänzer wrote:
On 25/01
Am 26.01.2017 um 16:59 schrieb Peter Frühberger:
2017-01-26 16:36 GMT+01:00 Christian König <deathsim...@vodafone.de
<mailto:deathsim...@vodafone.de>>:
Am 26.01.2017 um 12:16 schrieb Peter Frühberger:
Hi Christian,
2017-01-26 12:00 GMT+01:00 Christian König
Am 26.01.2017 um 13:14 schrieb Mark Thompson:
On 26/01/17 11:00, Christian König wrote:
Hi Peter,
Am 25.01.2017 um 19:45 schrieb Peter Frühberger:
Peter, Rainer any idea what I'm missing here? Do you guys use some
modified ffmpeg for Kodi or how does that work for you?
do you set
Am 26.01.2017 um 12:16 schrieb Peter Frühberger:
Hi Christian,
2017-01-26 12:00 GMT+01:00 Christian König <deathsim...@vodafone.de
<mailto:deathsim...@vodafone.de>>:
Hi Peter,
Am 25.01.2017 um 19:45 schrieb Peter Frühberger:
Peter, Rainer any idea what
Am 26.01.2017 um 12:01 schrieb Samuel Pitoiset:
On 01/26/2017 03:45 AM, Michel Dänzer wrote:
On 25/01/17 11:19 PM, Samuel Pitoiset wrote:
On 01/25/2017 03:56 AM, Michel Dänzer wrote:
On 25/01/17 12:05 AM, Marek Olšák wrote:
On Tue, Jan 24, 2017 at 2:17 PM, Christian König
<death
Hi Peter,
Am 25.01.2017 um 19:45 schrieb Peter Frühberger:
Peter, Rainer any idea what I'm missing here? Do you guys use some
modified ffmpeg for Kodi or how does that work for you?
do you set the format correctly, e.g.:
201 - 300 of 1736 matches
Mail list logo