From: "Aljaž Prusnik" <prusnik@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: Which modules for the VP-2033? Where is the module "mantis.ko"?
Date: Thu, 24 Dec 2009 00:45:02 +0100 [thread overview]
Message-ID: <1261611901.8948.37.camel@slash.doma> (raw)
In-Reply-To: <1a297b360912231124v6e31c9e6ja24d205f6b5dc39@mail.gmail.com>
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..
>
> manu@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
repository).
- 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.
Regards,
Aljaz
next prev parent reply other threads:[~2009-12-23 23:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 20:12 Which modules for the VP-2033? Where is the module "mantis.ko"? Ruediger Dohmhardt
2009-12-23 14:30 ` Aljaž Prusnik
2009-12-23 15:53 ` Igor M. Liplianin
2009-12-23 16:41 ` Aljaž Prusnik
2009-12-23 19:04 ` Ruediger Dohmhardt
2009-12-23 19:24 ` Manu Abraham
2009-12-23 20:01 ` Ruediger Dohmhardt
2009-12-23 20:26 ` Manu Abraham
2009-12-23 21:03 ` Ruediger Dohmhardt
2009-12-23 23:45 ` Aljaž Prusnik [this message]
2009-12-24 16:45 ` Ruediger Dohmhardt
2009-12-24 16:51 ` Aljaž Prusnik
2009-12-27 22:23 ` Manu Abraham
2009-12-28 19:28 ` Aljaž Prusnik
2009-12-28 20:06 ` Aljaž Prusnik
2009-12-29 18:25 ` Aljaž Prusnik
2010-01-09 17:26 ` Aljaž Prusnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1261611901.8948.37.camel@slash.doma \
--to=prusnik@gmail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox