Re: Frame buffer memory management V4L API considerations

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



Bill Dirks wrote:

These funtions are only used by the X server modules, not the user
application, right? And v4l/V4L2 driver and X driver need to be designed
and maintained "together" anyway. So just add whatever ioctl functions
for the communication between X and the Video for Linux kernel driver
you need for your system.

Actually, my app doesn't do anything in X... it uses the framebuffer directly.

Where I see the importance for V4L/2 to maintain compatibility with X, I hope it doesn't become so tightly integrated that non-X apps won't work. Likewise, we shouldn't be afraid of duplicating, in V4L/2, video functionality available in X, as not all video apps have X available.

Chris





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux