Trust Mobile Spycam 100

I got hold of a Trust Mobile Spycam 100, see also

Of course, a driver for Linux is nowhere to be found. lsusb gives the following output:

    [bart@room ~]$ lsusb
    Bus 004 Device 001: ID 0000:0000
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 004: ID 0979:0224 Jeilin Technology Corp., Ltd
    Bus 002 Device 002: ID 03f0:1204 Hewlett-Packard DeskJet 930c
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 001: ID 0000:0000

Using the -vv switch lsusbvv revealed more.
However, Gphoto doesn't tell me anything:

    [bart@room ~]$ gphoto2 --list-ports
    Devices found: 1
    Path                             Description
    usb:                             Universal Serial Bus
    [bart@room ~]$ gphoto2 --auto-detect
    Model                          Port
    [bart@room ~]$

I've opened the cam and tried to read the letters/numbers on the biggest
IC. It's hard to read, but seems to say:


I've found that there is also an (older?) "plus" version, but the product
number is different: 12728. I haven't got that one, so no specifics for
that one.

Gerard Klaver mentioned the following things:

  1. this specs page of the company in question
  2. To study the sn9c102 kernel module to learn what's necessary for v4l2
  3. To start with sniff-usb or usbsnoop and create a logfile of the USB commands, which should give an impression of the amount of work to do to retrieve an image. For a number of chips, this is about 30 USB commands, for others (m5603c) around 600.
  4. Decompression of the retrieved data is a whole other chapter
  5. From the lsusb -vv info, this chip also has bulk endpoints (libusb does not have isynchronous mode support). Sometimes, bulkmode can be used instead of iso to retrieve frames.

Also, Michel Xhaard suggested the trust100.inf Windows driver inf file might be useful.

For an interpretation of sniff-usb output, see

Here are the USB specifications: [[usb_20.pdf?]].