Mike, Thanks for the response. I've actually gone ahead and ordered an HDHomeRun, so this won't be an issue with me at the moment.
In any case, I'm now sorting something different out: Having 'upgraded' (as in, created a separate new bootable filesystem) from Ubuntu to Debian 'squeeze' (since Ubuntu is apparently abandoning the armv5tel architecture), I see all the appropriate driver messages, firmware loading, etc., and mythtv-setup shows my "WinTV HVR-1950 Model Category 7 [pvrusb2]" as an "Analog V4L capture card" (and it shows up under DVB and even MPEG-4 types, though without an associated audio device in both cases). However, the "IVTV MPEG-2 encoder card" selection (which I think I'm supposed to be using) simply has "Failed to open" under "Probed info". I'm using the same firmware files (v4l-cx2341x-enc.fw, v4l-cx25840.fw, v4l-pvrusb2-29xxx-01.fw and v4l-pvrusb2-73xxx-01.fw) as under the Ubuntu installation, which worked fine with the Ubuntu software (and still does when I boot that image). So it looks as if the probing for various tuner types, or the answer, differs somehow between the two systems on the same hardware and the same firmware. On the Debian system, attempting to use it as an 'Analog V4L capture card' shows no audio device, and doesn't give me the option to scan for channels. Thanks again, Charles ________________________________ From: Mike Isely <[email protected]> To: Communications nexus for pvrusb2 driver <[email protected]> Sent: Sat, April 10, 2010 10:22:53 PM Subject: Re: [pvrusb2] Is it possible to discriminate between two HVR-1950s? Charles: The pvrusb2 driver itself doesn't do anything to make the device's serial number visible to udev. HOWEVER, it was later discovered that the udev is seeing the serial number anyway, very likely because the number is being provided by the FX2 controller itself as part of the generic USB endpoint configuration data. I had erroneously thought that I needed to provide the serial number to udev, when in fact it's already there. This actually makes some sense because by the time the pvrusb2 driver is connected to the hardware, udev already knows everything it is going to know about the device. So you should be able to construct a rule in udev to uniquely identify each device. There is an old e-mail on this list that talks about this discovery. I should be able to dig it up if you can't find it. -Mike On Sat, 10 Apr 2010, Charles Green wrote: > I currently have a single HVR-1950 on my system (SheevaPlug), attached > to our cable TV feed, working quite nicely for analog. > > I need to add a second tuner to this system for over-the-air ATSC, > attached to an antenna in my attic. > > In following this mailing list for a while, I seem to recall that > unique serial number information is not made available by the driver > for, e.g., 'udev' to be able to set up unique and consistent /dev > names upon reboot. This wouldn't be a problem if all tuners got the > same signal feed, but in this case they won't. > > It's my understanding that these USB devices would be processed in > whatever order they appear on the hub, not necessarily related to > where they're plugged in. > > If it's not feasible to differentiate these, I'll probably go with > something like an HDHomerun; the single tuner version at least appears > to be cheaper than the Hauppauge unit anyway. > > Thanks for any guidance you can offer. > > -Charles Green > > > > > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
