Re: VINO support in kernel

[Fred Barnes <F.R.M.Barnes@kent.ac.uk>]

Hi,

> Please make sure you also selected CONFIG_I2C and CONFIG_I2C_ALGO_SGI as
> suggested on driver hopemage:
> http://www.linux-mips.org/~ladis/vino/vino.html

I've been poking around trying to get my indycam working;  close, but
no cigar.  Running the 2.4.26 kernel from debian,
kernel-image-2.4.26-r5k-ip22 -- assuming it has the mentioned MIPS patches
installed.

Modules look good:

    indycam                 1520   1 (autoclean)
    saa7191                 2080   1 (autoclean)
    vino                   10704   0
    i2c-algo-sgi            1856   0 [vino]
    i2c-core               16768   0 [indycam saa7191 i2c-algo-sgi]
    videodev                8368   2 [vino]

And this stuff was dropped in the kernel log:

    Linux video capture interface: v1.00
    i2c-core.o: i2c core module version 2.6.1 (20010830)
    VINO Rev: 0x00
    VINO: clipping 0, 0, 640, 486 / 1 - 640
    VINO: clipping 0, 0, 640, 486 / 1 - 640
    i2c-core.o: adapter VINO I2C bus registered as adapter 0.
    i2c-core.o: driver saa7191 registered.
    i2c-core.o: client [saa7191 client] registered to adapter [VINO I2C bus](pos. 0).
    i2c-core.o: driver indycam registered.
    i2c-core.o: client [IndyCam client] registered to adapter [VINO I2C bus](pos. 1).
    Indycam v1.0 detected.
    VINO: scaling 0, 0, 640, 480 / 1 - 640


Compiled vgrabbj (0.9.6) from sources, with the patch (applied cleanly),
and it sort of works, but doesn't quite.  I get a black image out, though.
For 3 runs of vgrabbj, this came out in the kernel log:  (first):

    VINO: scaling 0, 0, 640, 480 / 1 - 640
    XXX 2, 1
    VINO: intr status 0004
    VINO: chnl A clear EOD
    VINO: intr status 0002
    VINO: chnl A clear EOD

And the other two:

    VINO: scaling 0, 0, 640, 480 / 1 - 2560
    VINO: intr status 0006
    VINO: chnl A clear EOD
    VINO: scaling 0, 0, 640, 480 / 1 - 2560
    VINO: intr status 0006
    VINO: chnl A clear EOD


I'll hunt around for another indycam later, incase the one I'm using is duff in
some way.  But any other ideas ?

Aside: yesterday evening, playing around with client apps (camstream, xawtv),
videodev got left with a refcount of 1 (after unloading all the vino/indycam
stuff).  Not sure whether this was a side effect of xawtv (and friends)
prodding, though.


Thanks! (especially for the hard work you've put into making VINO happen!)

-- Fred