Improving DXR3 OSD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2005-04-18 at 23:49 +0300, Rantanen Teemu wrote:
> Sascha Volkenandt wrote:
> > I remember following that idea quite well, and from
> > what I know, they never figured out how to create
> > an interrupt after a frame transfer is complete. So 
> > it never got beyond polling and experimental guessing :-(
> 
> Yes... But what I was really after was to do the same thing for the OSD
> data. The amount of OSD data is a lot less then for the video, and you
> could make assumptions (like 10x) for the time it will take to transfer
> it, and it still wouldn't be a problem.
> 
> But, as far as I know, this hasn't been tested, and I don't know if it's
> possible (depends on the internal method dxr3 uses to create the osd).

Maybe the databook for the em8400 can shed some light on it? It should
be just an advanced version of the em8300. See

http://www.google.co.uk/search?q=em840x10a.pdf

-- 
Torgeir Veimo <torgeir@xxxxxxxxx>




[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux