I built a mythtv system for my brother that successfully used a single Hauppauge HVR-950 tuner, but he ran into a problem when he tried to add a second HVR-950 tuner. Based on some threads I've read, it looks like this is a known problem that was fixed recently, so I want to help him update his R5.5 system to the latest V4L driver. He is currently using a V4L driver built using the following procedure:

I am now pondering how to do the update properly. I found these instructionsin the v4l wiki, which essentially suggest that the build should be done from http://linuxtv.org/hg/v4l-dvb . Another thread I read sugggests that the code I originally built from ( http://mcentral.de/hg/~mrec/v4l-dvb-kernel ) was a custom code branch created by a developer named Markus Rechberger, that this code branch is essentially a "dead end", and that support for the em28xx tuners has been merged into the main V4L code base, as documented in this changelog entry.

All of this brings me to the following questions:

1. Where is the correct place to do a V4L build from: http://mcentral.de/hg/~mrec/v4l-dvb-kernel or http://linuxtv.org/hg/v4l-dvb ?

2. It looks like http://linuxtv.org/hg/v4l-dvb is updated continuously, and I don't see any clear way to identify a known-good version of this driver. In essence, it looks like when you do a build from this, you are taking a crap shoot on weather or not the most recent check in works or breaks things. Am I understanding the situation correctly?

3. Assuming the answer to # 2 is yes, any advise on how to best approach the situation and minimizing the odds of picking up a bad version?

Answers to these questions and any other advise / guidance would be greatly appreciated. Thank you!

Marc

That would be linuxtv.org. However, some people might have done some tricks to their own brancs, which is not yet merged with the v4l trunk. That was te case with my Anysee tuner previously. I would still recommend usin the linuxtv.org version.



Unfortunately that seems to be the case. There was a loosely related topic which helped me through getting it to compile.



As far as I know (based on Google) there is not a list of revisions which do compile an which don't. Your best bet is to get the head revision, and if it doesn't compile, get the one before it... In a couple of years you should stumble to a working revision

Hmm... I wonder if I made any sense.

_________________
Jari-Matti

MBE&FE: GeForce MX440, Athlon XP 2000+, MSI KT333 Ultra, onboard audio, 512 MB, 2 x Technotrend T1500 DVB-T, LiteOn DVD±RW 16x DW1650-488C, Seagate 250 GB
FE: 1500MHz Geforce MX200-V, int. audio, 256MB

Makes total sense -- thanks for taking the time to respond! I do have 1 more question -- is there an easy way I can save the drivers and DVB applications that are already installed, so that if the new version makes things worse, it will be easy to revert back to the version that is currently installed. Thanks!

Marc

Well, I guess you could rename the download folder with for example revision number. Besides from that, the only way would be to get a specified revision each with "hg clone".



There must be a better solution to this, but I've used this method, and it works for me.

_________________
Jari-Matti

MBE&FE: GeForce MX440, Athlon XP 2000+, MSI KT333 Ultra, onboard audio, 512 MB, 2 x Technotrend T1500 DVB-T, LiteOn DVD±RW 16x DW1650-488C, Seagate 250 GB
FE: 1500MHz Geforce MX200-V, int. audio, 256MB

I see your point. As long as a retain the sources for the other driver I built, I can always re-install them if the new version doesn't work. That makes sense. Actually, I think I left the sources and the results of the build on his machine, so I don't need to re-fetch it from the on-line repository. Thanks for the idea.

Marc