Jump to content


Member Since 22 Aug 2011
Offline Last Active 02 Nov 2015 21:35

Posts I've Made

In Topic: RTL2832U chipset support proposal

11 September 2013 - 10:59

Hi guys, in attachment you can find a new version of the Realtek driver patch for 3.7+ kernels.


The only changes since the latest version are 2 more USB PIDs that were requested a long time ago:


added definition of a new Terratec PCI-E stick (using the rtl2832u USB chip):
- TERRATEC Cinergy T Stick+ [ID 0ccd:00d7]
(thanks to sfasf);

added definition of a new Leadteck USB stick:
- Leadtek WinFast DTV2000 DS PLUS [ID 0413:6f12]
(thanks to michaelp);


In Topic: RTL2832U chipset support proposal

30 August 2013 - 15:02

Looks like the SDR guys did some good progress since last time I checked the project ;)

FM and DAB reception is now possible on Ubuntu, according to the webpage you linked :P 

Thanks for the update. 

In Topic: RTL2832U chipset support proposal

30 August 2013 - 11:02

Hi Kazlift,

unfortunately there is no way ATM to get the FM feature working on OpenPLI.

This is because the RTL2832 cannot demodulate the FM signal by itself: what you get from the chip is a series of raw digital samples at high rate of the FM modulated signal. We would need to demodulate them using a software demodulator, which is not available for Linux.

There is some work going on in the SDR (Software Defined Radio) project, so maybe one day we will be able to get FM radio from the RTL2832.

In Topic: Support for kernel-module-dvb-usb-pctv452e in current 3.8.7 kernel

30 July 2013 - 11:02

Yesterday pieterg pushed a patch that should fix the problems that many USB tuners showed with the new kernels. Please update your boxes and report if the problem is effectively solved.

In Topic: New kernel 3.8.7

29 July 2013 - 22:34

It's a kernel bug, so we have to wait until a "magic patch" comes out.

Looks like I finally have the 'magic patch'.
I traced it down to http://git.kernel.or...3a9070827796cfc

So indeed, a MIPS-only issue.


Great news! Unfortunately I will not be able to test it for a while.

BTW, how do you tracked the issue down to that patch? I was planning to run a full git bisect between 3.6 and 3.8.7...


Anyway, great job as usual! TY!