DVB-T scan files for Croatia (hr)
Hi Christoph, I'm delivering DVB-T scan files for Croatia. The scan files was tested for regions D01, D04, D05, D08 and are based on information provided by Croatian television (HRT) as well as OiV, so untested ones should be correct also. Frequencies: http://www.hrt.hr/index.php?id=173&tx_ttnews[cat]=102&tx_ttnews[tt_news]=56725&tx_ttnews[backPid]=185&cHash=bdf5a53e91 http://213.147.101.105/DVBT_MUXA_MUXB_Popis_odasiljackih_lokacija.html Parameters SD: http://www.hrt.hr/index.php?id=173&tx_ttnews[cat]=102&tx_ttnews[tt_news]=7456&tx_ttnews[backPid]=185&cHash=d02ef00f9b HD frequencies and parameters: http://www.oiv.hr/default.asp?ru=129&gl=20090710002&sid=&jezik=0 The two already existing files may be removed: hr-Zagreb, hr-Rijeka ... since data in hr-Zagreb is not for any city located in Croatia (in file says Hamburg) and usable channels from hr-Rijeka are already included in file hr-D05. Thank you and best regards, Samuel hr-D01 Description: Binary data hr-D09 Description: Binary data hr-D08 Description: Binary data hr-D07 Description: Binary data hr-D06 Description: Binary data hr-D05 Description: Binary data hr-D04 Description: Binary data hr-D03 Description: Binary data hr-D02 Description: Binary data
Re: TT-Budget/S-1500 PCI crashes with current hg (v4l-dvb-cdcf089168df)
Hi, for the kernel crash, there was a breakage introduced recently so all devices with an IR cause a kernel oops without the following patch: http://patchwork.kernel.org/patch/70126/ Regards On Thu, 21 Jan 2010 08:47:16 +0100, wrote: Hi, My Technotrend S-1500 crashes everytime i load the drivers. This is on 2.6.30.10 kernel with a 2 day old tip from mercurial repo on linuxtv. Reverting back to an older build seems to succeed but i have other tuning problems. Looks like a prob in the infrared driver registration. Is there any way to disable the IR totally as this is a backend server in a mythtv config. Here's the panic/crash: Thanks D Jan 21 10:33:54 home kernel: saa7146: unregister extension 'budget_ci dvb'. Jan 21 10:33:54 home kernel: budget_ci dvb :01:06.0: PCI INT A disabled Jan 21 10:33:54 home kernel: saa7146: register extension 'budget_ci dvb'. Jan 21 10:33:54 home kernel: budget_ci dvb :01:06.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 21 10:33:54 home kernel: IRQ 11/: IRQF_DISABLED is not guaranteed on shared IRQs Jan 21 10:33:54 home kernel: saa7146: found saa7146 @ mem fb6b6c00 (revision 1, irq 11) (0x13c2,0x1017). Jan 21 10:33:54 home kernel: saa7146 (0): dma buffer size 192512 Jan 21 10:33:54 home kernel: DVB: registering new adapter (TT-Budget/S-1500 PCI) Jan 21 10:33:54 home kernel: adapter has MAC addr = 00:d0:5c:07:98:02 Jan 21 10:33:54 home kernel: input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:04.0/:01:06.0/ input/input6 Jan 21 10:33:54 home kernel: [ cut here ] Jan 21 10:33:54 home kernel: WARNING: at fs/sysfs/dir.c:487 sysfs_add_one+0x92/0xb0() Jan 21 10:33:54 home kernel: Hardware name: System Product Name Jan 21 10:33:54 home kernel: sysfs: cannot create duplicate filename '/devices/virtual/irrcv/irrcv1' Jan 21 10:33:54 home kernel: Modules linked in: budget_ci(+) budget_core saa7146 mac80211 cfg80211 btusb bluetooth tun snd_ pcm_oss snd_mixer_oss usb_storage uhci_hcd it87 hwmon_vid i2c_dev cx22702 isl6421 cx24116 cx88_dvb cx88_vp3054_i2c wm8775 v ideobuf_dvb lnbp21 stv0299 tuner_simple tuner_types snd_hda_codec_analog tda9887 tda8290 tuner usblp cx8800 cx8802 cx88_als a dvb_core cx88xx v4l2_common ir_common i2c_algo_bit snd_hda_intel ttpci_eeprom nvidia(P) videodev v4l1_compat tveeprom snd_hda_codec i2c_nforce2 ohci_hcd ehci_hcd floppy ir_core videobuf_dma_sg btcx_risc videobuf_core forcedeth i2c_core snd_pcm snd_timer snd snd_page_alloc [last unloaded: saa7146] Jan 21 10:33:54 home kernel: Pid: 1350, comm: modprobe Tainted: P 2.6.30.10 #12 Jan 21 10:33:54 home kernel: Call Trace: Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? warn_slowpath_common+0x6f/0xd0 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? warn_slowpath_fmt+0x2b/0x30 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? create_dir+0x48/0x90 Jan 21 10:33:54 home kernel: [] ? sysfs_create_dir+0x29/0x50 Jan 21 10:33:54 home kernel: [] ? kobject_add_internal+0xc2/0x1b0 Jan 21 10:33:54 home kernel: [] ? kobject_add+0x2d/0x60 Jan 21 10:33:54 home kernel: [] ? device_add+0xd7/0x550 Jan 21 10:33:54 home kernel: [] ? kvasprintf+0x45/0x60 Jan 21 10:33:54 home kernel: [] ? kobject_init+0x2a/0xa0 Jan 21 10:33:54 home kernel: [] ? device_create_vargs+0xa9/0xc0 Jan 21 10:33:54 home kernel: [] ? device_create+0x2b/0x30 Jan 21 10:33:54 home kernel: [] ? ir_register_class+0x66/0xd0 [ir_core] Jan 21 10:33:54 home kernel: [] ? ir_input_register+0x1b5/0x290 [ir_core] Jan 21 10:33:54 home kernel: [] ? budget_ci_attach+0x1b2/0xce0 [budget_ci] Jan 21 10:33:54 home kernel: [] ? saa7146_init_one+0x807/0x8d0 [saa7146] Jan 21 10:33:54 home kernel: [] ? iput+0x1d/0x50 Jan 21 10:33:54 home kernel: [] ? sysfs_addrm_finish+0x3a/0x1f0 Jan 21 10:33:54 home kernel: [] ? dma_generic_alloc_coherent+0x0/0x110 Jan 21 10:33:54 home kernel: [] ? dma_generic_alloc_coherent+0x0/0x110 Jan 21 10:33:54 home kernel: [] ? sysfs_do_create_link+0x92/0x110 Jan 21 10:33:54 home kernel: [] ? local_pci_probe+0xb/0x10 Jan 21 10:33:54 home kernel: [] ? pci_device_probe+0x61/0x80 Jan 21 10:33:54 home kernel: [] ? driver_probe_device+0x75/0x180 Jan 21 10:33:54 home kernel: [] ? pci_match_device+0x16/0xb0 Jan 21 10:33:54 home kernel: [] ? __driver_attach+0x79/0x80 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? bus_for_each_dev+0x49/0x70 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? driver_attach+0x16/0x20 Jan 21 10:33:54 home kernel: [] ? __driver_attach+0x0/0x80 Jan 21 10:33:54 home kernel: [] ? bus_add_driver+0xaf/0x220 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? driver_register+
[RESEND PATCH] ir-kbd-i2c: Allow to disable Hauppauge filter through module parameter
Some Hauppauge devices have id=0 so such devices won't work.
For such devices add a module parameter that allow to turn
off filtering.
Signed-off-by: Samuel Rakitničan
---
diff -r 82bbb3bd0f0a linux/drivers/media/video/ir-kbd-i2c.c
--- a/linux/drivers/media/video/ir-kbd-i2c.cMon Jan 11 11:47:33 2010 -0200
+++ b/linux/drivers/media/video/ir-kbd-i2c.cSat Jan 16 16:39:14 2010 +0100
@@ -61,6 +61,10 @@
module_param(hauppauge, int, 0644);/* Choose Hauppauge remote */
MODULE_PARM_DESC(hauppauge, "Specify Hauppauge remote: 0=black, 1=grey (defaults
to 0)");
+static int haup_filter = 1;
+module_param(haup_filter, int, 0644);
+MODULE_PARM_DESC(haup_filter, "Hauppauge filter for other remotes, default is 1
(On)");
+
#define DEVNAME "ir-kbd-i2c"
#define dprintk(level, fmt, arg...) if (debug >= level) \
@@ -96,24 +100,27 @@
if (!start)
/* no key pressed */
return 0;
- /*
-* Hauppauge remotes (black/silver) always use
-* specific device ids. If we do not filter the
-* device ids then messages destined for devices
-* such as TVs (id=0) will get through causing
-* mis-fired events.
-*
-* We also filter out invalid key presses which
-* produce annoying debug log entries.
-*/
- ircode= (start << 12) | (toggle << 11) | (dev << 6) | code;
- if ((ircode & 0x1fff)==0x1fff)
- /* invalid key press */
- return 0;
- if (dev!=0x1e && dev!=0x1f)
- /* not a hauppauge remote */
- return 0;
+ if (haup_filter != 0) {
+ /*
+* Hauppauge remotes (black/silver) always use
+* specific device ids. If we do not filter the
+* device ids then messages destined for devices
+* such as TVs (id=0) will get through causing
+* mis-fired events.
+*
+* We also filter out invalid key presses which
+* produce annoying debug log entries.
+*/
+ ircode = (start << 12) | (toggle << 11) | (dev << 6) | code;
+ if ((ircode & 0x1fff) == 0x1fff)
+ /* invalid key press */
+ return 0;
+
+ if (dev != 0x1e && dev != 0x1f)
+ /* not a hauppauge remote */
+ return 0;
+ }
if (!range)
code += 64;
--
Lorem ipsum
--
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
[RESEND PATCH] ir-kbd-i2c: Allow to disable Hauppauge filter through module parameter
Some Hauppauge devices have id=0 so such devices won't work. For such devices add a module parameter that allow to turn off filtering. Signed-off-by: Samuel Rakitničan -- Lorem ipsum wintv-radio-ir.diff Description: Binary data
[PATCH] ir-kbd-i2c: Allow to disable Hauppauge filter through module parameter
Some Hauppauge devices have id=0 so such devices won't work.
For such devices add a module parameter that allow to turns
off filtering.
Signed-off-by: Samuel Rakitničan
---
diff -r 82bbb3bd0f0a linux/drivers/media/video/ir-kbd-i2c.c
--- a/linux/drivers/media/video/ir-kbd-i2c.cMon Jan 11 11:47:33 2010
-0200
+++ b/linux/drivers/media/video/ir-kbd-i2c.cWed Jan 13 13:46:53 2010
+0100
@@ -61,6 +61,10 @@
module_param(hauppauge, int, 0644);/* Choose Hauppauge remote */
MODULE_PARM_DESC(hauppauge, "Specify Hauppauge remote: 0=black, 1=grey
(defaults to 0)");
+static int haup_filter = 1;
+module_param(haup_filter, int, 0644);
+MODULE_PARM_DESC(haup_filter, "Hauppauge filter for other remotes,
default is 1 (On)");
+
#define DEVNAME "ir-kbd-i2c"
#define dprintk(level, fmt, arg...)if (debug >= level) \
@@ -96,24 +100,27 @@
if (!start)
/* no key pressed */
return 0;
- /*
-* Hauppauge remotes (black/silver) always use
-* specific device ids. If we do not filter the
-* device ids then messages destined for devices
-* such as TVs (id=0) will get through causing
-* mis-fired events.
-*
-* We also filter out invalid key presses which
-* produce annoying debug log entries.
-*/
- ircode= (start << 12) | (toggle << 11) | (dev << 6) | code;
- if ((ircode & 0x1fff)==0x1fff)
- /* invalid key press */
- return 0;
- if (dev!=0x1e && dev!=0x1f)
- /* not a hauppauge remote */
- return 0;
+ if (haup_filter != 0) {
+ /*
+* Hauppauge remotes (black/silver) always use
+* specific device ids. If we do not filter the
+* device ids then messages destined for devices
+* such as TVs (id=0) will get through causing
+* mis-fired events.
+*
+* We also filter out invalid key presses which
+* produce annoying debug log entries.
+*/
+ ircode = (start << 12) | (toggle << 11) | (dev << 6) |
code;
+ if ((ircode & 0x1fff) == 0x1fff)
+ /* invalid key press */
+ return 0;
+
+ if (dev != 0x1e && dev != 0x1f)
+ /* not a hauppauge remote */
+ return 0;
+ }
if (!range)
code += 64;
--
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: WinTV Radio rev-c121 remote support
On Mon, 11 Jan 2010 20:24:51 +0100, Samuel Rakitnican
wrote:
On Fri, 08 Jan 2010 13:59:14 +0100, Samuel Rakitnican
wrote:
On Tue, 05 Jan 2010 21:11:59 +0100, Samuel Rakitničan
wrote:
Hi,
I have an old bt878 based analog card. It's 'Hauppauge WinTV Radio'
model 44914,
rev C121.
I'm trying to workout support for this shipped remote control. I have
[...]
Card: http://linuxtv.org/wiki/index.php/File:Wintv-radio-C121.jpg
Remote: http://linuxtv.org/wiki/index.php/File:Wintv-radio-remote.jpg
Did some investigation, maybe this can help to clarify some things.
Still didn't get any response in dmesg from remote.
[...]
i2c_scan:
bttv0: i2c scan: found device @ 0x30 [IR (hauppauge)]
bttv0: i2c scan: found device @ 0xa0 [eeprom]
bttv0: i2c scan: found device @ 0xc2 [tuner (analog)]
[...]
modprobe ir-kbd-i2c debug=1
ir-kbd-i2c: probe 0x1a @ bt878 #0 [sw]: no
ir-kbd-i2c: probe 0x18 @ bt878 #0 [sw]: yes
[...]
OK, patch http://patchwork.kernel.org/patch/70126/ did the trick for
kernel oops and segfault. However there is still something wrong in the
filtering code for hauppauge remotes that prevents my remote codes for
passing through:
drivers/media/video/ir-kbd-i2c.c
99/*
100 * Hauppauge remotes (black/silver) always use
101 * specific device ids. If we do not filter the
102 * device ids then messages destined for devices
103 * such as TVs (id=0) will get through causing
104 * mis-fired events.
105 *
106 * We also filter out invalid key presses which
107 * produce annoying debug log entries.
108 */
109 ircode= (start << 12) | (toggle << 11) | (dev << 6) | code;
110 if ((ircode & 0x1fff)==0x1fff)
111 /* invalid key press */
112 return 0;
113
114 if (dev!=0x1e && dev!=0x1f)
115 /* not a hauppauge remote */
116 return 0;
117
118 if (!range)
119 code += 64;
When I comment in this part: if (dev!=0x1e && dev!=0x1f), my remote
works with a hauppage=1 parameter, althought a few buttons are not
mapped correctly.
dmesg example with an empty table (buttons CH+ and CH-):
: unknown key: key=0x20 down=1
: unknown key for scancode 0x0020
: unknown key: key=0x20 down=0
: unknown key for scancode 0x0021
: unknown key: key=0x21 down=1
: unknown key for scancode 0x0021
: unknown key: key=0x21 down=0
Can someone please take a look at this and perhaps fix the code. Thanks
in advance.
Regards,
Samuel
It seems that my device id is the one that code author wants to filter
(0x0) if I understood correctly. I can add it to if (dev!=0x1e &&
dev!=0x1f) statement, but I then (I guess) would broke the filter
functionality:
ir-kbd-i2c: ir hauppauge (rc5): s1 r1 t1 dev=0 code=32
If this is the case the only thing I can think of is to add a module
parameter that turns off
such filtering.
What do you think?
Regards,
Samuel
diff -r 82bbb3bd0f0a linux/drivers/media/video/ir-kbd-i2c.c
--- a/linux/drivers/media/video/ir-kbd-i2c.cMon Jan 11 11:47:33 2010 -0200
+++ b/linux/drivers/media/video/ir-kbd-i2c.cTue Jan 12 23:36:44 2010 +0100
@@ -61,6 +61,10 @@
module_param(hauppauge, int, 0644);/* Choose Hauppauge remote */
MODULE_PARM_DESC(hauppauge, "Specify Hauppauge remote: 0=black, 1=grey
(defaults to 0)");
+static int haup_filter = 1;
+module_param(haup_filter, int, 0644);
+MODULE_PARM_DESC(haup_filter, "Turn off Hauppauge filter for other
remotes (defaults to 1)");
+
#define DEVNAME "ir-kbd-i2c"
#define dprintk(level, fmt, arg...)if (debug >= level) \
@@ -96,6 +100,8 @@
if (!start)
/* no key pressed */
return 0;
+
+ if (haup_filter != 0) {
/*
* Hauppauge remotes (black/silver) always use
* specific device ids. If we do not filter the
@@ -114,6 +120,7 @@
if (dev!=0x1e && dev!=0x1f)
/* not a hauppauge remote */
return 0;
+ }
if (!range)
code += 64;
--
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: WinTV Radio rev-c121 remote support
On Fri, 08 Jan 2010 13:59:14 +0100, Samuel Rakitnican wrote: On Tue, 05 Jan 2010 21:11:59 +0100, Samuel Rakitničan wrote: Hi, I have an old bt878 based analog card. It's 'Hauppauge WinTV Radio' model 44914, rev C121. I'm trying to workout support for this shipped remote control. I have [...] Card: http://linuxtv.org/wiki/index.php/File:Wintv-radio-C121.jpg Remote: http://linuxtv.org/wiki/index.php/File:Wintv-radio-remote.jpg Did some investigation, maybe this can help to clarify some things. Still didn't get any response in dmesg from remote. [...] i2c_scan: bttv0: i2c scan: found device @ 0x30 [IR (hauppauge)] bttv0: i2c scan: found device @ 0xa0 [eeprom] bttv0: i2c scan: found device @ 0xc2 [tuner (analog)] [...] modprobe ir-kbd-i2c debug=1 ir-kbd-i2c: probe 0x1a @ bt878 #0 [sw]: no ir-kbd-i2c: probe 0x18 @ bt878 #0 [sw]: yes [...] OK, patch http://patchwork.kernel.org/patch/70126/ did the trick for kernel oops and segfault. However there is still something wrong in the filtering code for hauppauge remotes that prevents my remote codes for passing through: drivers/media/video/ir-kbd-i2c.c 99 /* 100 * Hauppauge remotes (black/silver) always use 101 * specific device ids. If we do not filter the 102 * device ids then messages destined for devices 103 * such as TVs (id=0) will get through causing 104 * mis-fired events. 105 * 106 * We also filter out invalid key presses which 107 * produce annoying debug log entries. 108 */ 109 ircode= (start << 12) | (toggle << 11) | (dev << 6) | code; 110 if ((ircode & 0x1fff)==0x1fff) 111 /* invalid key press */ 112 return 0; 113 114 if (dev!=0x1e && dev!=0x1f) 115 /* not a hauppauge remote */ 116 return 0; 117 118 if (!range) 119 code += 64; When I comment in this part: if (dev!=0x1e && dev!=0x1f), my remote works with a hauppage=1 parameter, althought a few buttons are not mapped correctly. dmesg example with an empty table (buttons CH+ and CH-): : unknown key: key=0x20 down=1 : unknown key for scancode 0x0020 : unknown key: key=0x20 down=0 : unknown key for scancode 0x0021 : unknown key: key=0x21 down=1 : unknown key for scancode 0x0021 : unknown key: key=0x21 down=0 Can someone please take a look at this and perhaps fix the code. Thanks in advance. Regards, Samuel -- 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: WinTV Radio rev-c121 remote support
On Tue, 05 Jan 2010 21:11:59 +0100, Samuel Rakitničan
wrote:
Hi,
I have an old bt878 based analog card. It's 'Hauppauge WinTV Radio'
model 44914,
rev C121.
I'm trying to workout support for this shipped remote control. I have
tried to add
following lines to bttv-cards.c and bttv-input.c, but that gived
really bad results
(dmesg output is in attachment).
diff -r b6b82258cf5e linux/drivers/media/video/bt8xx/bttv-cards.c
--- a/linux/drivers/media/video/bt8xx/bttv-cards.c Thu Dec 31
19:14:54 2009
-0200
+++ b/linux/drivers/media/video/bt8xx/bttv-cards.c Tue Jan 05
13:25:09 2010
+0100
@@ -491,6 +491,7 @@
.pll= PLL_28,
.tuner_type = UNSET,
.tuner_addr = ADDR_UNSET,
+ .has_remote = 1,
},
[BTTV_BOARD_MIROPRO] = {
.name = "MIRO PCTV pro",
diff -r b6b82258cf5e linux/drivers/media/video/bt8xx/bttv-input.c
--- a/linux/drivers/media/video/bt8xx/bttv-input.c Thu Dec 31
19:14:54 2009
-0200
+++ b/linux/drivers/media/video/bt8xx/bttv-input.c Tue Jan 05
13:25:09 2010
+0100
@@ -341,6 +341,12 @@
ir->last_gpio=
ir_extract_bits(bttv_gpio_read(&btv->c),
ir->mask_keycode);
break;
+ case BTTV_BOARD_HAUPPAUGE878:
+ ir_codes = &ir_codes_pctv_sedna_table;
+ ir->mask_keycode = 0;
+ ir->mask_keyup = 0;
+ //ir->polling = 50;
+ break;
}
if (NULL == ir_codes) {
dprintk(KERN_INFO "Ooops: IR config error [card=%d]\n",
btv->c.type);
r...@crni:~/v4l-dvb# modprobe bttv
Segmentation fault
r...@crni:~/v4l-dvb#
Message from sysl...@crni at Tue Jan 5 13:03:08 2010 ...
crni kernel: Oops: [#1] SMP
[...]
So I guess that's not going to work. I have read in
wiki that Hauppauge cards needs ir-kbd-i2c, so I tried with that too, but
then similar error like previous happens when I try 'modprobe ir-kbd-i2c
debug=1
hauppauge=1' as well as just 'modprobe ir-kbd-i2c'.
Can I have a little pointer what to do?
Regards,
Samuel
--
Card: http://linuxtv.org/wiki/index.php/File:Wintv-radio-C121.jpg
Remote: http://linuxtv.org/wiki/index.php/File:Wintv-radio-remote.jpg
Did some investigation, maybe this can help to clarify some things. Still
didn't get any response in dmesg from remote.
Chips:
U1 - ST EEPROM - 24C02 4 ST K143L
U2 - Fairchild Dual 4-Channel Analog Multiplexer/Demultiplexer - CD4052BCM
U5 - Microchip EPROM - PIC16C54C 20/S3 0117H08 - IR Remote Control?
U6 - PTC Headphone Driver IC - PT2308-S
In metal can: EPCOS G1984D - demodulator
i2c_scan:
bttv0: i2c scan: found device @ 0x30 [IR (hauppauge)]
bttv0: i2c scan: found device @ 0xa0 [eeprom]
bttv0: i2c scan: found device @ 0xc2 [tuner (analog)]
eeprom dump:
tveeprom 1-0050: full 256-byte eeprom dump:
tveeprom 1-0050: 00: 84 12 00 00 05 50 0e 7f 04 15 01 72 af 91 14 8d
tveeprom 1-0050: 10: 00 00 00 00 05 84 0a 00 01 01 20 77 00 40 62 6c
tveeprom 1-0050: 20: 3c 00 74 02 01 00 02 79 b3 00 00 00 00 00 00 00
tveeprom 1-0050: 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: 70: 00 00 00 00 00 00 00 00 00 00 00 00 13 eb 00 70
tveeprom 1-0050: 80: 84 12 00 00 05 50 0e 7f 04 15 01 72 af 91 14 8d
tveeprom 1-0050: 90: 00 00 00 00 05 84 0a 00 01 01 20 77 00 40 62 6c
tveeprom 1-0050: a0: 3c 00 74 02 01 00 02 79 b3 00 00 00 00 00 00 00
tveeprom 1-0050: b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tveeprom 1-0050: f0: 00 00 00 00 00 00 00 00 00 00 00 00 13 eb 00 70
tveeprom 1-0050: Tag [00] + 17 bytes: 05 50 0e 7f 04 15 01 72 af 91 14 8d
00 00 00 00 05
tveeprom 1-0050: Tag [01] + 9 bytes: 01 20 77 00 40 62 6c 3c 00
tveeprom 1-0050: Tag [02] + 3 bytes: 01 00 02
modprobe ir-kbd-i2c debug=1
ir-kbd-i2c: probe 0x1a @ bt878 #0 [sw]: no
ir-kbd-i2c: probe 0x18 @ bt878 #0 [sw]: yes
linux/drivers/media/video/ir-kbd-i2c.c
417 case 0x18:
418 case 0x1a:
419 name= "Hauppauge";
420 //ir->get_key = get_key_haup;
421 ir_type = IR_TYPE_RC5;
422 if (hauppauge == 1) {
423 ir_codes= &ir_codes_hauppauge_new_table;
424 } else {
425 ir_codes= &ir_codes_rc5_tv_table;
426 }
427 break;
If I comment above line segfault does not occur. Tried the remote under
windows, and is working properly.
--
To unsubscribe from this list: send the line "unsubscr
Re: DTV2000 H Plus issues
On Sun, 03 Jan 2010 09:21:21 +0100, Raena Lea-Shannon wrote: istva...@mailbox.hu wrote: On 01/02/2010 05:10 PM, Raena Lea-Shannon wrote: I have 2 TV Cards. The DTV2000 H Plus and a Technisat. The Technisat works very well. I am trying to get the DVT working for other video input devices such as VCR to make copies of old Videos and an inteface for my N95 video out. I do not seem to be able to get it to find a tuner. Seems to be problem finding the card. Any suggestions wold be greatly appreciated. This card uses an Xceive XC4000 tuner, which is not supported yet. However, a driver for the tuner chip is being developed at kernellabs.com, so the card may become supported in the future. -- [snip] That seems odd. This patch on the LinuxTv site http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026379.html seems to be using the cx88 drivers? [...] Hi, I'm not a developer, but I think that your device uses both of these chips. cx88 is the bridge chip, while the Xceive is the tuner chip. So, both of them needs to be supported in order for a device to work properly. Please see the following link for reference: http://www.kernellabs.com/blog/?p=1045 Regards -- 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: Success for Compro E650F analog television and alsa sound.
On Mon, 07 Dec 2009 03:00:03 +0100, Igor M. Liplianin wrote: I'm able to watch now analog television with Compro E650F. That's great news for somebody :) Is remote working for this card? My card (T750F) and this card share the same remote, so I thought maybe keymap may be shared too. I started working on it several months ago but I didn't finished the keys associations due to that my card is not supported at all. http://www.spinics.net/lists/linux-media/msg07705.html Regards, Samuel -- 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: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
On Tue, 08 Sep 2009 18:18:05 +0200, Morvan Le Meut wrote: [...] Since it doesn't work with thoses keycodes, i'm trying it with "ir_codes_adstech_dvb_t_pci". I'm sure it won't work ( it would be toot easy otherwise ) but since the remote looks the same ... If by chance it work, i'll try to better document what i did for someone to write a patch. ( Or at least, to serve as a reminder the next time i'll encounter the problem ) Hi, If gpio's are correct, than all you need to do is write a new keymap. These is how I did it: If codes from original keymap are wrong erase the keycodes in ir-keymaps.c, but leave the header, pointer or whatever is called. In your case like that: /* Sylvain Vignaud Compile/install/load the drivers. You should get something like these in dmesg: dmesg example for a single button pressed (my card): saa7134 IR (Compro Videomate DV: unknown key: key=0x29 raw=0x29 down=1 saa7134 IR (Compro Videomate DV: unknown key: key=0x29 raw=0x29 down=0 The keycode (0x29) must be unique for every button pressed, and this is what you write in ir-keymaps.c e.g. [0x29] = KEY_POWER, /* power */ There has been standardization of keys recently, so this is how things must be mapped now: (http://linuxtv.org/wiki/index.php/Remote_Controllers) Read also: (http://linuxtv.org/wiki/index.php/Remote_controllers-V4L) -- 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: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
On Tue, 08 Sep 2009 10:25:44 +0200, Morvan Le Meut
wrote:
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version ) but i
tried it and i see a small problem :
The remote isn't supported. ( If it is, i wonder why my computer don't
see it )
I found an old patch to add remote support to it here :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of altering
a source file, could someone adapt that old patch to correct this ? (
should be quick, i guess )
Thanks.
-- 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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before "dev->has_remote = SAA7134_REMOTE_GPIO;" )
is that correct ?
but from the diff file i should add what seems to be the remote keycode
in saa7134-input.c
"+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are currently
disabled
+[ 127] = KEY_FINANCE, // "release all keys" code - prevent
repeating enlessly a key
+ +[ 27 ] = KEY_POWER,"
( and so on )
Since i didn't see other keycodes for the other cards, i guess this is
wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
Hi Morvan,
I'm not a developer, however I've done someting similar in the past...
This "keycodes" looks pretty strange to me, but then again I'm not a
developer.
Just add it by hand and compile it, and install it.
After successful load of all new modules, you should get some response in
terminal, or in dmesg output like "Unknown key..." if keymap table is
wrong by pressing buttons on remote. If this gpio's are correct:
+ mask_keycode = 0xff;
+ mask_keyup = 0xff;
+ mask_keydown = 0xff;
+ polling = 50; // ms
--
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: Report: Compro Videomate Vista T750F
On Sun, 12 Jul 2009 23:33:06 +0200, hermann pitton wrote: Hi Samuel, Am Sonntag, den 12.07.2009, 13:30 +0200 schrieb Samuel Rakitnican: As the card=139 (Compro Videomate T750) DVB: Not working, not implemented Analog: Not working Audio In: ? (my T750F has additional connector ?) if amux LINE2 doesn't work it is usually LINE1. If both don't work, there is a external gpio controlled switch/mux chip. Default is loop through for external audio in. Means, if the saa7134 driver is unloaded, should be passed through to audio out. If not, there is such a mux chip involved. [snip] Well, I haven't managed to get sound from Audio In connector, it's possible however that I'm doing something wrong. I tried selecting in tvtime both Composite and S-Video, and I've tried using SoX: console$> ls /dev/dsp* dsp dsp1 console$> sox -c 2 -s -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -r 32000 /dev/dsp & for both .amux = LINE1 and LINE2 in saa7134-cards.c source file. RegSpy log: I have used RegSpy that comes with DScaler version 4.1.15. I'm hoping that they are of some use for both Analog television and Audio In. I have found out values crucial to changing inputs for both audio and video. Note that SAA7134_GPIO_GPSTATUS keeps changing all the time between 84ff00 and 94bf00 nevertheless of the device status. I have used VirtualDub (v1.7.7) as capturing application because it gives more control on input selecting (I can change audio input, not depending on video). From that I manage to distinguish values changing between video and audio. The crucial value for video seems to be SAA7134_ANALOG_IN_CTRL1 while for audio seems to be values SAA7133_AUDIO_CLOCK_NOMINAL and SAA7133_PLL_CONTROL. Changes: State 0 -> State 1: *(Switch: Analog TV -> Composite) SAA7134_GPIO_GPSTATUS: 0094ff00 -> 0494ff00 (-0-- ) SAA7134_ANALOG_IN_CTRL1: 83 -> 81(--1-) SAA7133_AUDIO_CLOCK_NOMINAL: 03187de7 -> 43187de7 (-0-- ) SAA7133_PLL_CONTROL: 03 -> 43(-0--) Changes: State 1 -> State 2: *(Switch: Composite -> S-Video) SAA7134_GPIO_GPSTATUS: 0494ff00 -> 0284ff00 (-10- ---1 ) SAA7134_ANALOG_IN_CTRL1: 81 -> 88(0--1) Changes: State 2 -> State 3: ***(Switch: Audio Source -> Audio Tuner (Still in S-Video mode)) SAA7134_GPIO_GPSTATUS: 0284ff00 -> 0294ff00 ( ---0 ) SAA7133_AUDIO_CLOCK_NOMINAL: 43187de7 -> 03187de7 (-1-- ) (same as 0) SAA7133_PLL_CONTROL: 43 -> 03 (-1--) (same as 0) Changes: State 3 -> State 4: **(Switch: Audio Source -> Audio Line (Still in S-Video mode)) SAA7134_GPIO_GPSTATUS: 0294ff00 -> 0484ff00 (-01- ---1 ) SAA7133_AUDIO_CLOCK_NOMINAL: 03187de7 -> 43187de7 (-0-- ) (same as 1, 2) SAA7133_PLL_CONTROL: 03 -> 43 (-0--) (same as 1, 2) (full log: http://pastebin.com/f5f8e6184) -- 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: Report: Compro Videomate Vista T750F
Hi Hermann, On Sun, 12 Jul 2009 23:33:06 +0200, hermann pitton wrote: [snip] Hm, if I get it right, without using windows previously the XCeive at 0x61 is not found and then it is tried in vain to use the qt1010 at 0x62. Also, after using windows gpio20 seems to be high. Maybe that is the gpio to get the tuner out of reset. Please try the attached patch as a shot into the dark. [snip] No, I pay attention when I test for channel that XCeive gets recognized as 0x61. When I do cold boot, or windows reboot its always gets recognized at 0x61. Sometimes (I don't know exactly what triggers that) the 0x61 gets omitted, and the result is that XCeive get recognized as 0x62. The result is that channel is not showing any more, apparently. I think that xc2028-27.fw file load failures triggers that behavior, because when I reboot linux with loading firmware failures, that behavior is showing (from what I have noticed). Sorry for the gpio alert, but I did some logging, and the gpio value varies, and depends on computer state. But it seems that is same in both cases after all. (details http://pastebin.com/f4c511dfc) I tried your patch, too, and it's not working. Thank you for trying. -- 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
Report: Compro Videomate Vista T750F
As the card=139 (Compro Videomate T750) DVB: Not working, not implemented Analog: Not working Audio In: ? (my T750F has additional connector ?) Composite In: Working S-Video In: Working IR: Works with T300 codes and different keymap (needs to be implemented) (http://www.spinics.net/lists/linux-media/msg07705.html) Analog TV and XCeive: Although John Newbigins reported that Analog is working in Apr 25 2007 with a patch. I did not try to implement this patch (by hand) because tree changed big from that date, so it seems that this can not be done. At least I can't. (http://www.linuxtv.org/pipermail/linux-dvb/2007-April/017449.html) With stock Slackware 12.2 it's showing a single channel (although tuner does't work) that previously was selected in a windows application and restarted. Thought I had to select in tvtime: Input configuration > Television standard > PAL (Default was NTSC). And then Restart with new settings to show up that channel. Otherwise it would still remain blue. XCeive is recognized at 0xc2 With new v4l-dvb tree channel is not showing up any more no mather what I do. New v4l also recognizes XCeive at 0xc2: tuner' 0-0061: chip found @ 0xc2 (saa7133[0]) xc2028 0-0061: creating new instance xc2028 0-0061: type set to XCeive xc2028/xc3028 tuner tvtime startup and shuting off: (Complete dump: http://pastebin.com/f376a8272) xc2028 1-0061: Loading firmware for type=BASE F8MHZ MTS (7), id . xc2028 1-0061: i2c output error: rc = -5 (should be 64) xc2028 1-0061: -5 returned from send xc2028 1-0061: Error -22 while loading base firmware (and then shutting off tvtime gives a line) xc2028 1-0061: Error on line 1141: -5 eeproms T750 and T750F (maybe needed for automatic IR keymap selection) T750 saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 03 01 08 ff 00 89 ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff d7 00 c4 86 1e 05 ff 02 c2 ff 01 ff ff ff ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7133[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff T750F saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff d7 00 c4 86 1e 05 ff 02 c2 ff 01 c6 ff 05 ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- 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
Help on mapping Media Center remote
Hi, With the huge help of Hermann, I managed to implement this remote with it's new card Compro VideoMate Vista T750F card=169 (just a copy of T750 with a diff keymap). I successfully compiled v4l and managed to get this remote to work. I need some help on mapping specific MCE buttons, since I don't know how remotes on linux function, or how MCE function. I just ran into this adventure, and stuck here. Please, reply with missing values, correcting the wrong ones (if there are any) so that I can finish keymap for this remote. Or with a hint what to enter here. Thanks in advance --- Picture of the remote: http://i28.tinypic.com/1z5j500.jpg /* Number in commment coresponds to remote button found in mce.gif and T750F-ENG.pdf manual. */ [ 0x1d ] = KEY_0, [ 0x1e ] = KEY_1, [ 0x1f ] = KEY_2, [ 0x20 ] = KEY_3, [ 0x21 ] = KEY_4, [ 0x22 ] = KEY_5, [ 0x23 ] = KEY_6, [ 0x24 ] = KEY_7, [ 0x25 ] = KEY_8, [ 0x26 ] = KEY_9, [ 0x01 ] = KEY_POWER, // 10 // [ 0x31 ] = /* 11 "Videos (MCE)" */ // [ 0x33 ] = /* 12 "Radio (MCE)" */ // [ 0x2f ] = /* 13 "Music (MCE)" */ // [ 0x30 ] = /* 14 "Pictures (MCE)"*/ // [ 0x2d ] = /* 15 "Recorded TV (MCE)" */ // [ 0x17 ] = /* 16 "MCE Guide" */ // [ 0x2c ] = /* 17 "Live TV (MCE)" */ // [ 0x2b ] = /* 18 "DVD Menu (MCE)"*/ // [ 0x32 ] = /* 19 "DVD Sub (MCE)" */ [ 0x11 ] = KEY_UP, // 20 [ 0x13 ] = KEY_LEFT,// 21 [ 0x12 ] = KEY_DOWN,// 22 [ 0x14 ] = KEY_RIGHT, // 23 [ 0x15 ] = KEY_OK, // 24 [ 0x16 ] = KEY_BACK,// 25 // [ 0x02 ] = /* 26 "Media Center" */ // [ 0x04 ] = // 27 >> TV app in win goes fullscreen/restore, or in manual says "More" for MCE [ 0x05 ] = KEY_VOLUMEUP,// 28 [ 0x06 ] = KEY_VOLUMEDOWN, // 29 [ 0x03 ] = KEY_MUTE,// 30 [ 0x07 ] = KEY_CHANNELUP, // 31 [ 0x08 ] = KEY_CHANNELDOWN, // 32 [ 0x0c ] = KEY_RECORD, // 33 [ 0x0e ] = KEY_STOP,// 34 [ 0x0a ] = KEY_REWIND, // 35 [ 0x0b ] = KEY_PLAY,// 36 [ 0x09 ] = KEY_FASTFORWARD, // 37 [ 0x10 ] = KEY_PREVIOUSSONG,/* 38 "Skip rewind" */ [ 0x0d ] = KEY_PAUSE, // 39 [ 0x0f ] = KEY_NEXTSONG,/* 40 "Skip Forward" */ // [ 0x2a ] = /* 41 The "*" button */ // [ 0x29 ] = /* 42 The "#" button */ [ 0x27 ] = KEY_CLEAR, // 43 // [ 0x34 ] = // 44 >> This one turn on/off TV app in win [ 0x28 ] = KEY_ENTER, // 45 [ 0x19 ] = KEY_RED, // 46 [ 0x1a ] = KEY_GREEN, // 47 [ 0x1b ] = KEY_YELLOW, // 48 [ 0x1c ] = KEY_BLUE,// 49 [ 0x18 ] = KEY_TEXT,// 50 "Teletext on/off" -- 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
Compro T750 - analog doesn't work ?
I have Slackware 12.2 with it's stock kernel (2.6.27.7-smp). I haven't done any modifications to system. Installed version of tvtime is 1.0.2. It asked for xc3028-v27.fw firmware file I've got it from a following link: http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 In tvtime Composite input is working. When I switch to Television it's showing blue screen with 'No signal' sign. After I restart from Windows, last viewed channel from a Windows app appears in tvtime, but if I try to change or scan channels nothing happens (it's showing the same channel every time). If I cold start the computer tvtime it's showing previously mentioned 'No signal' screen. Today (01.07.2009) I have installed latest v4l drivers using Mercurial hg, but the results are the same. If it help's below is a link on a forum thread on some other guy trying to get it work in Ubuntu with some more logs: http://ubuntuforums.org/archive/index.php/t-1092160.html Logs: ::lspci -vvnnn:: 00:0b.0 Multimedia controller [0480]: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder [1131:7133] (rev d1) Subsystem: Compro Technology, Inc. VideoMate T750 [185b:c900] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32 (21000ns min, 8000ns max) Interrupt: pin A routed to IRQ 19 Region 0: Memory at dfffb800 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Kernel driver in use: saa7134 Kernel modules: saa7134 ::Kernel log in system start (pulled out only relevant to v4l):: saa7130/34: v4l2 driver version 0.2.15 loaded saa7134 :00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 saa7133[0]: found at :00:0b.0, rev: 209, irq: 19, latency: 32, mmio: 0xdfffb800 saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750 [card=139,autodetected] saa7133[0]: board init: gpio is 84bf00 saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff d7 00 c4 86 1e 05 ff 02 c2 ff 01 c6 ff 05 ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7133[0]: i2c eeprom 60: 35 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff tuner 1-0062: chip found @ 0xc4 (saa7133[0]) xc2028 1-0062: creating new instance xc2028 1-0062: type set to XCeive xc2028/xc3028 tuner firmware: requesting xc3028-v27.fw xc2028 1-0062: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 xc2028 1-0062: Loading firmware for type=BASE F8MHZ MTS (7), id . xc2028 1-0062: i2c output error: rc = -5 (should be 64) xc2028 1-0062: -5 returned from send xc2028 1-0062: Error -22 while loading base firmware xc2028 1-0062: Loading firmware for type=BASE F8MHZ MTS (7), id . xc2028 1-0062: i2c output error: rc = -5 (should be 64) xc2028 1-0062: -5 returned from send xc2028 1-0062: Error -22 while loading base firmware xc2028 1-0062: Loading firmware for type=BASE F8MHZ MTS (7), id . xc2028 1-0062: i2c output error: rc = -5 (should be 64) xc2028 1-0062: -5 returned from send xc2028 1-0062: Error -22 while loading base firmware xc2028 1-0062: Loading firmware for type=BASE F8MHZ MTS (7), id . xc2028 1-0062: i2c output error: rc = -5 (should be 64) xc2028 1-0062: -5 returned from send xc2028 1-0062: Error -22 while loading base firmware xc2028 1-0062: Error on line 1130: -5 saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 saa7133[0]: registered device radio0 saa7134 ALSA driver for DMA sound loaded saa7133[0]/alsa: saa7133[0] at 0xdfffb800 irq 19 registered as card -1 xc2028 1-0062: Loading firmware for type=BASE FM (401), id 000
