Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Manu Abraham schreef: On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu Manu, I will test this version tonight and report back. My rotor is working fine I discovered a small bug in my own software. When this was fixed I could rotate the dish without problems. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
На 25.2.2007 11:41 Manu Abraham написа: On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu Wors fine. ACPI: PCI Interrupt :02:0b.0[A] - GSI 23 (level, low) - IRQ 18 irq: 18, latency: 32 memory: 0xef00, mmio: 0xe081c000 found a VP-1034 PCI DVB-S/DSS device on (02:0b.0), Mantis Rev 1 [1822:0014], irq: 18, latency: 32 memory: 0xef00, mmio: 0xe081c000 MAC Address=[00:08:ca:1a:99:3e] mantis_alloc_buffers (0): DMA=0x1ed3 cpu=0xded3 size=65536 mantis_alloc_buffers (0): RISC=0x1ec43000 cpu=0xdec43000 size=1000 DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 intel8x0_measure_ac97_clock: measured 61099 usecs intel8x0: clocking to 48000 agpgart: Detected an Intel i850 Chipset. agpgart: AGP aperture is 64M @ 0xf800 Linux 2.6.20 #1 SMP Sun Feb 25 15:42:20 EET 2007 i686 pentium4 i386 GNU/Linux ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Michel Verbraak schreef: Manu Abraham schreef: On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu Manu, I will test this version tonight and report back. My rotor is working fine I discovered a small bug in my own software. When this was fixed I could rotate the dish without problems. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Manu, The 24th of february 2007 version works allright for me. Following in messagelog: ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 19 (level, low) - IRQ 19 irq: 19, latency: 32 memory: 0xf68ff000, mmio: 0xc202e000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 19, latency: 32 memory: 0xf68ff000, mmio: 0xc202e000 MAC Address=[00:08:ca:19:9f:0b] mantis_alloc_buffers (0): DMA=0xde5 cpu=0x81000de5 size=65536 mantis_alloc_buffers (0): RISC=0x30a04000 cpu=0x810030a04000 size=1000 DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... Rotor is working allright so DiseqC is transfered normal. I merged only the mantis part into my kernel sources. This is a x86_64 kernel. What should be the differences to the previous version? I did not yet try a scan for the missing channels to see if they are visible right now because my dish needs reallignement, reception is poort, after a storm a few weeks ago and currently it is pooring rain here so I was not able to get on my roof. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. I copied the directory linux/driver/media/dvb/mantis to 2.6.20-source/driver/media/dvb Modified the Kconfig and Makefile in 2.6.20-source/driver/media/dvb Copied the file mb86* and cu1216* to 2.6.20-source/driver/media/dvb/frontends And modified the Kconfig and Makefile in 2.6.20-source/driver/media/dvb/frontends Did a make menuconfig to compile the Mantis driver as a module and did a make modules. I received the following two problems and some warnings: 1. Had to remove one line in cu1216.c file (#include linux/config.h) 2. and had to modify the line #include mantis_core.h into #include ../mantis/mantis_core.h. I installed the modules (make modules_install) and loaded the modules (modprobe mantis) Following is the result in the messagelog: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 16 ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 16 (level, low) - IRQ 16 irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2026000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2026000 **WARNING** I2C adapter driver [Mantis I2C] forgot to specify physical device; fix it! MAC Address=[00:08:ca:19:9f:0b] mantis_alloc_buffers (0): DMA=0x2d31 cpu=0x81002d31 size=65536 mantis_alloc_buffers (0): RISC=0x282c5000 cpu=0x8100282c5000 size=1000 DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... Just one WARNING line which I have never seen before. Removed the modules and loaded the mb86a16 and the mantis module with verbose=255 and had the following output in messagelog: ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 16 (level, low) - IRQ 16 gpif status: 6080 irqcfg: 0002 mantis_set_direction (0): TS direction setup irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2062000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2062000 **WARNING** I2C adapter driver [Mantis I2C] forgot to specify physical device; fix it! mantis_i2c_init (0): Initializing I2C .. mantis_i2c_init (0): [0x0408/] mantis_i2c_write: Address=[0x50] W[ 08 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ] mantis_i2c_read: Address=[0x50] R[ === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 00 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 08 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ca === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 19 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 9f === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 0b ] MAC Address=[00:08:ca:19:9f:0b] mantis_dma_init (0): Mantis DMA init mantis_alloc_buffers (0): DMA=0x2d31 cpu=0x81002d31 size=65536 mantis_alloc_buffers (0): RISC=0xe465000 cpu=0x81000e465000 size=1000 mantis_calc_lines (0): Mantis RISC block bytes=[4096], line bytes=[2048], line count=[32] mantis_dvb_init (0): dvb_register_adapter DVB: registering new adapter (Mantis dvb adapter). mantis_dvb_init (0): dvb_dmx_init mantis_dvb_init (0): dvb_dmxdev_init mantis_frontend_init (0): Mantis frontend Init mantis_fe_powerup (0): Frontend Power ON mantis_frontend_reset (0): Frontend Reset mantis_frontend_init (0): Device ID=14 mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_i2c_write: Address=[0x08] W[ 7f === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ] mantis_i2c_read: Address=[0x08] R[ === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === fe ] mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... I can scan channels and watch channels without a problem. Currently not able to rotate my rotor but I'm still investigating what the problem might be. Regards, Michel. Some info about the environment: [EMAIL PROTECTED] linux-2.6.20]# uname -a Linux garfield.verbraak.thuis 2.6.20 #3 SMP Sun Feb 18 11:33:30 CET 2007 x86_64 x86_64 x86_64 GNU/Linux [EMAIL PROTECTED] linux-2.6.20]# lspci -v 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) Subsystem: ASRock Incorporation Unknown device 00e1 Flags: bus master, 66MHz, fast devsel, latency 0 Memory at f800 (32-bit, prefetchable) [size=64M] Capabilities: [44] HyperTransport: Slave or Primary Interface
