Wolfgang Rohdewald wrote: > On Dienstag 14 Juni 2005 23:25, C.Y.M wrote: > >>Jun 14 14:07:14 sid vdr[12949]: switching to channel 182 >>Jun 14 14:07:14 sid vdr[14045]: transfer thread ended (pid=14045, tid=360458) >>Jun 14 14:07:14 sid vdr[12949]: buffer stats: 0 (0%) used >>Jun 14 14:07:14 sid vdr[12949]: ERROR (dvbdevice.c,819): Invalid argument >>Jun 14 14:07:14 sid vdr[12949]: ERROR: can't set PID 6437 on device 1 >>Jun 14 14:07:14 sid vdr[12949]: ERROR (dvbdevice.c,831): Invalid argument >>Jun 14 14:07:14 sid vdr[12949]: ERROR: failed to set PIDs for channel 182 on device 1 > > > well, what that patch does is > 1. return -EINVAL instead of the unspecific -1 in many cases > 2. propagate more errors back to the caller > > So maybe you found a bug in vdr or the driver which was there all along but hidden > and maybe harmless. > > it would be interesting to know which vdr statement gets that EINVAL from the driver. > Could you find that out? > Yes, I have a feeling you are correct about there being a bug all along but hidden. This bug, either in VDR, the drivers, or both, is causing the firmware to crash. I would be happy to find out which vdr statement gets that EINVAL from the driver, but my programming skills are fairly limited. P.S. Sorry if I kinda hijacked your original thread with this mplayer stuff. Best Regards,
