I've been forgetting about this project. I've installed a later version of suse now, and hopefully will move out and get a fast internet connection so i won't be held back by 25 meg kernel downloads that took two hours to download only to discover it's corrupted.
When i've settled in there (and preferably assembled my cam again) i'll get to some work. Uni work is mostly under control now so i should have enough time, bandwidth and possibly frame of mind soon:)
My ISP is being completely random. All connectections can drop out at any point. It seems ssh has some recovery, it actully allows me 'bout twenty seconds of typing before it stops for a couple of minutes..
I guess i'll have to work/update from uni.
Just so you know.
Well, we've got some action going on again after a deserved kick in the hind regions. The project webpage is also now in use, it'll probably be a useful center of information besides the mailing list.
most of it seems to be handled by the winbond chip. The exception is the brightness settings and such things. Look for `sccb' in the ov specs and for section 7.1.1 in the winbond specs if you want to figure out how exactly this works.
..at least, i think. I can't be sure without doing my PhD on administering a project on sourceforge, you know...
What i'm trying to say is: ``they should appear''.
Progress is being made. Mr. keatch (the other admin) is currently working on the transfer and v4l code.. And another potential programmer contacted us. We're all wayting for keatch to work his magic on the code right now:)
Heh.. oops. I kind of forgot about this page..
Okay, status:
The first person i gave my code to has started his own project here - see it at http://sourceforge.net/projects/lingo/
The second person I gave my code to might join this project, or the other one, who knows.. I'll talk to them.
Since I handed the the first person I gave to code to the code because I was to busy, i don't actually know the status just yet. I also lost his email addy and only just found it again.. Before I found it, i started coding a little more myself.... read more
whee... it's not kernel oopsing anymore.. Currently writing and tweaking the vide4linux code, which is most of the work to be done before this'll start working.
While the main chip of the Webcam Go has its full specs released, the microcontroller (which is a Creative chip) isn't. I've asked Creative about it but haven't yet gotten a reply - it's possible I may write that part of the driver in the future - right now i'm actually not even sure what the interface to that would be - not video4linux, not really.
-ish. What I've got working is nearly zilch, but I've got a lot of stuff, half the driver perhaps, that will instantly work when the stuff i'm working on does too. Expect some releases in, say, two or three weeks, less if uni isn't too annoying...