Linux Treiber

[olebowle]

Altough I removed every #include <asm/system.h> with the following one-liner:

Code: [Select]

for file in  $(grep -R 'asm/system.h' . | cut -d':' -f1); do sed -i '/asm\/system.h/d' $file; done
I still encounter a compiling error on kernel 3.4.2:

Code: [Select]

media_build/v4l/timblogiw.c: In function 'buffer_queue':
media_build/v4l/timblogiw.c:569:3: error: too few arguments to function 'fh->chan->device->device_prep_slave_sg'


[mastix]

I still encounter a compiling error on kernel 3.4.2:

Code: [Select]

media_build/v4l/timblogiw.c: In function 'buffer_queue':
media_build/v4l/timblogiw.c:569:3: error: too few arguments to function 'fh->chan->device->device_prep_slave_sg'


Since it was in a file that is not used by my system, I've just removed the condition and it worked pretty fine (and still does).

[tst]

Just want to note, that I've managed to get the USB Receiver up and running on an armv6 based RaspberryPi.

Very quick guide:

1. Enable DVB-USB and I2C Support on the Pi kernel (Howto: http://elinux.org/RPi_Kernel_Compilation)

2. Compile the media_build drivers against the kernel sources from step 1.

3. Install kernel, drivers and firmware on the Pi and enjoy (more or less).

(4. Install vdr and the streamdev plugin to stream the signal to your local network)

There is a dmesg error message "i2c message failed" right after plugging in the USB receiver, but scanning and watching works. Sound is a bit laggy though. The CPU usage is around 40% (with 1 client connected to the vdr streaming server). So doing anything else on the Pi results in a very very laggy stream.

[davy]

Hi,
Thanks for these usefull feed-back.
I assume that only mpeg4 can be watched in the raspberry as it mpeg2 codecs are not supported. Doesn't it ?

[tst]

As described here you can watch mpeg2. The only handicap is that there's no hardware acceleration for mpeg2 at the moment.

[davy]

So, you're confirming that Raspberry-pi is powerful enought to software-decode Mpeg2 TV streams and hardware-decode HD streams without too much lagg ?
What distrib are you using ? Debian, Openelec ?

[tst]

Hi,

I've tried watching TV directly on the Pi using the Debian Wheezy Beta Image and Mplayer without any tweaks or something (that means everything is software decoded): The stream is very slow and stuttering (CPU usage is around 80%).

But as far as I know the player shipped with OpenELEC is currently the only one, which able to use the Pi's mpeg4 hardware decoding features. If there's time, I'll try it during the weekend.

Using the Pi as an IPTV streaming server works quite well (as in "not perfect but it could be fixed").

[mastix]

Hi guys,

just wanted to know: What's the current status on integrating these drivers into the kernel? Are there any kernel builds available that contain this driver?

Greetz,

mastix

[Gerald]

@mastix: I have had success on Debian with 2.6 and 3.2/3.3 kernels... Just follow this thread.

[tst]

Using the Pi as an IPTV streaming server works quite well (as in "not perfect but it could be fixed").

Just a quick note for Pi enthusiasts: IPTV Streaming works much better (10-15% drop in CPU usage) with a hardfp optimized distribution (e.g. Raspbian).

[davy]

@Mastix
Max from DVBSKY try to include his patches to v4l-dvb code : http://patchwork.linuxtv.org/patch/10680/
and http://patchwork.linuxtv.org/patch/10849
Unfortunatly, there was a dispute about f... copyright so it seems to be on standbye for a while...
Recently, Max seems to try again : http://www.mail-archive.com/linux-media@vger.kernel.org/msg48861.html
Let see what happens with that because I think it won't be integrated in any kernel before it's integration in v4l-dvb.

@tst : You still talk about streaming & not displaying, don't you ? Good to know that raspberry can be use as low consumption streaming server !
What about displaying mpeg4 ?
For the mpg2 issue I've seen this treat that seems interesting : http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=5641&sid=8f236c7ea8052695a0e5612e0138bad3

[tst]

What about displaying mpeg4 ?

The RPi has licensed gpu decoding for MPEG4 (I guess this means DivX/Xvid) and h.264. But at the moment the (simple) omxplayer is the only one, which is using gpu decoding. More featurerich players (especially those which can handle DVB devices or playlists) like VLC or mplayer aren't patched yet. This means the Pi people have to wait until VLC supports the Raspberry Pi in order to watch TV. Without gpu decoding watching MPEG4 video is a mess.

[elesar]

Hello,

I'm trying to use this card on a mythtv server. Unfortunatly it seems the driver close all the time the device. Some software reopen it all the time some are following the guidelines. I think the persons at dvbsky are unaware of that, and they haven't answered my emails.

Right now to make it works I have to run in background femon to keep them open.

The problem is describe here : http://code.mythtv.org/trac/ticket/10830

Anyway the system like this is not stable, I warn against using this card with mythtv until this problem is fixed.

Can someone help ?

[olebowle]

I still encounter a compiling error on kernel 3.4.2:

Code: [Select]

media_build/v4l/timblogiw.c: In function 'buffer_queue':
media_build/v4l/timblogiw.c:569:3: error: too few arguments to function 'fh->chan->device->device_prep_slave_sg'


Since it was in a file that is not used by my system, I've just removed the condition and it worked pretty fine (and still does).

I set desc to 0 and indeed it works a treat. Thanks.

[warpme]

Hi *

FYI
I just back-ported 20120721 S952 drivers to 3.3x & 3.5.x kernels. (attached)
I prefer minimally-intrusive kernel tree patching + recompile over installing separate V4L, as second approach is potentially risk if You have other tuners in system which are not covered by media build V4L instance.
I fix also small bug related to not initializing BER level (original driver reports random values if read_ber is called too soon after tune).
For S952 cards, attached patches are in pair with drivers available on DvbSky site.

I have this card running under MythTV 0.25.2 + Unicable with great success (so far 4 weeks of 24x7 operation, 600+ recordings)

-br