170 replies to this topic

[Gennar1]

Thanks.
The Noxon DAB stick will probably not work, as there is no support for DAB in OpenPli (or in Linux either), but it doesn't hurt to add it anyway (maybe it will work in DVB-T mode even if it's not officially supported).

By the way, we did a few mistakes adding the Leadtek stick with the latest patch update:
1) new entries in the rtl2832u_usb_table must be added at the end, as the index in the array is used later to initialize the correct stick type;
2) adding the new VID:PID to the table is not enough to enable the new stick: we must also define the stick type (choosing between the 9 types available: rtl2832u_1st_properties to rtl2832u_9th_properties);

The patch in attachment should fix the problems and enable the new sticks (if I associated them with the correct device types).

We need testers...

Attached Files

•  rtl2832-added-new-Terratec-sticks.tar.gz   1.2KB   131 downloads

[pieterg]

thanks, added

[Gennar1]

Hi pieterg,
there is a problem with the patch I posted: it was based on my version of the rtl2832 patch, so it did not apply correctly to Ambrosa's version (because of a few empty lines that I removed).
So this broke the kernel compilation and the entire image build process.

I rebased the patch on Ambrosa's version and merged it with the main patch (dvb-usb-rtl2832.patch).

Please remove the "rtl2832-added-new-Terratec-sticks.patch" patch from the repository and substitute the old "dvb-usb-rtl2832.patch" with the one in attachment.

I compiled the kernel and built the entire image without problems with this version.

Sorry for the inconvenience.

Attached Files

•  dvb-usb-rtl2832.patch.zip   323.98KB   119 downloads

[pieterg]

ok, one combined patch is better indeed.
Hadn't even noticed the build failure yet, because of all kinds of other build errors we didn't even get to the point were the kernel would compile

[LubosD]

I cannot wait, has anybody a hardware USB analyser to record DAB traces ? ;-)

I don't think it's needed. You can use Wireshark to capture data from any USB port.

At any rate, I'd love to see DAB+ support on Linux. I can't believe it hasn't happened yet!

[killerno]

Hi guys,

Could you tell me how to make a driver for DM800?(kernel is 2.6.18-7.3) . Or someone could complie a driver for me? I would be very happy! I have a TERRATEC Cinergy T Stick BLACK DVB-t device. Thank you!!!

[ims]

lsusb:

Bus 002 Device 005: ID 1d19:1102 Dexatek Technology Ltd. DK mini DVB-T Dongle

I have next MSI Digi Vox Micro HD with:

Bus 002 Device 005: ID 1d19:1104 Dexatek Technology Ltd.

Is some chance, that they will be supported under DM800SE ?

Edited by ims, 27 January 2012 - 13:59.

[Gennar1]

You have to take the patch from this thread (or from the ETxx00 Openembedded repo) and try to apply it to the v4l-module tree used by the DM800SE. For sure you will have to manually edit the media/dvb/dvb-usb/Kconfig and Makefile as the patch will not apply cleanly there. This is the easy part, as it's just a cut&paste job. Then you can recompile the kernel and hope that the driver has support for the old kernels. But it's a long shot, as the oldest kernel referenced in the drivers is 2.6.26, so there may be a lot of compilation problems that needs to be fixed. Good luck...

[feitingen]

Hello,

Just wanted to say thanks, and that this works with my Leadtek Research, Inc. RTL2832 [WinFast DTV Dongle Mini], ID: 0413:6a03

It is not in the usb id array, if you add it, it works without problems on my 3.2 debian kernel.

Do you mind if this post is linked to from the linux tv wiki?

[Gennar1]

Thank you for the feedback. I will add the new USB ID in the next revision of the patch.
On my part there is no problem for linking this post on the linux tv wiki.

[Gennar1]

The Leadtek Mini stick has been added a couple of months ago in the OpenPli driver. Unfortunately Ambrosa is really busy in this weeks so he has not updated his GitHub repo recently.

The latest version of the patch for the rtl2832 driver is available on the OpenPli repo:

http://openpli.git.s...6f5e81797ea654a

In particular, this patch will apply directly on all kernels >= 3.0.0 and can be applied also to the current media_build tree so it will work on all kernels >= 2.6.31 (some simple manual editing of the dvb-usb Makefile and Kconfig files may be required to apply the patch, since the patch is based on the OpenPli kernel).

Edited by Gennar1, 29 February 2012 - 17:30.

[R00KIE]

Hello and thank you for making this driver compile and work well with kernel versions up to 3.2. I have been using the driver with a MobiDTV Pro adapter (1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle) without any problems and I have a patch I can share to allow it to use the included remote if anyone is interested.

I have also been maintaining an unofficial driver package for Arch Linux [1] based on the code from the git repo and it has worked well so far, however the driver fails to compile with kernel 3.3. I have been able to trace part of the problem to a change in the kernel headers (I think I got the name right) but I've hit something that is beyond my abilities to solve.

What I would like to know is if there are any plans to update the driver for kernel 3.3, or if there is updated code somewhere already. In case an update is planned is there any estimate when it will be available (and where)?

The initial patch I intended to use for kernel 3.3 is below:

diff -ur a/rtl2832u_fe.h b/rtl2832u_fe.h
--- a/rtl2832u_fe.h 2012-03-29 16:08:13.612269073 +0100
+++ b/rtl2832u_fe.h 2012-03-29 16:10:25.283492607 +0100
@@ -2,6 +2,7 @@
#ifndef __RTL2832U_FE_H__
#define __RTL2832U_FE_H__

+#define __DVB_CORE__
#include "nim_rtl2832_tua9001.h"
#include "nim_rtl2832_mt2266.h"
#include "nim_rtl2832_fc2580.h"
diff -ur a/rtl2832u.h b/rtl2832u.h
--- a/rtl2832u.h 2012-03-29 16:08:13.612269073 +0100
+++ b/rtl2832u.h 2012-03-29 16:10:25.230160130 +0100
@@ -2,7 +2,7 @@
#define _RTL2832U_H_


-
+#define __DVB_CORE__
#include "dvb-usb.h"

#ifndef USB_VID_REALTEK
diff -ur a/rtl2832u_ioctl.h b/rtl2832u_ioctl.h
--- a/rtl2832u_ioctl.h 2012-03-29 16:08:13.612269073 +0100
+++ b/rtl2832u_ioctl.h 2012-03-29 16:10:25.373491163 +0100
@@ -1,6 +1,7 @@
#ifndef __RTL2832U_IOCTL_H__
#define __RTL2832U_IOCTL_H__

+#define __DVB_CORE__
#include "rtl2832u_fe.h"
#include "rtl2832u_io.h"

diff -ur a/rtl2832u_io.h b/rtl2832u_io.h
--- a/rtl2832u_io.h 2012-03-29 16:08:13.612269073 +0100
+++ b/rtl2832u_io.h 2012-03-29 16:10:25.340158365 +0100
@@ -4,6 +4,7 @@
#ifndef __USB_SYS_RTL2832_H__
#define __USB_SYS_RTL2832_H__

+#define __DVB_CORE__
#include "dvb-usb.h"

extern int dvb_usb_rtl2832u_debug;

[1] https://aur.archlinu...es.php?ID=51225

[Gennar1]

Hi R00Kie,
the answer to your question is in the post above yours

The git tree by Ambrosa is no more mantained due to lack of time. The latest patch in the OpenPli kernel (which is linked above) supports all the kernels up to 3.4. A few days ago I applied it to the brand new 3.4-rc1 without any problem.

In the 3.3 kernel all the media drivers have moved to the new DVBv5 API, and a compatibility layer has been added in dvb-core to translate DVBv3 calls to the new API. You can see the changes looking for the define V4L2_ONLY_DVB_V5.

There are also a few new USB IDs and a bugfix for signal strength.

[R00KIE]

Oh thats's great, thanks for that information. I will cook a package for Arch based on this and will report on the result.

Another thing I'd like to ask is related to remote controls, are there any plans to make remote control handling more generic? If I'm not seeing it wrong, the remote control code<->key translation is hardcoded in rtl2832u.c and it will work only well for one remote, it would be nice if there could be another way of doing it (such as having /dev/lirc0 created). If a correct mapping is hardcoded using inputlirc [1] works well though.

Another thing is related to the IR protocols, from the remotes I have tested (the ones I have at home and the one that came with the receiver), only the ones using the NEC protocol seem to work, I have tested with one that uses RC6 (Sony RM-836) and every key returned the same code (using the module option debug=4 and looking at the dmesg output), is this a known problem, no one ever really tested this or is there something I might be doing wrong?

[1] http://inputlirc.sourcearchive.com/

[R00KIE]

I've tested the patch and there was a small glitch

/tmpfs/dvb-usb-rtl2832u-git-mine-update/src/build_dir/rtl2832u.c:775:4: error: 'USB_PID_WINFAST_DTV_DONGLE_MINI' undeclared here (not in a function)

It seems that USB_PID_WINFAST_DTV_DONGLE_MINI is not defined, however this is the same PID as was already defined as USB_PID_LEADTEK_WARM_3 in ambrosa's git repo so I have fixed/reverted it with:

diff -ur b/rtl2832u.c c/rtl2832u.c
--- b/rtl2832u.c	2012-04-02 16:32:43.115887641 +0100
+++ c/rtl2832u.c	2012-04-02 17:28:07.455836234 +0100
@@ -826,6 +826,7 @@
 
 	{ USB_DEVICE(USB_VID_LEADTEK, USB_PID_LEADTEK_WARM_1)},		// 60			
 	{ USB_DEVICE(USB_VID_LEADTEK, USB_PID_LEADTEK_WARM_2)},		// 61
+	{ USB_DEVICE(USB_VID_LEADTEK, USB_PID_LEADTEK_WARM_3)},		
 
 	{ USB_DEVICE(USB_VID_YUAN, USB_PID_YUAN_WARM)},			//62
         { USB_DEVICE(USB_VID_YUAN, USB_PID_YUAN_WARM80)},		//63
@@ -844,8 +845,6 @@
 	
 	{ USB_DEVICE(USB_VID_GOLDENBRIDGE, USB_PID_GOLDENBRIDGE_WARM)},	//75
 
-	{ USB_DEVICE(USB_VID_LEADTEK, USB_PID_WINFAST_DTV_DONGLE_MINI)},	// 76
-
 	{ USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_00D3)},		// 77
 	{ USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_00D4)},		// 78
 	{ USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_00E0)},		// 79
diff -ur b/rtl2832u.h c/rtl2832u.h
--- b/rtl2832u.h	2012-04-02 16:32:43.115887641 +0100
+++ c/rtl2832u.h	2012-04-02 17:28:48.065194478 +0100
@@ -114,6 +114,9 @@
 #endif
 #define	USB_PID_LEADTEK_WARM_1					0x6680
 #define	USB_PID_LEADTEK_WARM_2					0x6F11
+#define	USB_PID_LEADTEK_WARM_3					0x6A03
+
+
 #ifndef  USB_VID_COMPRO
 	#define USB_VID_COMPRO						0x185B
 #endif 

I have tested this with kernels 3.0.26, 3.2.13 and 3.3, builds cleanly and works fine

Good work on getting signal strength reporting fixed.

OT
How do I edit posts? I was planning to add this info to my previous post but I didn't see any way to edit it.

[dAF2000]

OT
How do I edit posts? I was planning to add this info to my previous post but I didn't see any way to edit it.

There is a time out on editing your posts to prevent that writers change their post after a long time while the readers don't notice that.

[Gennar1]

I've tested the patch and there was a small glitch

/tmpfs/dvb-usb-rtl2832u-git-mine-update/src/build_dir/rtl2832u.c:775:4: error: 'USB_PID_WINFAST_DTV_DONGLE_MINI' undeclared here (not in a function)

It seems that USB_PID_WINFAST_DTV_DONGLE_MINI is not defined, however this is the same PID as was already defined as USB_PID_LEADTEK_WARM_3 in ambrosa's git repo so I have fixed/reverted it with:

Hi R00KIE,
probably this is because I added the new USB ID to dvb-usb-ids.h, instead of keeping it inside the rtl2832 driver. The patch probably failed to to apply this hunk to your kernel tree so later you got the "undefined" error.

Regarding the IR support, here we develop software for set-top-boxes so we already have good remotes. We don't use the cheap remotes that are usually bundled with USB tuners, so there is no particular effort in this kind of developments.

Thanks for the feedback, it's always appreciated.

Regards,
Gennar1

[R00KIE]

Hello Gennar1,

I see now that I missed that little change to dvb-usb-ids.h, this because I'm not trying to patch the whole kernel sources but I'm compiling the driver standalone (using the kernel headers supplied by the distro).

Regarding the IR support, my question was about letting the USB tuner work with any remote, however you have confirmed what I suspected, you already use decent IR receivers so it wouldn't make sense to waste time trying to make the IR receiver inside the USB tuner work with all remotes. I'll leave the exercise of patching the sources to support the bundled remote (or others) up to the user (or the user can just use a decent IR receiver and be done with it).

Thanks for all the help.

[vin]

How about the Terratec Cinergy TStick RC (Rev. 3)?
Bus 002 Device 005: ID 0ccd:00d3 TerraTec Electronic GmbH

Any possibility to get this device working?

[vin]

According to this site, it should be based on a Realtek RTL2832U / Elonics E4000 combination.
http://linux.terratec.de/tv_en.html

Can I get my hopes high?