Category | terratec

I'm continuing to try to flush out my backlog of patches. It turns up I missed a patch when I did the Terratec Cinergy T XS USB support, which resulted in the remote control not working. Setup a new tree and asked the user to test (since I've already sent back the hardware to the user I borrowed it from). http://kernellabs.com/hg/~dheitmueller/ttxs-remote Also setup a tree with fixes for the Geniatech x8000 for a user I helped on the #linuxtv IRC channel a couple of weeks ago. http://kernellabs.com/hg/~dheitmueller/geniatech_x8000 I started evaluating what would be required to get VBI support...

---

I received an email tonight from a user who characterized me as "impolite" for not replying to his previous email in a timely manner (two days). I make an effort to take constructive criticism in stride, and am always looking for ways to improve the quality of the free volunteer services I provide to the community. In that light, I took a few minutes to take an inventory of the various things I did this week to see if I could have avoided the dissatisfied email. So, what have I been doing in the last week? Gained access to Andreas Lunderhage's debugging environment, analyzed the USB traces...

---

I was contacted by a developer in Italy who had already started work on an xc4000 driver and was nice enough to send me his code. It needs *alot* of work (in fact, it doesn't work at all), but it's a starting point. http://kernellabs.com/hg/~dheitmueller/pctv-340e Added an initial board profile for the 340e, and setup the GPIOs based on the information the vendor was kind enough to provide. I2C read operations to the xc4000 are failing, which I suspect is a problem with the xc4000 being still held in reset. As far as I can tell, there is no i2c gate on the board blocking access to the tuner...

---

Well, the 59 emails exchanged with Terratec users finally paid off, at least for the version of the product that uses the zl10353. With the help of Simon Kenyon, who was nice enough to let me SSH into his environment for a few hours, I was able to identify the problem, which ended up being a misconfiguration of the i2c gate for this board. To make things more confusing, setting the i2c gate parameters on the zl10353 when there is no tuner behind the gate actually wedges the i2c bus. As a result, the xc3028 initialization and first tuning attempt would go through, but after the first call to close...

---

I spent pretty much all evening continuing to look at why neither variant of the Terratec Cinergy T XS works. It seems that across the v4l-dvb codebase there is a significant inconsistency in what module is responsible for the i2c gate control. There are cases where the tuner driver opens/closes the gate. There are cases where the demod open/closes the gate. There are cases where the demod *only* closes the gate, presumably because the tuner or the PLL opened the gate. I suspect what might be the problem is *nobody* is opening the gate, so the write commands being sent to the tuner are being...

---

I was out of town for a few days last week, hence no updates during that period.... Fixes continue at a slow pace for the 950q analog support. A user pointed out problems with colorspace configuration when using the 950q with gstreamer. I spent most of Monday night debugging the issue, which I now believe is some unimplemented v4l ioctl() calls failing which result in gstreamer falling back to a default colorspace. Most people seem pretty happy now with the support since the xc5000 fixes went out. Email continues back and forth with Terratec Cinergy T XS users as I add more and more debug...

---

Still continuing to clear out my backlog of miscellaneous fixes. Added support for the K-World 2800d (thanks to Paul Thomas for loaning me the hardware and being so patient). While doing that work, I managed to uncover a minor bug in the em28xx audio code (the /dev/audio1 device file was being created even if the device didn't support audio). One thing I had noticed over the last few months is cases where users would report that ATSC scanning worked but tuning did not. In all of these cases, it turned up that the user was connected to a USB 1.1 port (12 Mbps). For ATSC, that means only about...

---