Thread (7 messages) 7 messages, 5 authors, 2008-03-04

Re: [RFC] move sensor control out of kernel

From: Guennadi Liakhovetski <hidden>
Date: 2008-02-29 23:10:24

On Fri, 29 Feb 2008, eric miao wrote:
The soc-camera is pretty good. Yet it doesn't solve the issue of
complicated sensor control. mt9m001.c and mt9v022.c are two
good examples, but are all too simple. I have a sensor driver here
with more than 4000 lines of code.
mt9xxxx drivers also only implement a subset of camera capabilities. The 
approach taken with these two drivers was to implement a minimal 
functional control subset in the kernel, so that "standard" user-space 
applications like xawtv, mplayer, etc. can work with them out of the box, 
and provide access to camera registers over the .get_register / 
.set_register interface for applications requiring finer camera tuning. It 
has disadvantages, of course. But it avoids kernel bloat, nevertheless 
providing reasonable functionality, reduces (kernel) development costs, 
etc. Maybe this interface should be made standard and at least removed 
from under #ifdef CONFIG_VIDEO_ADV_DEBUG?

Thanks
Guennadi
---
Guennadi Liakhovetski

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help