So I am now at the point where I am ready to start debugging signal lock. This is the phase in the project where all the code is written but has never actually been tested/debugged. My situation however is complicated by the fact that I do not actually have access to a DVB-T signal currently.
While I will be soliciting testers in general once I have something that I think basically works, at this point, I need one experienced user with access to a DVB signal who can provide an environment for me to remotely debug the board.
The ideal candidate:
- Owns a PCTV 340e
- Has used DVB devices under Linux in the past
- Owns at least one other DVB board other than the PCTV 340e that is supported under Linux
- Has access to a reliable DVB-T signal
- Can provide a “known good” channels.conf created with their other tuner
- Has recompiled the v4l-dvb codebase from source in the past.
- Can provide ssh access to a PC that has both the 340e connected and this other card, and doesn’t care if they have to reinstall the OS when the project is done
- The PC should also have installed the gcc toolchain and linux headers required to build v4l-dvb from source
The plan would be that once the environment is setup, I would ssh in, install my v4l-dvb development tree, and then debug dvb signal acquisition with the tuner until it is working. (using the “other device” as a reference). My expectation is the PC would have to be made available for about a week.
If there is someone out there wishing to help who meet the above criteria, please email me at dheitmueller at kernellabs.com.
The sooner I can get the board bootstrapped, the sooner 340e users who have been waiting for support for so long will finally get it.