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 clarify this and fix the driver that is faulty. > Tried to create the hook on Initialize(), still crashes on exit(). Well, then I guess you'll need to do some debugging to find out what really goes wrong here. > Haven't tried your patch, because as far as I know the driver claims it > can do QAM256, and even if that was disabled today it would take some > time to get into all linux distributions... Btw it even claims to > support QAM256 on the product package, but it still doesn't work. I > guess that's the reason they are so inexpensive here... At any rate, these things *must* be fixed in the driver! Even if it takes a while for a fix to get into the main kernel source. Klaus > 2010/4/5 Klaus Schmidinger <klaus.schmidin...@tvdr.de > <mailto:klaus.schmidin...@tvdr.de>> > > On 05.04.2010 12:43, Teemu Rantanen wrote: > > Hi, > > > > I tried also without delete cDeviceHook but it still crashed... > > Please try creating the cReddoDeviceHook in > cPluginDisableReddoQAM256::Initialize(), > as suggested in PLUGINS.html. > > > 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) > > This is what I get here: > > r...@video:/home/kls/vdr/VDR > ls -l > /sys/class/dvb/dvb0.frontend0/device/subsystem_* > -r--r--r-- 1 root root 4096 2010-04-05 16:25 > /sys/class/dvb/dvb0.frontend0/device/subsystem_device > -r--r--r-- 1 root root 4096 2010-04-05 16:25 > /sys/class/dvb/dvb0.frontend0/device/subsystem_vendor > > r...@video:/home/kls/vdr/VDR > ls -l > /sys/class/dvb/dvb0.frontend0/device/id* > ls: cannot access /sys/class/dvb/dvb0.frontend0/device/id*: No such > file or directory > > Maybe a bug in the driver? > > > - You need to set strtoul() base as 16 as the files don't have 0x in > > front of the hex > > r...@video:/home/kls/vdr/VDR > cat > /sys/class/dvb/dvb0.frontend0/device/subsystem_device > 0x0000 > r...@video:/home/kls/vdr/VDR > cat > /sys/class/dvb/dvb0.frontend0/device/subsystem_vendor > 0x13c2 > > Maybe the "reddo" driver behaves differently than the FuSi driver? > > > What about making this an utility method in VDR? Give device file name > > and return id... > > Will do. > > > Have you tried whether it works with my patch? > In that case you wouldn't even need the whole plugin. > > Klaus > > > ------------------------------------------------------------------------ > > _______________________________________________ > vdr mailing list > email@example.com > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr _______________________________________________ vdr mailing list firstname.lastname@example.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr