On sre, 2009-12-23 at 23:24 +0400, Manu Abraham wrote:
> > Aljaz, do you have the module mantis.ko?
> There was a build issue when i posted the link originally, but it had
> been fixed..
> m...@manu-04:/stor/work/merge/v4l-dvb/v4l> ls *.ko |grep mantis
> mantis_core.ko
> mantis.ko

Yup, I have both of them. I just compiled http://jusst.de/hg/v4l-dvb
again and the result is (depmode -a was run):

- ir-common.ko is under drivers/media/common (not drivers/media/IR like
Igor suggested but that is probably because it's a different
- mantis.ko and mantis_core.ko are under drivers/media/dvb/mantis

The modules loaded are:
mantis                 14728  0 
mantis_core            23909  12 mantis
ir_common              27005  1 mantis_core
mb86a16                16598  1 mantis
tda10021                4822  1 mantis
tda10023                5823  1 mantis
zl10353                 5893  1 mantis
stv0299                 7860  1 mantis
dvb_core               75201  2 mantis_core,stv0299

kernel log has only these lines on mantis:
Mantis 0000:03:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
DVB: registering new adapter (Mantis DVB adapter)
DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...

and that's it. No VP-2040 to be seen anywhere and it's not there even if
I do cat /proc/bus/input/devices (used to be one of the inputs).

So I guess this is now the work in progress if I understand correctly or
should the input be recognized regardless?

Just to confirm on the autoload: no, it does not happen by default. I
have to manually put modules under /etc/modules to load them on startup.


To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to