Martin,
No, sorry, the information which Marcus Meissner needs, is here.
Marcus,
This is what Martin used in order to get the camera to work. The
Vendor:Product number is based upon the output of lsusb -v, which Martin
previously posted to me and to the sane-devel list. So at this point it
looks to me as though we knocked down another one.
Cheers,
Theodore Kilgore
On Wed, 14 Sep 2005, Martin wrote:
> I installed libgphoto2-2.1.6.
>
> Edited the source file pdc640.c in the directory,
> libgphoto2-2.1.6/camlibs/polaroid/
>
> and added the lines,
>
> {"Clever CAM 360", 0x797, 0x8001, {
> jd350e,
> BAYER_TILE_BGGR,
> &jd350e_postprocessing_and_flip,
> "scope%04i.ppm"
> }
> },
>
> which is similar to the lines already there for,
> {"GrandTek ScopeCam", 0x797, 0x801c, {
> jd350e,
> BAYER_TILE_BGGR,
> &jd350e_postprocessing_and_flip,
> "scope%04i.ppm"
> }
> },
>
>
> and did a make and make install.
>
> What is the method to test this to see if I can gain access to the pictures
> in the camera?
> Thanks,
> -Martin
>
>
> kilg...@banach.math.auburn.edu wrote:
>
>>
>>
>> On Tue, 13 Sep 2005, Martin wrote:
>>
>>> I don't have this folder on my system, libgphoto2/camlibs/
>>>
>>> Does something have to be installed to have it?
>>>
>>
>> Well, yes. You need to go to gphoto.org and click on download, which will
>> take you to the actual project page. There, you will have a couple of
>> choices. Either you can download the libgphoto2-2.1.6 source tarball, or
>> you should download the CVS tree for ligphoto2, which reflects the daily
>> updates of the developers. I would say it is always better to get the CVS
>> tree in a situation like this, but then there is an extra step for
>> compiling.
>>
>
