Hi,
2008/7/7 Sam Liddicott <[EMAIL PROTECTED]>:
> I've been following this mailing list generally and observing progress.
>
> Because I'm spread too thin to contribute technically, I started a
> bounty page at:
> http://www.liddicott.com/~sam/?p=76<http://www.liddicott.com/%7Esam/?p=76>
>
> After a year, this has reached about $770 dollars for the developers.
>
> Please could I ask one or a few of the developers who would have an
> interest in claiming the bounty to identify themselves (in response or
> via private email or as a blog comment) and give a short statement on
> what work they think there is left to do.
I'm interested in claiming (and sharing) the bounty once the kernel driver
hits mainline.
I don't think it's going to be a m560x driver but a m5602 and a m5603 as
they differ too greatly from each other.
Thus you may need to explicitly state if this bounty is for the m5602 or
m5603 or to be shared between them.
I myself have only been working with the m5602 but the situation is quite
complicated due to that there are no datasheets or information on how the
m5602 usb bridge works.
Couple this together with that there are at least three different sensors
(Omnivision ov9650, Samsung S5K83A, Micron MT9V111) used together with the
chip, all requiring different initializations and where there are no
datasheets for the s5k83a. Additionally different notebook vendors (MSI,
Acer, Packard Bell, Acer, Clevo) use the same bridge and sensor but with
different initializations in some unknown scheme.
Finally, the windows driver is braindead only setting one pixelformat
(Bayer-encoding) with a fixed resolution (VGA) making it almost impossible
to reverse-engineer the windows driver all operations like resizing and
color recovery seems to be made in software.
To answer your question:
"When will it hit mainline?", my answer is that I don't know.
I intend to try to sort out all the different variations in sensors and
vendor specific implementations and commit something that at least is giving
some kind of basic support for all known sensors.
But the reality is that without any datasheet or a contact inside ALi
wanting to answer our questions the driver is always going to be limited in
respect to picture quality and pixel format support.
A small comfort is that most of all new webcam chips designed nowadays
adhear to the usb video class specification and should work out of the box
with the uvc driver so the next laptop you buy will probably have
webcam-support out of the box.
Regards,
Erik
>
>
> I intend to combine the statements of work and post it on the bounty
> page as an update.
>
> If key developers don't have an interest in the bounty, please also let
> me know.
>
> Sam
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> M560x-driver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
