CityK wrote: > CityK wrote: > >> Hans wrote: >> >>> CityK wrote: >>> >>> >>>> In regards to the tuner type being set twice, that is precisely my point >>>> -- its peculiar and not symptomatic of normal behaviour. That is why I >>>> asked whether you expected it to do this >>>> >>>> >>> I think it is OK. The second setup is probably done by dvb_attach() in >>> saa7134-dvb.c, line 1191. Can you verify that with a debug message? >>> >>> >> Could not verify. (dmesg output provided below at end). >> >> > > Actually, looking at the dmesg output now, it is apparent that you are > correct: > > dvb_init() allocating 1 frontend > > So, its a case of a bit of redundancy now. Michael Krufky wrote: > CityK wrote: >> - Hans' second attempt at this is found in his v4l-dvb-kworld test >> repo... testing this code revealed that analog tv did indeed work >> again withtvtime ... I also noted that there seems to be a bit of >> redundancy nowin terms of the tuner being initialized twice >> >> ... [snip]... >> >> - Hans kworld repo: >> Pros: does provide analog tv functionality for, at a minimum, tvtime. >> Cons: The changes introduced result in, as testing to date has shown, a >> harmless bit of duplication in the way of the tuner being loaded twice. >> kdetv/motv/xawtv, at a minimum, do not work in overlay mode. > > Tuner is _not_ loaded twice. The tuner-simple driver is displaying > itself twice in the dmesg logs, because it is attached twice. I actually knew that, but as a consequence of writing a long reply, late at night, I wasn't fully coherent in my faculties and ended up misreporting the case. > Once for analog, again for digital -- this is *by design*. > > The old code used dvb-pll for the digital side, and tuner-simple for > analog. The common support within those two modules has been merged > together to remove redundancy and allow us to share state between the > two instances of the driver for the same part. > > As tuner-simple registers each side of the interface, it will display > a message to the kernel logs indicating what tuner has been attached > -- this is what you see twice. Mike, thanks for the clarification that the behaviour is intended by design. And looking at the events in conjunction with the above explanation, it all makes sense: tuner 1-0061: chip found @ 0xc2 (saa7133[0]) tuner-simple 1-0061: creating new instance tuner-simple 1-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in) saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 dvb_init() allocating 1 frontend nxt200x: NXT2004 Detected tuner-simple 1-0061: attaching existing instance tuner-simple 1-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in) hermann pitton wrote: > For the second attach of hybrid tuners in digital mode we maybe should print something > pointing to it. > Yes, I agree -- adding something simple to the existing message here might help any future cases of head-scratching by those less knowledgeable of the intricacies. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
