Sascha Volkenandt wrote:
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).
Teemu
On Mon, 2005-04-18 at 23:49 +0300, Rantanen Teemu wrote:
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 wrote:
I seriously doubt that dxr3 driver developers are unaware of this. According to this datasheet the em8400 is capable of a full 256 colors OSD. Btw: http://sourceforge.net/mailarchive/message.php?msg_id=9640995 no follow-ups.
Bye
On Tue, 2005-04-19 at 00:28 +0200, Luca Olivetti wrote:
Probably. I also dont understand why no dxr3 developer have tried to tackle the x-card. They have the dxr3 to build on, there's more documentation available, and there's even a binary linux driver which could be tried to reverse engineer.
-
Luca Olivetti -
Rantanen Teemu -
Torgeir Veimo