Re: v4l2 api

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



> >... which clearly indicates it is indeed redundant.  At least for TV
> >cards, what about usb webcams?

>  That reminds me, how should (digital) USB webcams implement 
>  VIDIOC_ENUMSTD?  Should they set std.id = V4L2_STD_UNKNOWN? Should they 
>  just return -EINVAL? Or should we have have a V4L2_STD_DIGITAL_CAM for 
>  devices where modulation standards and fixed frame rates don't apply?

Just returning -EINVAL looks fine to me.

>  And to answer your question, with USB webcams you cannot infer the 
>  timeperframe from any other fields in the V4L(2) API.

Ok, then lets keep it.

>  Oh, and speaking of digital things, will there be V4L2_STD #defines for 
>  the various digital broadcast standards? Or should we create a new ioctl 
>  for that?

What exactly do you have in mind?

HDTV?  Probably.  Which ones we need?

DVB?  Don't think so, there is a API for dvb already.

Others?

  Gerd

-- 
You can't please everybody.  And usually if you _try_ to please
everybody, the end result is one big mess.
				-- Linus Torvalds, 2002-04-20





[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