matthieu castet wrote:
Maybe v4l should do something like alsa and provide an userspace
library that will hide the hardware specific stuff.
For example I know there is alsa plugin that emulate mixer for
hardware that miss it.
That would be the way if it is common to all cameras so programs like
Motion only has to support a few standard APIs.
But how would all the different camera drivers be able to support one
common userland library? Alsa is one project that supports many sound
devices as I understand it. But camera drivers are any small projects
that all (almost) conforms to either V4L or V4L2 API. How will ONE
library be made? And has anyone taken this initiative and committed to
maintain it? Sounds like a full time job.
How does Motion support SN9C10x ?
From what I saw sn9c102 driver only export privates formats
V4L2_PIX_FMT_SN9C10X and V4L2_PIX_FMT_SBGGR8.
It probably does not. A guy started working on V4L2 support in Motion
but has not finished the job because of his job + family stuff.
So if anyone feels like helping the Motion project with V4L2 support
when be very welcome to submit a patch on the Motion TWiki (same site as
the PWC wiki).
Kenneth
--
Kenneth Lavrsen,
Glostrup, Denmark
[EMAIL PROTECTED]
Home Page - http://www.lavrsen.dk
_______________________________________________
pwc mailing list
[email protected]
http://lists.saillard.org/mailman/listinfo/pwc
