On Thursday 21 December 2006 14:56, Martin Dauskardt wrote: > just a quick feedback: > > as always, tested with vdr (pvrinput + pvr350-Plugin), which work > well with 0.8 and 2.6.18 with latest v4l-dvb hg. > > This time I merged the trunk instead of 0.8 in latest v4l-dvb hg, so > it should be like 2.6.19. No compile problems. > > ivtv log looks good, but I am not sure about the last lines regarding > the remote (I want to use lirc_i2c !!)
Nothing was changed in ivtv regarding i2c, so any changes in there are caused by kernel/v4l-dvb problems <snip> > Needless to say that the remote does not work... I wonder if v4l-dvb + 2.6.18 will work. This might be a compatibility problem between the two. > OSD looks like this, although ivtv_fb was loaded with compatibility > mode: http://drseltsam.device.name/vdr/trunk_osd.jpg > can`t see anything :-( Ian, does this ring a bell? > pvrinput-Plugin (which uses only the encoder) does not work. I > already removed the 3:2-pulldown stuff in the code, but there seems > to be more which breaks compatibility. Do you have more information on this? What exactly does not work? > > pvr350-Plugin (which uses only OSD and decoder): When using a > DVB-T-card, I can watch TV (of course no OSD), and channel switching > using decoder stop/start is now as I always wanted it to be. The new > stop mechanism seems to works pretty good! OK. There should be no more need to call IVTV_IOC_STOP/IVTV_IOC_PLAY as opposed to IVTV_IOC_START/STOP_DECODE. The ivtv_cfg_stop_decode struct now has a flags field that can be used to set the stop behavior. I've spent quite some time testing that to get it to work properly. Hans _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
