Good News,Open source code for TBS Card has been released

[Paust55]

@crazycat,
I've make a "make stagingconfig" and after that I compiled the driver, but the result isn't good for me, because I need "lirc_serial" for a Homebrew-IR receiver on serial port COM1.
And I think you use "lirc_sir" and this is for my opinion only for the IrDa port and not for the serial port.

I found a "/lib/... /staging/lirc/lirc_serial.ko", but it seems that this driver doesn't work!
In the past, the original "lirc_serial.c" from the tbs-driver (not the open source driver) has also a problem and I replaced the "/linux/drivers/staging/lirc/lirc_serial.c" with a working file from an other dvb-driver, before I compiled the driver.

Have you any idea for me, how I can use a serial port with the tbs-driver?

Paul

[krmlk]

git clone https://github.com/tbsdtv/media_build.git
Cloning into 'media_build'...
fatal: unable to access 'https://github.com/tbsdtv/media_build.git/': Peer's Certificate has expired.

card 6909

[crazycat]

I found a "/lib/... /staging/lirc/lirc_serial.ko", but it seems that this driver doesn't work!
In the past, the original "lirc_serial.c" from the tbs-driver (not the open source driver) has also a problem and I replaced the "/linux/drivers/staging/lirc/lirc_serial.c" with a working file from an other dvb-driver, before I compiled the driver.

Have you any idea for me, how I can use a serial port with the tbs-driver?

I think you need serial_ir driver, this not staging driver and compiled always with default config.

boss@COMPUTER:/usr/local/src/media_build/media/drivers/media/rc$ modinfo serial_ir
filename: /lib/modules/4.4.0-42-generic/kernel/drivers/media/rc/serial_ir.ko
license: GPL
author: Ralph Metzler, Trent Piepho, Ben Pfaff, Christoph Bartelmus, Andrei Tanas
description: Infra-red receiver driver for serial ports.
srcversion: FF8F60CB673E21952355B22
depends: rc-core
vermagic: 4.4.0-42-generic SMP mod_unload modversions
parm: type:Hardware type (0 = home-brew, 1 = IRdeo, 2 = IRdeo Remote, 3 = AnimaX, 4 = IgorPlug (int)
parm: io:I/O address base (0x3f8 or 0x2f8) (int)
parm: iommap:physical base for memory mapped I/O (0 = no memory mapped io) (bool)
parm: ioshift:shift I/O register offset (0 = no shift) (int)
parm: irq:Interrupt (4 or 3) (int)
parm: share_irq:Share interrupts (0 = off, 1 = on) (bool)
parm: sense:Override autodetection of IR receiver circuit (0 = active high, 1 = active low ) (int)
parm: txsense:Sense of transmitter circuit (0 = active high, 1 = active low ) (bool)
parm: softcarrier:Software carrier (0 = off, 1 = on, default on) (bool)

[imperia]

The driver compiled successfully on latest debian kernel 4.8.0-2, but its not working. I got spammed in syslog:

Code: Select All Code

Dec 18 01:18:34 vdr kernel: dvb_demux: dvb_dmx_swfilter_section_packet: dvb_demux.c discontinuity detected 184 bytes lost

[Paust55]

I think you need serial_ir driver, this not staging driver and compiled always with default config. ...

Okay, I've made a new test today and after compiling the new driver I could make a modprobe serial_ir without an error message. But I can't control my HTPC with my remote control.


I used a Ubuntu-14.04 as Operating system (with yavdr-0.6) and "lirc_serial" with a Homebrew-IR-Receiver on Com-Port 1.
To activate the right Com-Port I used this conf-Filer in /etc/modpobe.d/lirc-serial.conf with this content:

Code: Select All Code

options lirc_serial irq=4 io=0x3f8
install lirc_serial setserial /dev/ttyS0 uart none; /sbin/modprobe --ignore-install lirc_serial

Do you know what I have to do, to switch from lirc_serial to serial_ir?
Or have anyone some examples to configure "serial_ir" in Ubuntu?

Paul

[Paust55]

I'll answer myself, because I found a solution for use my remote control with "serial_ir" instead of my old "lirc_serial"


1. In /etc/modprobe.d I added a new file called "serial_ir.conf" with this content:

#COM1 equivalent, /dev/ttyS0
options serial_ir irq=4 io=0x3f8

2. In /etc/lirc I changed the file "hardware.conf" and replace "lirc_serial" with "serial_ir" :

...
REMOTE_MODULES="lirc_dev serial_ir"
REMOTE_DEVICE="/dev/lirc0"
...

After a reboot I can now use my remote control and all things work perfect!
I used an needed the new open sorce driver with my new TBS-6205 to receive DVB-C and DVB-T2 with on driver at the samt time!

Very good work from your team!

Paul

[Paust55]

I found a small cosmetic issue in the new open source driver, when I check my registered frontends.
In addition to my new TBS-6205 for DVB-T2 I used one TBS-8922 and one TBS-6981 for DVB-S2.

All 3 DVB cards work fine, but if I look at linux console wich frontends are available I get not the right description for my old cards (TBS-8922 and TBS-6981). Only the description for the new TBS-6205 are correct.

For example what I mean, here is the output when I put dmesg | grep "registering frontends" in a console with the "old closed source" driver:

DVB: registering adapter 0 frontend 0 (TurboSight TBS 8922 DVBS/S2 frontend)...
DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
DVB: registering adapter 3 frontend 0 (TurboSight TBS 6205 DVBT/T2 frontend)...
DVB: registering adapter 4 frontend 0 (TurboSight TBS 6205 DVBT/T2 frontend)...
DVB: registering adapter 5 frontend 0 (TurboSight TBS 6205 DVBT/T2 frontend)...
DVB: registering adapter 6 frontend 0 (TurboSight TBS 6205 DVBT/T2 frontend)...

The same with the new open source driver will get the following output:

DVB: registering adapter 0 frontend 0 (Tmax TAS2101)...
DVB: registering adapter 1 frontend 0 (Conexant CX24117/CX24132)...
DVB: registering adapter 2 frontend 0 (Conexant CX24117/CX24132)...
DVB: registering adapter 3 frontend 0 (TurboSight TBS 6205 DVB-T/T2/C )...
DVB: registering adapter 4 frontend 0 (TurboSight TBS 6205 DVB-T/T2/C )...
DVB: registering adapter 5 frontend 0 (TurboSight TBS 6205 DVB-T/T2/C )...
DVB: registering adapter 6 frontend 0 (TurboSight TBS 6205 DVB-T/T2/C )...

You see that I get in place of "TBS 8922" the name of the used IC "TAS2101" and the "TBS 6981" will shown as "CX24117/CX24132".
It's not an important issue, but it will be a "nice to have" if we get the right output with the new open source driver!

Paul

[Paust55]

I found an new bug in the new open source driver:
I get no value for SNR with my TBS-6981, only a value for STR.
My other cards (TBS-8922 and TBS-6205) have a value for STR and SNR.

With the old linux-tbs-driver a have for all cards a value for STR and SNR.

Paul

[crazycat]

cx24117 frontend driver return some snr value
https://github.com/tbsdtv/linux_media/b ... 117.c#L830

but look like this some raw register value, not dB or %.

[Paust55]

but look like this some raw register value, not dB or %.

I use yaVDR with the vdr-plugin-femon to display STR and SNR.
With the new driver I get a value = 0% for SNR with my TBS-6981 card.
I don't know what's wrong, but with my other used cards TBS-8922 and TBS-6205 I get both values: STR and SNR

And with the "old" closed linux-tbs-driver I get both values for my TBS-6981: STR and SNR.

Paul