Andy Furniss wrote:
Andy Furniss wrote:
Grigori Goronzy wrote:
On 02.07.2014 22:18, Andy Furniss wrote:
Before I knew how to get field sync to use my TVs deinterlacer I had to
modify mesa so that I could use the vdpau de-interlacer(s), when I did
this I noticed that 422 didn't work and looked the same as it does now
this has gone in with my si.
Are you trying to use the temporal deinterlacer with 4:2:2? Sorry, that
isn't implemented yet! The temporal deinterlacer pass always outputs
4:2:0.
No, I am not using the deinterlacer.
I also just noticed I am getting below probably 1/frame when playing
422, I am using mplayer software decode.
[25491.054338] VM fault (0x00, vmid 0) at page 0, read from unknown (0)
[25491.054341] radeon 0000:01:00.0: GPU fault detected: 146 0x06031014
[25491.054342] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[25491.054343] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
Maybe not 1/frame but anyway the first couple of a run have numbers
rather than 0000s
[27977.386795] radeon 0000:01:00.0: GPU fault detected: 146 0x0c035014
[27977.386800] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x000015E0
[27977.386802] radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03050014
[27977.386804] VM fault (0x04, vmid 1) at page 5600, write from CB (80)
[27977.386841] radeon 0000:01:00.0: GPU fault detected: 146 0x0c03e014
[27977.386842] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x000015E0
[27977.386844] radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030E0014
[27977.386846] VM fault (0x04, vmid 1) at page 5600, write from CB (224)
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
