On 06.04.2010 14:07, Teemu Rantanen wrote:
Hi,
the right way, of course, is to fix the driver, and make vdr check what
device can do. I'm glad Petri had time to test it, and I hope to see the
patch in next version of vdr. But I couldn't use the driver patch even
if I wanted to patch kernel
On 05.04.2010 00:55, Teemu Rantanen wrote:
Hi,
There's a new version of the patch implemented as a plugin. It seems to
work, but there are few things to notice:
- Plugin does not cache which devices are Reddo devices, instead it
probes sysfs every time QAM256 channel is being tuned into
Hi,
I tried also without delete cDeviceHook but it still crashed...
Well, the fixes are basically available in the plugin, as I copied the probe
method (and modified slightly to suit the plugin). Those are:
- The sysfs filenames are idVendor (subsystem_vendor) and idProduct
(subsystem_device)
-
Ok, so the sysfs names of vendor/product are driver-dependent... All my usb
devices have idVendor/idProduct even though only one of them is Reddo.
Tried to create the hook on Initialize(), still crashes on exit().
Haven't tried your patch, because as far as I know the driver claims it can
do
On 05.04.2010 18:14, Teemu Rantanen wrote:
Ok, so the sysfs names of vendor/product are driver-dependent... All my
usb devices have idVendor/idProduct even though only one of them is Reddo.
I'm not saying that what the FuSI driver does is correct, either ;-)
Somebody with more knowledge should
On 04/05/2010 12:57 PM, Klaus Schmidinger wrote:
On 05.04.2010 00:55, Teemu Rantanen wrote:
Hi,
There's a new version of the patch implemented as a plugin. It seems to
work, but there are few things to notice:
- Plugin does not cache which devices are Reddo devices, instead it
probes
Hi,
There's a new version of the patch implemented as a plugin. It seems to
work, but there are few things to notice:
- Plugin does not cache which devices are Reddo devices, instead it probes
sysfs every time QAM256 channel is being tuned into (on any device). It
would be nice if cDeviceHook
Hi,
I bought a Reddo dvb-c usb card last week and wanted to make it a backup
card without a risk of it accidentally tuning into QAM256 channel and
spitting out garbage. It seems to be quite good value for money in Finland
if you want dvb-c usb card and don't need QAM256.
I followed this
Klaus added the ability to limit satellites to certain dvb card in
VDR-1.7.13. However, a lot of users have the need to do device
limiting at the transponder level, which VDR still can't do (and
likely will never do I think, unfortunately). But, Klaus also added
device hooks in VDR-1.7.13 as
I see... I actually noticed cDeviceHook but couldn't figure out if it could
be used or not as there was no reference anywhere for it.
This patch could be very nicely implemented fully in a plugin. I'll try
that...
Thanks,
Teemu
2010/4/3 VDR User user@gmail.com
Klaus added the ability to
VDR User wrote:
I believe the best way to handle this situation is by allowing the
user control over what devices may be used to tune what channels. VDR
can't be smart enough to figure it out due to incorrect bad design
in v4l. Another strong reason to allow this to be configured at the
On 30/10/2009, abbe normal 1abenor...@gmail.com wrote:
hello guys
yes i do think this is a good idea...
as with different tuners they could be used for other lnbs like c -band and
ku
i could only use my s2/s card for services on a c and ku setup then
tune and record from different
On Fri, Oct 30, 2009 at 12:11 AM, Theunis Potgieter
theunis.potgie...@gmail.com wrote:
Does the sourcecap patch not address this whole issue? Even if source
cap or something similar is applied, how will VDR be able to tune to a
8psk turbo-fec type channel if v4l2 does not provide any support
On 29/10/2009, Petri Helin phe...@googlemail.com wrote:
Hi,
I have an USB DVB-C card (Reddo dvb-c, actually a relabelled Tongshi box),
which works very well with the current Linux driver excluding channels with
QAM-256 modulation. Would it be easy to check FE_CAN_QAM_256 in vdr before
On 10/28/09 23:15, Petri Helin wrote:
Hi,
I have an USB DVB-C card (Reddo dvb-c, actually a relabelled Tongshi
box), which works very well with the current Linux driver excluding
channels with QAM-256 modulation. Would it be easy to check
FE_CAN_QAM_256 in vdr before trying to use a device
On Thu, Oct 29, 2009 at 10:13 AM, Klaus Schmidinger
klaus.schmidin...@tvdr.de wrote:
On 10/28/09 23:15, Petri Helin wrote:
Hi,
I have an USB DVB-C card (Reddo dvb-c, actually a relabelled Tongshi
box), which works very well with the current Linux driver excluding
channels with QAM-256
On Thu, Oct 29, 2009 at 1:13 AM, Klaus Schmidinger
klaus.schmidin...@tvdr.de wrote:
On 10/28/09 23:15, Petri Helin wrote:
Hi,
I have an USB DVB-C card (Reddo dvb-c, actually a relabelled Tongshi
box), which works very well with the current Linux driver excluding
channels with QAM-256
There is the isue whereone tunner might be connected to an LNB on a rotor and
another to a fixed. Knowing how the tunner can tune
wouldn't help then.
- Original Message -
From: Klaus Schmidinger klaus.schmidin...@tvdr.de
To: vdr@linuxtv.org
Sent: Thursday, October 29, 2009 1:13 AM
hello guys
yes i do think this is a good idea...
as with different tuners they could be used for other lnbs like c -band and ku
i could only use my s2/s card for services on a c and ku setup then
tune and record from different types of services...
then each tuner could live on a fixed satellite
Hi,
I have an USB DVB-C card (Reddo dvb-c, actually a relabelled Tongshi
box), which works very well with the current Linux driver excluding
channels with QAM-256 modulation. Would it be easy to check
FE_CAN_QAM_256 in vdr before trying to use a device to tune to a
particular channel? In
I have 3 dvb-s cards in one of my boxes. 2 of those cards are able to
tune all channels in my channels.conf. 1 of them can only tune some.
So, the problem is there seems to be no way to specify something like
'use device X,Y,Z' for a certain channel in channels.conf... I had
raised this issue
21 matches
Mail list logo