On Fri, 19 Jun 2009, Andy Walls wrote:
On Fri, 2009-06-19 at 12:47 -0500, Theodore Kilgore wrote:
On Fri, 19 Jun 2009, Andy Walls wrote:
On Thu, 2009-06-18 at 21:43 -0500, Theodore Kilgore wrote:
On Thu, 18 Jun 2009, Andy Walls wrote:
Interesting. To answer your question, I have no idea off the top of my
head. I do have what seems to be a similar camera. It is
Bus 005 Device 006: ID 0979:0371 Jeilin Technology Corp., Ltd
and the rest of the lsusb output looks quite similar. I do not know,
though, if it has any chance of working as a webcam. Somehow, the thought
never occurred to me back when I got the thing. I would have to hunt some
stuff down even to know if it is claimed to work as a webcam.
The packaging that mine came in claims "3-in-1":
digital video camcorder (with microphone)
digital camera
web cam
You did say that it comes up as a different USB device when it is a
webcam? You mean, a different product ID or so?
Yes
Look for this in the original lsusb output I provided
:
Webcam mode:
Bus 003 Device 005: ID 0979:0280 Jeilin Technology Corp., Ltd
Device Descriptor:
Oops, right you are. Blame it on my old eyes. They are the same age as the
rest of me, but sometimes they feel older.
And the upshot is that we may have the same camera, at least as a webcam,
perhaps with a different name. I finally made mine to work in webcam mode.
On mine, one has to press down a button labelled "DV" at the same time as
pressing down the button with the picture of a camera beside it, to turn
on the webcam mode. As opposed to just pressing the "camera" button to
turn on the camera to shoot a picture.
OK. I have two steps to take:
1. Installing the driver and software on my sole remaining Windows
machine. It already has snoopy.
2. Getting the camera away from my daughter for more than 2 minutes.
It's like the thing is glued to her hand. :)
I hope that you can still manage to do these things. I did get a snoop log
of my own, but it would be nice to have some confirmation, too, that the
cameras really are acting the same way. That may look like a stupid thing
to say until one realizes that things which have the same USB
Vendor:Product number do _not_ necessarily act the same way.
Well, here are some of the things I learned:
As a stillcam, it is confirmed that my cam is a standard mass storage
device, transparent SCSI, bulk. It uses outep 0x01 and inep 0x82 (the
first pair of endpoints).
Here it is as a mass storage device.
T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0979 ProdID=0371 Rev= 1.00
S: Manufacturer=Jeilin
S: Product=USB 1.1 Device
S: SerialNumber=09790
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 4 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms
and here it is as a webcam.
T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 16 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0979 ProdID=0280 Rev= 1.00
S: Manufacturer=Jeilin
S: Product=USB 1.1 Device
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 4 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms
Now it is using the other pair of endpoints, 0x03 and 0x84.
There is a sequence of init commands
00000000: 71 81
00000000: 70 05
00000000: 95 70
00000000: 00 (all the 00 are responses)
00000000: 71 81
00000000: 70 04
00000000: 95 70
00000000: 00
00000000: 71 00
00000000: 70 08
00000000: 95 70
00000000: 00
00000000: 94 02
00000000: de 24
00000000: 94 02
00000000: dd f0
00000000: 94 02
00000000: e3 2c
00000000: 94 02
00000000: e4 00
00000000: 94 02
00000000: e5 00
00000000: e5 00
00000000: 94 02
00000000: e6 2c
00000000: 94 03
00000000: aa 00
00000000: 71 1e
00000000: 70 06
00000000: 71 80
00000000: 70 07
and then it starts to stream. The stream downloads 0x200 (512) bytes at a
time. It appears that there is an SOF marker consisting of
ff ff ff ff
followed by at least two zeroes. These seem to occur only at the
beginnings of some of the downloaded 0x200-sized blocks.
There is a closing sequence at the end which is similar to the init
sequence
00000000: 71 00
00000000: 70 09
00000000: 71 80
00000000: 70 05
It would be interesting to see your log file and to compare. I could also
send you this one if you are curious, but it is 5,760,902 bytes so I
should ask that if you want to see it then how to send it? Me, I suspect
that if you have one of similar size and bz2 it and send it to me as an
attachment, then it is not any problem.
Now, having found an excuse not to finish grading those papers today, I
will probably have to pay more concentrated attention to grading and
travel planning tomorrow. But do send the log along anyway if you can get
it done.
Theodore Kilgore
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
