After running a videodev viewer on the local bttv device, the dvb videodev device can not be open()ed anymore, returning errno=ENXIO "no such device" for the dvb's videodev (of siemens dvb-s 1.3 card) which devfs has put under /dev/video#.
TVeng: [tveng2.c] p_tveng2_open_device_file (line 99) open() failed: No such device TVeng: [tveng1.c] p_tveng1_open_device_file (line 117) open() failed: No such device TVeng: [tveng1.c] p_tveng1_open_device_file (line 118) open() failed: '/dev/ost/video1':
The szap can still open the frontend device and it seems to be working. Targetting the videodev viewer directly on to /dev/dvb/adapter0/video0 does not work (bad ioctl).
TVeng: [tveng2.c] p_tveng2_open_device_file (line 110) VIDIOC_QUERYCAP failed: Invalid argument TVeng: [tveng1.c] p_tveng1_open_device_file (line 126) VIDIOCGCAP failed: Invalid argument open() failed: '/dev/dvb/adapter0/video0':
Looking into the dvb sources says that it doesn't grok any videodev ioctl anyway - doh, what a surprise!
Anyway, the devfs did create a /dev/v4l/video1 for the dvb video device - it goes a bit further here but the `zapping` application goes out for a coredump a little later. The only suspicous lines so far looks like this in log/messages
Jun 6 17:57:55 pc3 kernel: dvb: VIDIOCGPICT called: b:32768 c:32768 s:32768 d:16 p:3 [...] Jun 6 17:57:55 pc3 kernel: dvb: VIDIOCSWIN called: clips: 0, x:0, y:0, h:192, w:64 Jun 6 17:57:55 pc3 kernel: saa7146: ==> calculate_video_dma1_overlay: illegal values: y: 0 h: 192 d: 0 b: 0 base: 0
And I guess that "illegal" comes from bitdepth set to zero here!
any clues? -- guido http://google.de/search?q=guidod GCS/E/S/P C++/++++$ ULHS L++w- N++@ d(+-) s+a- r+@>+++ y++ 5++X- (geekcode)
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
