Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT, MAX S8 sowie TT S2-6400 (Teil 3)

Zitat von bas-t

After make untar do:

Code

cd linux
patch -p1 < path/to/pci_dma_supported.diff
cd ..
make distclean
make allyesconfig  ## or make menuconfig
make
make install

That's it.

Thanks for your help. When I try to perform this code:

patch -p1 < path/to/pci_dma_supported.diff

I have the following answer:

[userssh@pcsalon media_build_experimental]$ sudo patch -p1 < /home/userssh/pci_dma_supported.diffcan't find file to patch at input line 5Perhaps you used the wrong -p or --strip option?The text leading up to this was:--------------------------|diff --git a/drivers/media/pci/cx23885/cx23885-core.c b/drivers/media/pci/cx23885/cx23885-core.c|index 3bd386c..abd15b3 100644|--- a/drivers/media/pci/cx23885/cx23885-core.c|+++ b/drivers/media/pci/cx23885/cx23885-core.c--------------------------File to patch:

zofiel: you didn't do the "cd linux".

Gerald

Zitat von gda

zofiel: you didn't do the "cd linux".

Gerald

yeah, thanks a lot. Patch applied.

This patch doesn't fix the following error, Is'n It?

/home/userssh/media_build_experimental/v4l/adp1653.c: In function 'adp1653_of_init': /home/userssh/media_build_experimental/v4l/adp1653.c:468:20: error: too few arguments to function 'devm_gpiod_get'


  pd->enable_gpio = devm_gpiod_get(&client->dev, "enable");


                    ^


In file included from /home/userssh/media_build_experimental/v4l/adp1653.c:39:0:


include/linux/gpio/consumer.h:73:32: note: declared here


 struct gpio_desc *__must_check devm_gpiod_get(struct device *dev,


                                ^


scripts/Makefile.build:264: fallo en las instrucciones para el objetivo '/home/userssh/media_build_experimental/v4l/adp1653.o'


make[4]: *** [/home/userssh/media_build_experimental/v4l/adp1653.o] Error 1


Makefile:1378: recipe for target '_module_/home/userssh/media_build_experimental/v4l' failed


make[3]: *** [_module_/home/userssh/media_build_experimental/v4l] Error 2


make[3]: Leaving directory '/usr/lib/modules/4.3.3-2-ARCH/build'


Makefile:51: fallo en las instrucciones para el objetivo 'default'


make[2]: *** [default] Error 2


make[2]: se sale del directorio '/home/userssh/media_build_experimental/v4l'


Makefile:28: fallo en las instrucciones para el objetivo 'all'


make[1]: *** [all] Error 2


make[1]: se sale del directorio '/home/userssh/media_build_experimental'


Makefile:82: fallo en las instrucciones para el objetivo 'default'


make: *** [default] Error 2

How I can fix It? I have a Skystar 2 express HD and i think that this driver is the only than works with my device.

Thanks a lot for your help

zofiel:

Zitat von 9000H

Hi,

hab ich hier auch mit kernel 4.3

Diff

--- adp1653.c.orig	2015-11-15 12:52:09.842224791 +0100
+++ adp1653.c	2015-11-15 12:52:39.574751240 +0100
@@ -465,7 +465,7 @@
 
 	of_node_put(child);
 
-	pd->enable_gpio = devm_gpiod_get(&client->dev, "enable");
+	pd->enable_gpio = devm_gpiod_get(&client->dev, "enable", GPIOD_ASIS);
 	if (!pd->enable_gpio) {
 		dev_err(&client->dev, "Error getting GPIO\n");
 		return -EINVAL;

Alles anzeigen

CU
9000h

This is posted just one page back. I guess it wil solve your issue.
Do you even read this thread at all?

Zitat von bas-t

zofiel:

This is posted just one page back. I guess it wil solve your issue.
Do you even read this thread at all?

First of all, thanks a lot for all forum help.

yes, I come this to forum following this error via Google. As you can see, I'm very newbie with patchs, and I don't speak German, so I'm reading the thread but It's very difficult. Sorry for this Offtopic.

I'm reading your quote but I don't know how

Zitat von bas-t

zofiel:

This is posted just one page back. I guess it wil solve your issue.
Do you even read this thread at all?

First of all, thanks a lot for all forum help.

yes, I come this to forum following this error via Google. As you can see, I'm very newbie with patchs, and I don't speak German, so I'm reading the thread but It's very difficult. Sorry for this Offtopic.

I'm reading your quote but I don't know how to apply this config, so any little help is welcome.

zofiel:
sorry, I did not realise that you are extremely new to this.
So here's how to do it:

like before, after make untar, do

cd linux
patch -p1 < path/to/pci_dma_supported.diff
patch -p1 < path/to/adp1653.diff
cd ..
make distclean
make allyesconfig  ## or make menuconfig
make
make install

Cheers,
Tycho.

For some reason, the pci_dma_supported.diff starts to fail.
Here's an updated version.

Thanks a lot!! works perfect!!!!

Zitat von zofiel

Thanks a lot!! works perfect!!!!

You're welcome.

Mal eine kurze Frage, ist es möglich die MAX S8 parallel noch zu herkömmlichen Cine Duoflex-Karten im selben Rechner zu betreiben?

Oder könnte das zu Problemen führen?

Danke,

Hi, I'm using an Octopus with a dual S2 board and was using the 0.5 for a few years without problem. Upgrading to a new kernel I decided to give the latest 0.9.18 a try but for some reason only vertical polarized channels seem to work. Anybody experienced this yet? The only symptoms I see are very very high BER, and 0 or very low signal strength and SNR.

version: 0.9.18
srcversion: B3FB489B38DDF7D19A16E2B

What supprises me is that the vertical channels work. While this could in theory be a LNB problem (water/moisture inside the LNB? I noticed the change with the different version so thinking of this at first.

I have a small update on this. It turns out the LNB is broken, de Horizontals no longer work. I have thus far excluded the cables and used a different LNB. With a different LNB it worked for a day, after a day, the signal strength dropped from 80% to 20% on the H and a day later, de V also had a drop from 80% to 20%. Using the original M7 tuner also shows the same symptoms on the LNB now.

Is it possible that for some reason the 0.9.8.1 driver can potentially kill LNB's? I've been using the 0.5 driver for 3 years now and never had a problem and within a week of using the 0.9.8 driver I killed the H on my duo lnb and the H and V on my inverto black LNB. For now, I will connect the duo lnb again to the 0.9.8 driver and see how long it takes before the V is killed also here (since the LNB is half-useless. If the V also dies, i'll roll back the 0.9.8 driver ... and keep using the 0.5

Hallo zusammen,

ich bekomme I2C timeouts trotz "options ddbridge msi=0". Jemand 'ne Idee warum das so ist? Hardware ist eine DD Cine S2 v6.5 plus DuoFlex S2. Läuft unter ESXi 6.0 mit VT-d Passthrough.

root@vdr:~# uname -a
Linux vdr 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux

root@vdr:~# cat /etc/modprobe.d/ddbridge.conf 
options ddbridge msi=0

dmesg Auszug wenn ddbridge geladen wird:

[Fri Jan 22 16:13:08 2016] media: Linux media interface: v0.10
[Fri Jan 22 16:13:08 2016] WARNING: You are using an experimental version of the media stack.
	As the driver is backported to an older kernel, it doesn't offer
	enough quality for its usage in production.
	Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
	1555f3bf5cc172e7d23c2b8db10d656d15bec13e [media] saa7164: fix compiler warning
	ebf984bb151e9952cccd060d3aba0b4d30a87e81 [media] v4l2: replace s_mbus_fmt by set_fmt in bridge drivers
	5eab4983777ba913efb42dd0f177b0dcdbd4f3d9 [media] v4l2: replace try_mbus_fmt by set_fmt in bridge drivers
	experimental: 82186b8b60da1c55e956c89d78a8de4e670d5a29 experimental/ddbridge: Include LNBH25 driver in build process.
	v4l-dvb-saa716x: d7e98fc592305a600909003da2b7cc4338242511 saa716x_ff: Do not return on command ready timeout
[Fri Jan 22 16:13:08 2016] Digital Devices PCIE bridge driver 0.9.18, Copyright (C) 2010-15 Digital Devices GmbH
[Fri Jan 22 16:13:08 2016] DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB adapter
[Fri Jan 22 16:13:08 2016] DDBridge: HW 0001000d REGMAP 00010004
[Fri Jan 22 16:13:08 2016] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2
[Fri Jan 22 16:13:08 2016] Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2
[Fri Jan 22 16:13:08 2016] Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE
[Fri Jan 22 16:13:08 2016] Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE
[Fri Jan 22 16:13:08 2016] 0 netstream channels
[Fri Jan 22 16:13:08 2016] DVB: registering new adapter (DDBridge)
[Fri Jan 22 16:13:08 2016] DVB: registering new adapter (DDBridge)
[Fri Jan 22 16:13:08 2016] DVB: registering new adapter (DDBridge)
[Fri Jan 22 16:13:08 2016] DVB: registering new adapter (DDBridge)

dmesg Auszug mit I2C timeouts:

root@vdr:~# dmesg -T|tail -8
[Fri Jan 22 17:12:31 2016] DDBridge I2C timeout, card 0, port 0, link 0
[Fri Jan 22 17:12:31 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000f03
[Fri Jan 22 17:12:32 2016] DDBridge I2C timeout, card 0, port 1, link 0
[Fri Jan 22 17:12:32 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000000
[Fri Jan 22 18:06:02 2016] DDBridge I2C timeout, card 0, port 0, link 0
[Fri Jan 22 18:06:02 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000e03
[Fri Jan 22 18:06:02 2016] DDBridge I2C timeout, card 0, port 1, link 0
[Fri Jan 22 18:06:02 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000000

Woran kann das liegen?

Zitat von BerndV

ich bekomme I2C timeouts trotz "options ddbridge msi=0". Jemand 'ne Idee warum das so ist? Hardware ist eine DD Cine S2 v6.5 plus DuoFlex S2. Läuft unter ESXi 6.0 mit VT-d Passthrough.

Ich habe jetzt mal MSI im Kernel abgeschaltet:

root@vdr:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=98334508-4299-4072-8870-04ee745a0fde ro pci=nomsi quiet

bekomme aber immer noch Meldungen:

root@vdr:~# dmesg -T|tail -8
[Sun Jan 31 02:57:22 2016] DDBridge I2C timeout, card 0, port 0, link 0
[Sun Jan 31 02:57:22 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000c03
[Sun Jan 31 02:57:22 2016] DDBridge I2C timeout, card 0, port 1, link 0
[Sun Jan 31 02:57:22 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000000
[Sun Jan 31 03:02:19 2016] DDBridge I2C timeout, card 0, port 0, link 0
[Sun Jan 31 03:02:19 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000d03
[Sun Jan 31 03:02:19 2016] DDBridge I2C timeout, card 0, port 1, link 0
[Sun Jan 31 03:02:19 2016] ddbridge 0000:03:00.0: DDBridge IRS 00000000

Wie kann das sein? Oder haben die I2C timeouts nix mit MSI zu tun?

Wollte mich an dieser Stelle einfach mal bedanken.

options ddbridge msi=0

In /etc/modprobe.d zu laden hat es bei mir wohl gebracht! Davor (ich nutze eine Cine S2 6.5 mit Duo Flex S2) hat es mir immer zwei der vier Karten mit den I2C-Timeout Meldungen im syslog zerbröselt, was zum Absturz des VDR und des Systems (runterfahren ging nicht mehr, musste das System mittels der Powertaste stromlos machen) führte. Selbst, wenn man ein Reboot ging, die Karte 3 und 4 kamen nicht mehr hoch, dazu musste erstmal stromlos gemacht werden.

Komischerweise habe ich den Effekt erst seit ein paar Tagen, die Karten aber schon seit 3 Monaten verbaut. Verstehe, wer wolle...

Since kernel 4.4 I'm having the following errors

home/userssh/media_build_experimental/v4l/saa716x_priv.h:39:11: note: in expansion of macro 'KERN_ERR'


    printk(KERN_ERR "%s (%d): " __fmt "\n" , __func__ , SAA716x_DEV , ##__arg); \


           ^


/home/userssh/media_build_experimental/v4l/saa716x_rom.c:270:3: note: in expansion of macro 'dprintk'


   dprintk(SAA716x_ERROR, 1,


   ^


include/linux/kern_levels.h:4:18: warning: format '%d' expects argument of type 'int', but argument 5 has type 'long unsigned int' [-Wformat=]


 #define KERN_SOH "\001"  /* ASCII Start Of Header */


                  ^


include/linux/kern_levels.h:12:21: note: in expansion of macro 'KERN_SOH'


 #define KERN_NOTICE KERN_SOH "5" /* normal but significant condition */


                     ^


/home/userssh/media_build_experimental/v4l/saa716x_priv.h:41:11: note: in expansion of macro 'KERN_NOTICE'


    printk(KERN_NOTICE "%s (%d): " __fmt "\n" , __func__ , SAA716x_DEV , ##__arg); \


           ^


/home/userssh/media_build_experimental/v4l/saa716x_rom.c:270:3: note: in expansion of macro 'dprintk'


   dprintk(SAA716x_ERROR, 1,


   ^


include/linux/kern_levels.h:4:18: warning: format '%d' expects argument of type 'int', but argument 5 has type 'long unsigned int' [-Wformat=]


 #define KERN_SOH "\001"  /* ASCII Start Of Header */


                  ^


include/linux/kern_levels.h:13:19: note: in expansion of macro 'KERN_SOH'


 #define KERN_INFO KERN_SOH "6" /* informational */


                   ^


/home/userssh/media_build_experimental/v4l/saa716x_priv.h:43:11: note: in expansion of macro 'KERN_INFO'


    printk(KERN_INFO "%s (%d): " __fmt "\n" , __func__ , SAA716x_DEV , ##__arg); \


           ^


/home/userssh/media_build_experimental/v4l/saa716x_rom.c:270:3: note: in expansion of macro 'dprintk'


   dprintk(SAA716x_ERROR, 1,


   ^


include/linux/kern_levels.h:4:18: warning: format '%d' expects argument of type 'int', but argument 5 has type 'long unsigned int' [-Wformat=]


 #define KERN_SOH "\001"  /* ASCII Start Of Header */


                  ^


include/linux/kern_levels.h:14:20: note: in expansion of macro 'KERN_SOH'


 #define KERN_DEBUG KERN_SOH "7" /* debug-level messages */

the code is too long, so you can follow It in http://pastebin.com/7ii94LwQ

Any idea? Thanks for your help

After update to new kernel i get the followin errors:

rgu@tv-server:~/media_build_experimental$ make
make -C /home/rgu/media_build_experimental/v4l
make[1]: Verzeichnis „/home/rgu/media_build_experimental/v4l“ wird betreten
creating symbolic links...
make -C firmware prep
make[2]: Entering directory '/home/rgu/media_build_experimental/v4l/firmware'
make[2]: Leaving directory '/home/rgu/media_build_experimental/v4l/firmware'
make -C firmware
make[2]: Entering directory '/home/rgu/media_build_experimental/v4l/firmware'
make[2]: Nothing to be done for 'default'.
make[2]: Leaving directory '/home/rgu/media_build_experimental/v4l/firmware'
Kernel build directory is /lib/modules/4.4.0-6-generic/build
make -C ../linux apply_patches
make[2]: Entering directory '/home/rgu/media_build_experimental/linux'
Patches for 4.4.0-6-generic already applied.
make[2]: Leaving directory '/home/rgu/media_build_experimental/linux'
make -C /lib/modules/4.4.0-6-generic/build SUBDIRS=/home/rgu/media_build_experimental/v4l modules
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-6-generic'
CC [M] /home/rgu/media_build_experimental/v4l/adp1653.o
/home/rgu/media_build_experimental/v4l/adp1653.c: In function 'adp1653_of_init':
/home/rgu/media_build_experimental/v4l/adp1653.c:468:20: error: too few arguments to function 'devm_gpiod_get'
pd->enable_gpio = devm_gpiod_get(&client->dev, "enable");
^
In file included from /home/rgu/media_build_experimental/v4l/adp1653.c:39:0:
include/linux/gpio/consumer.h:73:32: note: declared here
struct gpio_desc *__must_check devm_gpiod_get(struct device *dev,
^
scripts/Makefile.build:264: die Regel für Ziel „/home/rgu/media_build_experimental/v4l/adp1653.o“ scheiterte
make[3]: *** [/home/rgu/media_build_experimental/v4l/adp1653.o] Fehler 1
Makefile:1396: recipe for target '_module_/home/rgu/media_build_experimental/v4l' failed
make[2]: *** [_module_/home/rgu/media_build_experimental/v4l] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-6-generic'
Makefile:51: die Regel für Ziel „default“ scheiterte
make[1]: *** [default] Fehler 2
make[1]: Verzeichnis „/home/rgu/media_build_experimental/v4l“ wird verlassen
Makefile:28: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2
rgu@tv-server:~/media_build_experimental$

Any ideas?

Zitat von Tolotos

[...] Any ideas?

Einfach die weiter oben geposteten Patches verwenden.

Sorry - welchen patch? ist da irgendwo ein link, oder muss ich die diffs abschreiben?!

Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT, MAX S8 sowie TT S2-6400 (Teil 3)
Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT, MAX S8 sowie TT S2-6400 (Teil 3)