Re: [mythtv-users] Anyone tested the DVB-T2 dual tuner TBS6280?
Thanks for sharing your experience. On Sat, Aug 13, 2011 at 11:08 AM, Lawrence Rust l...@softsystem.co.uk wrote: The stock v4l sources supplied are old (from around 2.6.35) and don't contain many current fixes. This isn't a problem per-se unless you intend to use the card with another v4l card. In this case your brand new, bug fixed drivers are replaced by TBS's version which may or, as in my case, may not work. I have 2 other older cards that I intend to use it with, but currently I'm using Ubuntu 10.04 LTS which have a 2.6.32 kernel, so this would not be a problem, but later when I upgrade to 12.04 LTS and a newer kernel this will be problematic. Since I can't trust that TBS will deliver newer drivers. I repeatedly mailed TBS support at supp...@tbsdtv.com to ask how I could only install the 6981 driver but never got an answer. In desperation I setup a git tree of 2.6.35 and merged it with the TBS drivers in order to separate their changes. Finally after many hours I have a set of patches that I can apply to 2.6.39 that produce a working driver. Is it possible to mix modules based on different versions of v4l? To me that looks like it will work as long as the core infrastructure is the same, but as soon as some common data structure that is used by the obj files is changed it will break and you might not notice directly. Just as you say with the IR changes, but also more subtle changes by adding/removing elements in structures. Be warned that if you run a 2.6.38 or later kernel then the IR RC won't work because of significant changes to the RC architecture that TBS don't like (see http://www.tbsdtv.com/forum/viewtopic.php?f=22t=929 and http://www.tbsdtv.com/forum/viewtopic.php?f=22t=110start=90#p2693 ) In the links you refer to the driver author (at least he seems to be the author) states that he has not upgraded to the latest IR code due to compatibility issues between the CX23885 and IR. /Harald -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [mythtv-users] Anyone tested the DVB-T2 dual tuner TBS6280?
On Mon, Aug 15, 2011 at 8:11 PM, Simon Hobson li...@thehobsons.co.uk wrote: Date: Sat, 13 Aug 2011 22:08:30 +0300 From: Turbosight Europe euro_supp...@tbsdtv.com ... also, in case of TBS 6280 there is something else you should know - currently we keep two separate Linux drivers: one that support DVB-T only and another that supports DVB-T2 only. that's because we want more people to test those two drivers before we merge them and it's more efficient to locate the problem in case a customer report such. so, the driver for TBS 6280 you can find on our website supports DVB-T only, but it can be switched to support DVB-T2 very easy. so, single driver that supports DVB-T and DVB-T2 will be released after we're sure both codes are bug-free. so, far feedback we received doesn't reveal any serious bugs and reported problems were fixed - as i mentioned we already have customers in UK that are Linux users and use the card to watch DVB-T2 signal in UK. OK so this states that the current drivers don't support both DVB-T and -T2 simultaneously. This is good to know since this would be my common usage, going to record DVB-T2 on one of the tuners while recording DVB-T on the other. /Harald -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Anyone tested the DVB-T2 dual tuner TBS6280?
Thanks all for your quick answers.
On Tue, Aug 9, 2011 at 1:10 PM, Bjørn Mork bj...@mork.no wrote:
There's a binary-only tbs62x0fe_driver for x86_{32,64} in the archive,
so it _might_ work. But I don't think anyone here will recommend
something like that...
Yes, this is what I was afraid of. That it was binary drivers, and I
agree that this usually only leads to problems when integrating it
with kernels that was not thought of by the developers.
Since I unfortunately don't have time to reverse engineer this binary
driver, I think I wait for another dual tuner DVB-T2 card shows up.
Thanks,
Harald
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Call for Testers - dib0700 IR improvements
Hi, Thanks for working on improving the Nova T 500 performance, it is much appreciated, and let me know if you need further help with debugging it. I tried your dib0700-ir tree. My problems with the Nova T 500 and the 1.20 firmware have been warm reboots. Before your patch a warm reboot would give I2C errors in dmesg log with the 1.20 FW, hence I have only used my machine with cold boots since my upgrade this xmas. With the 1.10 FW and Ubuntu 7.04 + v4l tip sometime in 2008 the system have run without much problems including frequent warm reboots for 2 years. Sorry to say this patch does not solve the problem to have a working IR after a warm reboot see dmesg logs below. I have not seen any problems with high load before, so can't give any info on that matter more than it is certainly low now. The I2C errors I saw before your patch come shortly after a warm reboot (see last dmesg log included), but have not had any problems after cold boots for the past week the system have been recording. I run on: Linux hgu 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux Motherboard: ABIT IL-90MV 945GT Mobile S478 HDMI mATX CPU: Intel Core 2 Duo Mobile T5600 1.83GHz 2M DVB-T cards: Hauppauge WinTV Nova-T 500 DVB-T Twinhan VisionPlus DVB-T In a bad reception area (the Twinhan can't acceptably receive all the channels the Hauppauge can) /Harald dmesg logs: Warm reboot (after ubuntu 9.10 2.6.31-16 standard modules) got non-working remote but working video [8.282314] dib0700: loaded with support for 14 different device-types [8.282568] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [8.282615] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [8.282798] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [8.311479] DVB: registering new adapter (bttv0) [8.396083] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)... [8.509562] usbcore: registered new interface driver snd-usb-audio [8.578470] MT2060: successfully identified (IF1 = 1228) [9.107028] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [9.107285] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [9.113153] DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... [9.119744] MT2060: successfully identified (IF1 = 1235) [9.490288] dst(0) dst_get_device_id: Recognise [DTTDIG] [9.490294] DST type flags : 0x10 firmware version = 2 [9.531093] dst(0) dst_get_mac: MAC Address=[00:08:ca:30:10:39] [9.531103] DVB: registering adapter 1 frontend 0 (DST DVB-T)... [9.684982] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1e.0/:03:06.2/usb2/2-1/input/input6 [9.685059] dvb-usb: schedule remote query interval to 50 msecs. [9.685066] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [9.685327] dib0700: rc submit urb failed Cold boot (directly after the previous) got working remote and video [ 19.445048] dib0700: loaded with support for 14 different device-types [ 19.445747] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 19.445754] usb 2-1: firmware: requesting dvb-usb-dib0700-1.20.fw [ 19.498041] usbcore: registered new interface driver snd-usb-audio [ 19.508086] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 19.508115] HDA Intel :00:1b.0: setting latency timer to 64 [ 19.547850] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 19.586410] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS... [ 19.586598] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 19.699301] dst(0) dst_get_device_id: Recognise [DTTDIG] [ 19.699310] DST type flags : 0x10 firmware version = 2 [ 19.741032] dst(0) dst_get_mac: MAC Address=[00:08:ca:30:10:39] [ 19.741042] DVB: registering adapter 0 frontend 0 (DST DVB-T)... [ 19.848324] e1000e :02:00.0: irq 26 for MSI/MSI-X [ 19.904203] e1000e :02:00.0: irq 26 for MSI/MSI-X [ 19.904842] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.917288] dib0700: firmware started successfully. [ 19.945541] kjournald starting. Commit interval 5 seconds [ 19.946387] EXT3 FS on sda1, internal journal [ 19.946397] EXT3-fs: mounted filesystem with writeback data mode. [ 20.019719] __ratelimit: 9 callbacks suppressed [ 20.019723] type=1505 audit(1262768018.239:14): operation=profile_replace pid=1011 name=/usr/share/gdm/guest-session/Xsession [ 20.021747] type=1505 audit(1262768018.243:15): operation=profile_replace pid=1013 name=/sbin/dhclient3 [ 20.022550] type=1505 audit(1262768018.243:16): operation=profile_replace pid=1013 name=/usr/lib/NetworkManager/nm-dhcp-client.action [ 20.022984] type=1505 audit(1262768018.243:17): operation=profile_replace pid=1013 name=/usr/lib/connman/scripts/dhclient-script [
