On Sat, Jun 01, 2002 at 11:23:47AM -0700, Dmitri wrote:
> On Wed, 2002-05-29 at 20:58, an unknown sender wrote:
>
> > I am considering beginning a project to write a driver for the ProScope
> > sold by Bodelin here in the US.
>
> > The ProScope appears to use the Divio Prolink chipset, at least from
> > what I can decypher from looking at the debug info from the kernel.
> > (With USB verbose debug option)
>
> Is the chipset supported by any existing driver? If not, is there any
> active project to write one? You don't want to start coding until you
> find that out.
>
To the best of my knowledge, no. I have made a pretty extensive online
search, but that was passive, this is my first active move. The chipset
is listed as unsupported, and I can find no evidence of existing
projects. Which sucks, as I am way lazy...
> > I may be able to get access to info on
> > this device, and can get the device itself from the sales manager for
> > the company, since he's a neighbour of mine here at the marina :)
> > Anyway. I am new to device drivers, and especialy new to USB stuff so
> > would appreciate any and all info I can get on what path to persue.
>
> You need the programmer's manual on the chipset, with detailed
> description of how to control the camera and how to decode the data.
> Until you have it, there is not much to discuss.
That's what I am in the process of doing now. I have an email exchange
going between the manuf of the device, me and the local distributor. The
chipset is a buyout of course, and what I really need is the manual for
that. The proscope itself is basically a rather clever repackage of the
basic system. The replaceable lenses make it particularly useful
however, and the price *at ~$200) is nice too.
>
> > I
> > was thinking about starting with one of the other Camera drivers and
> > using it as a base to get my feet wet as it were. Any suggestions as to
> > which one? I don't yet know for sure, what driver to start with. The
> > device doesn't respond to any of the existing drivers (duh!) Help?
>
> The device may not "respond" to existing drivers just because it has
> different ProductID and VendorID, they are supposed to be
> vendor-dependent. There are many cameras on the market that use the same
> chipset (and the same driver) but have unique identification (due to
> legal requirements).
>
> If you have to write a driver, you probably want to create a minidriver
> for usbvideo. Several camera drivers are written this way. Look in
> linux/drivers/usb/ for details. Then you don't need to deal with V4L
> interface.
Thanks a lot, I will do this. Like I said,I am basically clueless, with
a desire to do and learn. (unfortunately, it's rarely in that order...)
--
Jim Richardson
Anarchist, pagan and proud of it
http://www.eskimo.com/~warlock
Linux, from watches to supercomputers, for grandmas and geeks.
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
