Benjamin Forgeau wrote:
Another thing, there is no "version.h" in the kernel include

files.
Why?? Will it disappear??
This one was omitted by accident, I sent it again to Alan Cox. You should find it in the kernel release which includes the next patchset.

Ok, but what is the purpose of it? Pre-compiled programs won't have the chance to determine the version of the API then (an old debate I think). If the purpose is to determine the name of the right device, it is strange to have it in the kernel, because either you use a devfs, and then the names are ok, or you use (ok, in the future) a file system set up by a linux distribution, and I don't know why the names should be in the old fashion.
Right now the changes were never binary compatible in any way, so you had to determine the DVB API version at compile time.

In the next API version we'll add an info ioctl to determine the version at runtime, too.


And what is the status of OSD in the future releases?? There is a remark in the help message saying that it may not be supported

later.

That's correct. Don't rely on it - this interface is very tight bound
to
the AV7110 based DVB cards. Use e.g. DirectFB, SDL, XRender or any
other
portable graphics API when you create a DVB video application.

I don't quite understand. So you mean we have to forget about OSD???
All applications that use it right now should be extended to allow output via DirectFB, XRender, whatever.


Or a Frame Buffer device will come in the near future for OSD??
no, that's unfortunally not possible.


By the way, maybe I missed something, but what is the status of sending raw data to the DVB display (you, know, in order to see DivX films on the DVB tv-out)??
impossible for AV7110 based cards, too.

Holger



--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.

Reply via email to