[MPlayer-dev-eng] [PATCH] very experimenal nvidia_vid

[Dmitry Baryshkov]

В Чтв, 25.09.2003, в 20:48, Sascha Sommer пишет:
> I made the fixes you proposed and added the fourcc.
> Current solution attached.
Will test later.
> 
> >> Another problem is that it currently only support uyvy overlay and there
> >> is no yv12 -> uyvy converter. Therefore you will
> >> have to use the dll codecs or our native cyuv codecs to test it.
> >> Not talking about the missing vsync support...
> >According to DirectFB driver, you can support YV12 on archs >= NV10, by
> >using pitch|1<<16|0x00100000 on setting NV_PVIDEO_FORMAT for archs>=NV10
> >(cannot test. I have only Vanta :)
> >
> >Dunno, if using YV12 is possible for NV04, but if you change 0x011 to
>  >0x111 on line 668 (when setting NV_PVIDEO_OVERLAY (KEY_ON, VIDEO_ON,
>  >FORMAT_CCIR)), you will select yuy2 output format :) (tested)
> >
> >So uyvy isn't really problem :)
> 
> It seems planar formats are not possible for nv03. Directx always sets the
> format to YUY2 even when the app thinks it uses yv12 overlay. I think the
> card can do yv12 -> yuy2 with
> dma blits.
Maybe. Laso there is (IIRC nVidia sources from rivatv docs section) a
 memory-to-memory convertor. We can use it, but it will require BIG
 changes (supporting FIFO, hash table, etc.). There is only one plus - 
 this code exists in rivatv, and it can use PIO, so it can be done in
 userspace :)
> 
> >I see another problem: vidix API must be expanded to pass bpp to vidix
> > driver (for rivatv_overlay_colorkey). Also dunno, if BPP <15 or >24 are
> >supported by all cards. (IIRC RIVA128 didn't support even 16bpp).
> 
> It is not a problem as we can read those values directly from the card.
> I implemented it for nv03 but the registers for nv04 and later are
> different.
> Maybe the #if 0 block from rivafb helps you.
Will look at it. BTW: do you mean rivafb from rivatv, or from kernel?

> >There is another problem. I couldn't get it work with vesa:vidix and
> >fbdev:vidix. (vesa:vidix plays, but video isn't shown. trying setting
> >colorkey to r=0,g=0,b=0, uncommenting block, and trying different
> >bufferdepth's gave nothing).
> 
> fbdev:vidix works for nv03, vesa untested
will try fbdev again.
> I still didn't get the colorkeying right for xvidix. It works with the gimp
> window
> but not with window created by mplayer.
What color depth are you using? IIRC, in nv driver from X were some
  hacks with RIVA128 and 15,16 color depths. Maybe a problem is there?

> Sascha
> 
> ______________________________________________________________________
-- 
With best wishes
Dmitry Baryshkov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: ??? ????? ????????? ????????? ???????? ????????
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20030926/9b23555e/attachment.pgp>