Which modules for the VP-2033? Where is the module "mantis.ko"?

Which modules for the VP-2033? Where is the module "mantis.ko"?

[Ruediger Dohmhardt]

Hi Manu,

the driver from http://jusst.de/hg/v4l-dvb/ compiles fine on Suse-11.1
(2.6.27.39-0.2-default).

However, it does not build the module "mantis.ko", as it used to be.
Where is it?
A search for mantis like

    cd v4l-dvb-ccd0c555c680
    find . -name "mantis*.ko"

    -> ./v4l/mantis_core.ko

shows up just the mantis_core.ko.

Which modules I'm supposed to load for the VP-2033?

Ciao Ruediger

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

In the same vein, I'm interested in this one, namely:

I have tried the http://jusst.de/hg/v4l-dvb, since recently the
liplianin mantis driver is not working (unknown symbols...). 

However, the problems I have as opposed to the previously working driver
are:
- the module does not install in a way it gets autoloaded on startup - I
have to manually add it (modprobe) or put it into /etc/modules (debian)
- while the card itself works, I don't have IR functionality anymore.
>From what I gather from the kernel log, the input line

input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4

just doesn't exist anymore. Further more the whole bunch is missing:

mantis_ca_init (0): Registering EN50221 device
mantis_ca_init (0): Registered EN50221 device
mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface
input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4
Creating IR device irrcv0


I tried 2.6.32 kernel which worked before, now I'm using 2.6.33-rc1
where I had to comment out #include <linux/autoconf.h> the from the
v4l-dvb/v4l/config-compat.h.


Any ideas how to get the comfort back? ;)

Regards,
Aljaz

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Igor M. Liplianin]

On 23 декабря 2009 16:30:16 Aljaž Prusnik wrote:
> In the same vein, I'm interested in this one, namely:
>
> I have tried the http://jusst.de/hg/v4l-dvb, since recently the
> liplianin mantis driver is not working (unknown symbols...).
>
> However, the problems I have as opposed to the previously working driver
> are:
> - the module does not install in a way it gets autoloaded on startup - I
> have to manually add it (modprobe) or put it into /etc/modules (debian)
> - while the card itself works, I don't have IR functionality anymore.
>
> >From what I gather from the kernel log, the input line
>
> input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4
>
> just doesn't exist anymore. Further more the whole bunch is missing:
>
> mantis_ca_init (0): Registering EN50221 device
> mantis_ca_init (0): Registered EN50221 device
> mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface
> input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4
> Creating IR device irrcv0
>
>
> I tried 2.6.32 kernel which worked before, now I'm using 2.6.33-rc1
> where I had to comment out #include <linux/autoconf.h> the from the
> v4l-dvb/v4l/config-compat.h.
>
>
> Any ideas how to get the comfort back? ;)
>
> Regards,
> Aljaz
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Since module ir-common.ko moved to IR directory just remove old one.

	rm /lib/modules/$(uname -r)/kernel/drivers/media/common/ir-common.ko

Also it would be good to do

	make remove

Then again build and install drivers.

-- 
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

On sre, 2009-12-23 at 17:53 +0200, Igor M. Liplianin wrote:
> Since module ir-common.ko moved to IR directory just remove old one.
> 
> 	rm /lib/modules/$(uname -r)/kernel/drivers/media/common/ir-common.ko
> 
> Also it would be good to do
> 
> 	make remove
> 
> Then again build and install drivers.
> 

Ok. There was no common folder in the above path. Anyway, I did rm and
make remove and did a new build (2.6.33-rc1). First, there were
warnings:
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/saa7134.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/saa7134.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/mantis.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-kbd-i2c.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-kbd-i2c.ko] undefined!
WARNING:
"ir_core_debug" [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-common.ko] undefined!
WARNING:
"ir_g_keycode_from_table" [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-common.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/em28xx.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/em28xx.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx88xx.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx88xx.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx23885.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx23885.ko] undefined!
WARNING:
"ir_input_register" [/mnt/storage/temp/technisat/s2-liplianin/v4l/bttv.ko] undefined!
WARNING:
"ir_input_unregister" [/mnt/storage/temp/technisat/s2-liplianin/v4l/bttv.ko] undefined!

Then I restarted the machine and this is in the kernel log:
ir_common: Unknown symbol ir_g_keycode_from_table
ir_common: Unknown symbol ir_core_debug
+ no mantis module loaded.

I have the IR folder under lib/modules where ir-common.ko resides. In
the common folder there is no file ir-common.ko.

If I do manual loading, I get:
sudo modprobe mantis
WARNING: Error inserting mb86a16
(/lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/frontends/mb86a16.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting mantis
(/lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

dmesg says:
[  289.939402] ir_common: Unknown symbol ir_g_keycode_from_table
[  289.939690] ir_common: Unknown symbol ir_core_debug


This is the s2-liplianin tree.

If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
module loads, but there is no remote anywhere (there is an IR folder
with the ir-common.ko file, under common there is not).


Aljaz

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Ruediger Dohmhardt]

Aljaž Prusnik schrieb:
>
> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
> module loads, but there is no remote anywhere (there is an IR folder
> with the ir-common.ko file, under common there is not).
>
>   
Aljaz, do you have the module mantis.ko?

Ruediger

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Manu Abraham]

Hello Ruediger,

On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
<ruediger.dohmhardt@freenet.de> wrote:
> Aljaž Prusnik schrieb:
>>
>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>> module loads, but there is no remote anywhere (there is an IR folder
>> with the ir-common.ko file, under common there is not).
>>
>>
> Aljaz, do you have the module mantis.ko?
>
> Ruediger
>

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


Dec 12 01:18:25 manu-04 kernel: [168362.291827] found a VP-2033 PCI
DVB-C device on (06:01.0),
Dec 12 01:18:25 manu-04 kernel: [168362.291842] Mantis 0000:06:01.0:
PCI INT A -> GSI 17 (level, low) -> IRQ 17
Dec 12 01:18:25 manu-04 kernel: [168362.291848] Mantis 0000:06:01.0:
enabling bus mastering
Dec 12 01:18:25 manu-04 kernel: [168362.291876]     Mantis Rev 1
[1822:0008], irq: 17, latency: 64
Dec 12 01:18:25 manu-04 kernel: [168362.291881]     memory: 0x0, mmio:
0xf875e000
Dec 12 01:18:25 manu-04 kernel: [168362.292577] i2c-adapter i2c-7:
adapter [Mantis I2C] registered
Dec 12 01:18:25 manu-04 kernel: [168362.292586] i2c-adapter i2c-7:
master_xfer[0] W, addr=0x50, len=1
Dec 12 01:18:25 manu-04 kernel: [168362.292590] i2c-adapter i2c-7:
master_xfer[1] R, addr=0x50, len=6
Dec 12 01:18:25 manu-04 kernel: [168362.292593]
mantis_i2c_write: Address=[0x50] <W>[ 08 ]
Dec 12 01:18:25 manu-04 kernel: [168362.292813]
mantis_i2c_read:  Address=[0x50] <R>[ 00 08 ca 19 ea ee ]
Dec 12 01:18:25 manu-04 kernel: [168362.293539]     MAC
Address=[00:08:ca:19:ea:ee]
Dec 12 01:18:25 manu-04 kernel: [168362.293565] mantis_alloc_buffers
(0): DMA=0x2c50000 cpu=0xc2c50000 size=65536
Dec 12 01:18:25 manu-04 kernel: [168362.293571] mantis_alloc_buffers
(0): RISC=0x31e36000 cpu=0xf1e36000 size=1000
Dec 12 01:18:25 manu-04 kernel: [168362.293575] DVB: registering new
adapter (Mantis DVB adapter)
Dec 12 01:18:26 manu-04 kernel: [168363.172508] vp2033_frontend_init
(0): Probing for CU1216 (DVB-C)
Dec 12 01:18:26 manu-04 kernel: [168363.172515] i2c-adapter i2c-7:
master_xfer[0] W, addr=0x50, len=1
Dec 12 01:18:26 manu-04 kernel: [168363.172519] i2c-adapter i2c-7:
master_xfer[1] R, addr=0x50, len=1
Dec 12 01:18:26 manu-04 kernel: [168363.172522]
mantis_i2c_write: Address=[0x50] <W>[ ff ]
Dec 12 01:18:26 manu-04 kernel: [168363.172741]
mantis_i2c_read:  Address=[0x50] <R>[ 22 ]
Dec 12 01:18:26 manu-04 kernel: [168363.172967] i2c-adapter i2c-7:
master_xfer[0] W, addr=0x0c, len=1
Dec 12 01:18:26 manu-04 kernel: [168363.172970] i2c-adapter i2c-7:
master_xfer[1] R, addr=0x0c, len=1
Dec 12 01:18:26 manu-04 kernel: [168363.172973]
mantis_i2c_write: Address=[0x0c] <W>[ 1a ]
Dec 12 01:18:26 manu-04 kernel: [168363.173194]
mantis_i2c_read:  Address=[0x0c] <R>[ 7c ]
Dec 12 01:18:26 manu-04 kernel: [168363.173416] TDA10021: i2c-addr =
0x0c, id = 0x7c
Dec 12 01:18:26 manu-04 kernel: [168363.173419] vp2033_frontend_init
(0): found Philips CU1216 DVB-C frontend (TDA10021) @ 0x0c
Dec 12 01:18:26 manu-04 kernel: [168363.173422] vp2033_frontend_init
(0): Mantis DVB-C Philips CU1216 frontend attach success
Dec 12 01:18:26 manu-04 kernel: [168363.173428] DVB: registering
adapter 0 frontend 0 (Philips TDA10021 DVB-C)...
Dec 12 01:18:26 manu-04 kernel: [168363.173549] mantis_uart_init (0):
Initializing UART @ 9600 bps NONE parity
Dec 12 01:18:26 manu-04 kernel: [168363.175459] mantis_uart_work (0):
UART BUF:0 <3f>


The IR stuff needs a bit more work, which I will be pushing out, later ..

Regards,
Manu

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Ruediger Dohmhardt]

Manu Abraham schrieb:
> Hello Ruediger,
>
> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
> <ruediger.dohmhardt@freenet.de> wrote:
>   
>> Aljaž Prusnik schrieb:
>>     
>>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>>> module loads, but there is no remote anywhere (there is an IR folder
>>> with the ir-common.ko file, under common there is not).
>>>
>>>
>>>       
>> Aljaz, do you have the module mantis.ko?
>>
>> Ruediger
>>
>>     
>
> There was a build issue when i posted the link originally, but it had
> been fixed..
>
>   
Yupp, it works now!

I just downloaded version 2315248f648c. It compiles fine on Suse 11.1 and
it works here with vdr-1.7.10 and xineliboutput (from CVS).

However, as Aljaž also noted, the driver does not "autoload".
I need to do modprobe mantis.ko.

Manu, this used to work, but I do not remember when the "autoload was lost".


Ciao Ruediger D.

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Manu Abraham]

On Thu, Dec 24, 2009 at 12:01 AM, Ruediger Dohmhardt
<ruediger.dohmhardt@freenet.de> wrote:
> Manu Abraham schrieb:
>> Hello Ruediger,
>>
>> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
>> <ruediger.dohmhardt@freenet.de> wrote:
>>
>>> Aljaž Prusnik schrieb:
>>>
>>>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>>>> module loads, but there is no remote anywhere (there is an IR folder
>>>> with the ir-common.ko file, under common there is not).
>>>>
>>>>
>>>>
>>> Aljaz, do you have the module mantis.ko?
>>>
>>> Ruediger
>>>
>>>
>>
>> There was a build issue when i posted the link originally, but it had
>> been fixed..
>>
>>
> Yupp, it works now!
>
> I just downloaded version 2315248f648c. It compiles fine on Suse 11.1 and
> it works here with vdr-1.7.10 and xineliboutput (from CVS).
>
> However, as Aljaž also noted, the driver does not "autoload".
> I need to do modprobe mantis.ko.
>
> Manu, this used to work, but I do not remember when the "autoload was lost".


Have you run depmod ?

Regards,
Manu

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Ruediger Dohmhardt]

Manu Abraham schrieb:
> On Thu, Dec 24, 2009 at 12:01 AM, Ruediger Dohmhardt
> <ruediger.dohmhardt@freenet.de> wrote:
>   
>> Manu Abraham schrieb:
>>     
>>> Hello Ruediger,
>>>
>>> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
>>> <ruediger.dohmhardt@freenet.de> wrote:
>>>
>>>       
>>>> Aljaž Prusnik schrieb:
>>>>
>>>>         
>>>>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>>>>> module loads, but there is no remote anywhere (there is an IR folder
>>>>> with the ir-common.ko file, under common there is not).
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> Aljaz, do you have the module mantis.ko?
>>>>
>>>> Ruediger
>>>>
>>>>
>>>>         
>>> There was a build issue when i posted the link originally, but it had
>>> been fixed..
>>>
>>>
>>>       
>> Yupp, it works now!
>>
>> I just downloaded version 2315248f648c. It compiles fine on Suse 11.1 and
>> it works here with vdr-1.7.10 and xineliboutput (from CVS).
>>
>> However, as Aljaž also noted, the driver does not "autoload".
>> I need to do modprobe mantis.ko.
>>
>> Manu, this used to work, but I do not remember when the "autoload was lost".
>>     
>
>
> Have you run depmod ?
>   
Yes, I did

    depmod -a

several times. Actually, if I were to miss a "depmod" than also the command

    modprobe mantis

would not work, because the module would not be found.

Ruediger

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

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

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Ruediger Dohmhardt]

Aljaž Prusnik schrieb:
> 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
>
>   
Aljaž, thanks for the "reply". As Manu said above there was a build problem.
As said already in this Thread, I downloaded version 2315248f648c, which
compiles fine and
has all modules for the 2033 DVB-C.

Rüdiger

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

On čet, 2009-12-24 at 17:45 +0100, Ruediger Dohmhardt wrote:
> Aljaž, thanks for the "reply". As Manu said above there was a build problem.
> As said already in this Thread, I downloaded version 2315248f648c, which
> compiles fine and
> has all modules for the 2033 DVB-C.

I have the same version and it doesn't work for me. I have a 2040
module.

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Manu Abraham]

Hello Aljaz,

On Thu, Dec 24, 2009 at 8:51 PM, Aljaž Prusnik <prusnik@gmail.com> wrote:
> On čet, 2009-12-24 at 17:45 +0100, Ruediger Dohmhardt wrote:
>> Aljaž, thanks for the "reply". As Manu said above there was a build problem.
>> As said already in this Thread, I downloaded version 2315248f648c, which
>> compiles fine and
>> has all modules for the 2033 DVB-C.
>
> I have the same version and it doesn't work for me. I have a 2040
> module.

Can you please do a lspci -vn for the Mantis card you have ? Also try
loading the mantis.ko module with verbose=5 module parameter, to get
more debug information.

Regards,
Manu

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote:
> Can you please do a lspci -vn for the Mantis card you have ? Also try
> loading the mantis.ko module with verbose=5 module parameter, to get
> more debug information.

$ lspci -vn

03:07.0 0480: 1822:4e35 (rev 01)
	Subsystem: 1ae4:0002
	Flags: bus master, medium devsel, latency 32, IRQ 21
	Memory at fdcff000 (32-bit, prefetchable) [size=4K]
	Kernel driver in use: Mantis


$ modprobe -v mantis  verbose=5

insmod /lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis_core.ko 
insmod /lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis.ko
verbose=5

$ dmesg

[ 2371.762511] Mantis 0000:03:07.0: PCI INT A disabled
[ 2462.703393] Mantis 0000:03:07.0: PCI INT A -> GSI 21 (level, low) ->
IRQ 21
[ 2462.704761] DVB: registering new adapter (Mantis DVB adapter)
[ 2463.563234] DVB: registering adapter 0 frontend 0 (Philips TDA10023
DVB-C)...
[ 2522.842548] Mantis 0000:03:07.0: PCI INT A disabled
[ 2534.495759] found a VP-2040 PCI DVB-C device on (03:07.0),
[ 2534.495771] Mantis 0000:03:07.0: PCI INT A -> GSI 21 (level, low) ->
IRQ 21
[ 2534.495796]     Mantis Rev 1 [1ae4:0002], irq: 21, latency: 32
[ 2534.495799]     memory: 0x0, mmio: 0xffffc900128cc000
[ 2534.495818] mantis_stream_control (0): Set stream to HIF
[ 2534.495841] mantis_i2c_init (0): Initializing I2C ..
[ 2534.495845] mantis_i2c_init (0): Disabling I2C interrupt
[ 2534.495849] mantis_i2c_xfer (0): Messages:2
[ 2534.495852]         mantis_i2c_write: Address=[0x50] <W>[ 08 ]
[ 2534.496243]         mantis_i2c_read:  Address=[0x50] <R>[ 00 08 c9 d0
02 09 ]
[ 2534.497049]     MAC Address=[00:08:c9:d0:02:09]
[ 2534.497051] mantis_dma_init (0): Mantis DMA init
[ 2534.497071] mantis_alloc_buffers (0): DMA=0x3d670000
cpu=0xffff88003d670000 size=65536
[ 2534.497073] mantis_alloc_buffers (0): RISC=0x3b731000
cpu=0xffff88003b731000 size=1000
[ 2534.497076] mantis_calc_lines (0): Mantis RISC block bytes=[4096],
line bytes=[2048], line count=[32]
[ 2534.497077] mantis_dvb_init (0): dvb_register_adapter
[ 2534.497079] DVB: registering new adapter (Mantis DVB adapter)
[ 2534.497081] mantis_dvb_init (0): dvb_dmx_init
[ 2534.497166] mantis_dvb_init (0): dvb_dmxdev_init
[ 2534.497269] mantis_frontend_power (0): Power ON
[ 2534.497271] gpio_set_bits (0): Set Bit <12> to <1>
[ 2534.497274] gpio_set_bits (0): GPIO Value <3000>
[ 2534.598099] gpio_set_bits (0): Set Bit <12> to <1>
[ 2534.598111] gpio_set_bits (0): GPIO Value <3000>
[ 2534.699066] mantis_frontend_soft_reset (0): Frontend RESET
[ 2534.699077] gpio_set_bits (0): Set Bit <13> to <0>
[ 2534.699085] gpio_set_bits (0): GPIO Value <1000>
[ 2534.800077] gpio_set_bits (0): Set Bit <13> to <0>
[ 2534.800087] gpio_set_bits (0): GPIO Value <1000>
[ 2534.901079] gpio_set_bits (0): Set Bit <13> to <1>
[ 2534.901089] gpio_set_bits (0): GPIO Value <3000>
[ 2535.002089] gpio_set_bits (0): Set Bit <13> to <1>
[ 2535.002099] gpio_set_bits (0): GPIO Value <3000>
[ 2535.354084] vp2040_frontend_init (0): Probing for CU1216 (DVB-C)
[ 2535.354096] mantis_i2c_xfer (0): Messages:2
[ 2535.354103]         mantis_i2c_write: Address=[0x50] <W>[ ff ]
[ 2535.354328]         mantis_i2c_read:  Address=[0x50] <R>[ e4 ]
[ 2535.354555] mantis_i2c_xfer (0): Messages:2
[ 2535.354560]         mantis_i2c_write: Address=[0x0c] <W>[ 1a ]
[ 2535.354781]         mantis_i2c_read:  Address=[0x0c] <R>[ 7d ]
[ 2535.355034] mantis_i2c_xfer (0): Messages:2
[ 2535.355039]         mantis_i2c_write: Address=[0x50] <W>[ ff ]
[ 2535.355257]         mantis_i2c_read:  Address=[0x50] <R>[ e4 ]
[ 2535.355482] mantis_i2c_xfer (0): Messages:1
[ 2535.355486]         mantis_i2c_write: Address=[0x0c] <W>[ 00 33 ]
[ 2535.355819] mantis_i2c_xfer (0): Messages:2
[ 2535.355823]         mantis_i2c_write: Address=[0x0c] <W>[ 1a ]
[ 2535.356055]         mantis_i2c_read:  Address=[0x0c] <R>[ 7d ]
[ 2535.356279] vp2040_frontend_init (0): found Philips CU1216 DVB-C
frontend (TDA10023) @ 0x0c
[ 2535.356285] vp2040_frontend_init (0): Mantis DVB-C Philips CU1216
frontend attach success
[ 2535.356291] vp2040_frontend_init (0): Done!
[ 2535.356298] DVB: registering adapter 0 frontend 0 (Philips TDA10023
DVB-C)...
[ 2535.356573] mantis_uart_init (0): Initializing UART @ 9600bps
parity:NONE
[ 2535.356602] mantis_uart_read (0): Reading ... <3f>
[ 2535.356609] mantis_uart_work (0): UART BUF:0 <3f> 
[ 2535.356613] 
[ 2535.356619] mantis_uart_init (0): UART succesfully initialized

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

On pon, 2009-12-28 at 20:28 +0100, Aljaž Prusnik wrote:
> On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote:
> > Can you please do a lspci -vn for the Mantis card you have ? Also try
> > loading the mantis.ko module with verbose=5 module parameter, to get
> > more debug information.
> 

To continue, it seems the module is registering the remote commands, but
dunno, why irw shows nothing:

dmesg of typing on remote:
[ 4854.805594] mantis_uart_read (0): Reading ... <3d>
[ 4854.805605] mantis_uart_work (0): UART BUF:0 <3d> 
[ 4854.805609] 
[ 4854.805615] mantis_uart_read (0): Reading ... <3d>
[ 4854.805621] mantis_uart_work (0): UART BUF:0 <3d> 
[ 4854.805624] 
[ 4895.266923] 
[ 4895.266926] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.266956] 
[ 4895.266958] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.266979] 
[ 4895.266981] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.266999] 
[ 4895.267000] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.267015] 
[ 4895.267016] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.267031] 
[ 4895.267032] -- Stat=<4000800> Mask=<800> --<IRQ-1>
[ 4895.267043] mantis_uart_read (0): Reading ... <3e>
[ 4895.267054] mantis_uart_work (0): UART BUF:0 <3e> 
[ 4895.267058] 
[ 4895.267065] mantis_uart_read (0): Reading ... <3e>
[ 4895.267070] mantis_uart_work (0): UART BUF:0 <3e> 

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

On pon, 2009-12-28 at 21:06 +0100, Aljaž Prusnik wrote:
> On pon, 2009-12-28 at 20:28 +0100, Aljaž Prusnik wrote:
> > On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote:
> > > Can you please do a lspci -vn for the Mantis card you have ? Also try
> > > loading the mantis.ko module with verbose=5 module parameter, to get
> > > more debug information.
> > 
> 
> To continue, it seems the module is registering the remote commands, but
> dunno, why irw shows nothing:

Well - to answer myself on this one, it doesn't because there is no
input device registered. I used to have this under input devices
(cat /proc/bus/input/devices):

I: Bus=0001 Vendor=0000 Product=0000 Version=0001
N: Name="Mantis VP-2040 IR Receiver"
P: Phys=pci-0000:03:06.0/ir0
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=100003
B: KEY=108fc330 284204100000000 0 2000000018000 218040000801
9e96c000000000 ffc

So the question is, why is it not registered as an input anymore?

Regards,
Aljaz

Re: Which modules for the VP-2033? Where is the module "mantis.ko"?

[Aljaž Prusnik]

Hi!

Still no change regarding regaining IR support for VP2040 device.
Despite successfully loading the module from Abraham's tree and starting
the UART, I still do not see the input device that I can use with lirc.

I tried both trees:
today's Liplianin tree, dmesg on loading the mantis module:

ir_common: Unknown symbol ir_g_keycode_from_table
ir_common: Unknown symbol ir_core_debug


today's Abraham's tree, dmesg on loading the mantis modulem verbose=5: 

the result is still the same as the last time I wrote about it (no input
device is registered, despite successful uart initialization).