Looks fine.
Applied to stage/sunxi-3.4.
tor 2014-07-03 klockan 13:28 +0200 skrev Andreas Baierl:
> G2D seems to break if a zero value of src_rect.w or src_rect.h is
> provided to g2d_blit, g2d_fill or g2d_stretchblit.
> para.src_rect.w == 0 or para.src_rect.h == 0 results in trying to write
>
G2D seems to break if a zero value of src_rect.w or src_rect.h is
provided to g2d_blit, g2d_fill or g2d_stretchblit.
para.src_rect.w == 0 or para.src_rect.h == 0 results in trying to write
-1 toG2D_DMA0_SIZE_REG register within the mixer_* functions, e.g. here
https://github.com/linux-sunxi/linu
For testing purposes, setting timeout=500 has the effect, that OSD stops
flickering, but instead of the correct image, only a black area with OSD
dimensions is displayed.
"wait g2d irq pending flag timeout" still is there.
I also applied
https://github.com/amery/linux-sunxi/commit/7015bbb75ac57
On Wed, 05 Mar 2014 20:32:42 +0100
Andreas Baierl wrote:
> Am 04.03.2014 11:56, schrieb Andreas Baierl:
> > Hi all,
> > it seems, that the G2D kernel driver has some issue:
> >
> > libvdpau-sunxi uses G2D_CMD_BITBLT for creating surfaces, so at the
> > end of mixer_blt, there is g2d_wait_cmd_fin
Am 04.03.2014 11:56, schrieb Andreas Baierl:
Hi all,
it seems, that the G2D kernel driver has some issue:
libvdpau-sunxi uses G2D_CMD_BITBLT for creating surfaces, so at the
end of mixer_blt, there is g2d_wait_cmd_finish() called.
As soon as (timeout==0) gets TRUE in
https://github.com/linux-s
Hi all,
it seems, that the G2D kernel driver has some issue:
libvdpau-sunxi uses G2D_CMD_BITBLT for creating surfaces, so at the end
of mixer_blt, there is g2d_wait_cmd_finish() called.
As soon as (timeout==0) gets TRUE in
https://github.com/linux-sunxi/linux-sunxi/blob/sunxi-3.4/drivers/char/s
