Re: Re: V4L2 to-do list

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



On Tue, Aug 28, 2001 at 08:59:54AM +0000, Gerd Knorr wrote:
> Bill Dirks wrote:
> 
> >  + design /proc filesystem support
> 
> I'd just add some new field(s) to the existing 2.4.x procfs support
> (i.e. type2 with v4l2 capabilities, ...).

I am partially responsible for the procfs-stuff in the cpia-driver (and
not proud of it ;). For the ones that never had a look at it: it allows
to control about any aspect of the cpia-chip (color-gains, compression
targets, ... - all in all about 50 values) via writing to a
procfs-file. I _dont_ :) think something like this has much to do with
a basic v4l2 api. But I still wonder how could this be done in a better
way. Since we are talking about designing an API for the next 10 years
the question how to support such stuff in some way seems to be valid.
In other words, what is the v4l2-way to deal with hardware that has
dozens of non-standard options to control? Or is this out of scope?

-Peter

-- 
Feeling amorous, she looked under the sheets and cried, "Oh, no,
it's Microsoft!"
-------------------------------
Email: Peter_Pregler@xxxxxxxxx





[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