[PATCH 2/5] [media] rc/keymaps: add keytable for Terratec Cinergy C PCI
This RC map was taken from Christoph Pinkl's patch
(http://patchwork.linuxtv.org/patch/7217/). It is used solely by the respective
mantis based card because the encoding is not known.
Signed-off-by: Jan Klötzke
---
drivers/media/rc/keymaps/Makefile | 1 +
.../media/rc/keymaps/rc-terratec-cinergy-c-pci.c | 88 ++
include/media/rc-map.h | 1 +
3 files changed, 90 insertions(+)
create mode 100644 drivers/media/rc/keymaps/rc-terratec-cinergy-c-pci.c
diff --git a/drivers/media/rc/keymaps/Makefile
b/drivers/media/rc/keymaps/Makefile
index 07c4b98..775f663 100644
--- a/drivers/media/rc/keymaps/Makefile
+++ b/drivers/media/rc/keymaps/Makefile
@@ -86,6 +86,7 @@ obj-$(CONFIG_RC_MAP) += rc-adstech-dvb-t-pci.o \
rc-tbs-nec.o \
rc-technisat-ts35.o \
rc-technisat-usb2.o \
+ rc-terratec-cinergy-c-pci.o \
rc-terratec-cinergy-xs.o \
rc-terratec-slim.o \
rc-terratec-slim-2.o \
diff --git a/drivers/media/rc/keymaps/rc-terratec-cinergy-c-pci.c
b/drivers/media/rc/keymaps/rc-terratec-cinergy-c-pci.c
new file mode 100644
index 000..7958f45
--- /dev/null
+++ b/drivers/media/rc/keymaps/rc-terratec-cinergy-c-pci.c
@@ -0,0 +1,88 @@
+/* keytable for Terratec Cinergy C PCI Remote Controller
+ *
+ * Copyright (c) 2010 by Igor M. Liplianin
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ */
+
+#include
+#include
+
+static struct rc_map_table terratec_cinergy_c_pci[] = {
+ { 0x3e, KEY_POWER},
+ { 0x3d, KEY_1},
+ { 0x3c, KEY_2},
+ { 0x3b, KEY_3},
+ { 0x3a, KEY_4},
+ { 0x39, KEY_5},
+ { 0x38, KEY_6},
+ { 0x37, KEY_7},
+ { 0x36, KEY_8},
+ { 0x35, KEY_9},
+ { 0x34, KEY_VIDEO_NEXT}, /* AV */
+ { 0x33, KEY_0},
+ { 0x32, KEY_REFRESH},
+ { 0x30, KEY_EPG},
+ { 0x2f, KEY_UP},
+ { 0x2e, KEY_LEFT},
+ { 0x2d, KEY_OK},
+ { 0x2c, KEY_RIGHT},
+ { 0x2b, KEY_DOWN},
+ { 0x29, KEY_INFO},
+ { 0x28, KEY_RED},
+ { 0x27, KEY_GREEN},
+ { 0x26, KEY_YELLOW},
+ { 0x25, KEY_BLUE},
+ { 0x24, KEY_CHANNELUP},
+ { 0x23, KEY_VOLUMEUP},
+ { 0x22, KEY_MUTE},
+ { 0x21, KEY_VOLUMEDOWN},
+ { 0x20, KEY_CHANNELDOWN},
+ { 0x1f, KEY_PAUSE},
+ { 0x1e, KEY_HOME},
+ { 0x1d, KEY_MENU}, /* DVD Menu */
+ { 0x1c, KEY_SUBTITLE},
+ { 0x1b, KEY_TEXT}, /* Teletext */
+ { 0x1a, KEY_DELETE},
+ { 0x19, KEY_TV},
+ { 0x18, KEY_DVD},
+ { 0x17, KEY_STOP},
+ { 0x16, KEY_VIDEO},
+ { 0x15, KEY_AUDIO}, /* Music */
+ { 0x14, KEY_SCREEN}, /* Pic */
+ { 0x13, KEY_PLAY},
+ { 0x12, KEY_BACK},
+ { 0x11, KEY_REWIND},
+ { 0x10, KEY_FASTFORWARD},
+ { 0x0b, KEY_PREVIOUS},
+ { 0x07, KEY_RECORD},
+ { 0x03, KEY_NEXT},
+
+};
+
+static struct rc_map_list terratec_cinergy_c_pci_map = {
+ .map = {
+ .scan= terratec_cinergy_c_pci,
+ .size= ARRAY_SIZE(terratec_cinergy_c_pci),
+ .rc_type = RC_TYPE_UNKNOWN, /* Legacy IR type */
+ .name= RC_MAP_TERRATEC_CINERGY_C_PCI,
+ }
+};
+
+static int __init init_rc_map_terratec_cinergy_c_pci(void)
+{
+ return rc_map_register(&terratec_cinergy_c_pci_map);
+}
+
+static void __exit exit_rc_map_terratec_cinergy_c_pci(void)
+{
+ rc_map_unregister(&terratec_cinergy_c_pci_map);
+}
+
+module_init(init_rc_map_terratec_cinergy_c_pci);
+module_exit(exit_rc_map_terratec_cinergy_c_pci);
+
+MODULE_LICENSE("GPL");
diff --git a/include/media/rc-map.h b/include/media/rc-map.h
index aa56264..9873a17 100644
--- a/include/media/rc-map.h
+++ b/include/media/rc-map.h
@@ -196,6 +196,7 @@ void rc_map_init(void);
#define RC_MAP_TBS_NEC "rc-tbs-nec"
#define RC_MAP_TECHNISAT_TS35"rc-technisat-ts35"
#define RC_MAP_TECHNISAT_USB2"rc-technisat-usb2"
+#define RC_MAP_TERRATEC_CINERGY_C_PCI"rc-terratec-cinergy-c-pci"
#define RC_MAP_TERRATEC_CINERGY_XS "rc-terratec-cinergy-xs"
#define RC_MAP_TERRATEC_SLIM "rc-terratec-slim"
#define RC_MAP_TERRATEC_SLIM_2 "rc-terratec-slim-2"
--
2.1.4
--
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
Terratec Cinergy C (HD ?) support
Hi everyone ! I just discovered that Terratec made an other revision of their Cinergy C PCI card (it is a DVB-C lci card). I tried to install it on a debian system with the kernel 3.2.0 and with back port 3.14 without success, I have no device in /dev/dvb. The wiki page ( http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C ) shows a card with a black PCB but mine has a white one. The weird thing is that the box says it supports HDTV so I guess I own a HD version even it is not mentioned on the product name. lspci -vnn shows that : 04:00.0 Multimedia controller [0480]: InfiniCon Systems Inc. Device [1820:4e35] (rev 01) Subsystem: ATELIER INFORMATIQUES et ELECTRONIQUE ETUDES S.A. Device [1539:1178] Flags: bus master, medium devsel, latency 32, IRQ 8 Memory at 9010 (32-bit, prefetchable) [disabled] [size=4K] I found no information on this hardware yet… I’m currently building latest sources but I don’t think it will help so much. Do you have any clue that could lead supporting this device on linux ? 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
Re: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Manu Abraham writes: > Terratec Cinregy C is VP-2033 and not VP-2040. Can you please enlighten me on how to tell this difference? I have two of these cards: bjorn@canardo:~$ lspci -vvnns 05:00 05:00.0 Multimedia controller [0480]: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] [1822:4e35] (rev 01) Subsystem: TERRATEC Electronic GmbH Device [153b:1178] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- GSI 16 (level, low) -> IRQ 16 [ 35.847869] DVB: registering new adapter (Mantis DVB adapter) [ 37.358998] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... [ 37.359079] Mantis :05:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 37.607414] DVB: registering new adapter (Mantis DVB adapter) [ 38.486159] DVB: registering adapter 1 frontend 0 (Philips TDA10023 DVB-C)... But as both the VP-2033 and VP-2040 code support both TDA10021 and TDA10023 there is obviously some other difference between these. Bridge version maybe? Or something else? Bjørn -- 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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Mauro Carvalho Chehab writes:
> Hmm... there's something wrong: this would be the revert patch, as produced
> by git revert:
>
> diff --git a/drivers/media/pci/mantis/mantis_cards.c
> b/drivers/media/pci/mantis/mantis_cards.c
> index 0207d1f..095cf3a 100644
> --- a/drivers/media/pci/mantis/mantis_cards.c
> +++ b/drivers/media/pci/mantis/mantis_cards.c
> @@ -275,7 +275,7 @@ static struct pci_device_id mantis_pci_table[] = {
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C, &vp2033_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C, &vp2040_config),
> MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
> - MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
> + MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T, &vp3030_config),
> { }
> };
> diff --git a/drivers/media/pci/mantis/mantis_core.c
> b/drivers/media/pci/mantis/mantis_core.c
> index 684d906..22524a8 100644
> --- a/drivers/media/pci/mantis/mantis_core.c
> +++ b/drivers/media/pci/mantis/mantis_core.c
> @@ -121,7 +121,7 @@ static void mantis_load_config(struct mantis_pci *mantis)
> mantis->hwconfig = &vp2033_mantis_config;
> break;
> case MANTIS_VP_2040_DVB_C: /* VP-2040 */
> - case CINERGY_C: /* VP-2040 clone */
> + case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
> case TECHNISAT_CABLESTAR_HD2:
> mantis->hwconfig = &vp2040_mantis_config;
> break;
>
> There's something wrong there: the comments at "mantis_core", before this
> patch, is saying that TERRATEC_CINERGY_C_PCI is a VP-2040 clone.
>
> That doesn't look right: this card is either a VP-2033 clone (as stated on
> mantis_cards), or a VP-2040 (as stated on mantis_core).
Just delete the whole mantis_core.c file. It has never been built in
the in-kernel driver. See, no reference to it at all:
bjorn@nemi:/usr/local/src/git/linux$ cat drivers/media/dvb/mantis/Makefile
mantis_core-objs := mantis_ioc.o\
mantis_uart.o \
mantis_dma.o\
mantis_pci.o\
mantis_i2c.o\
mantis_dvb.o\
mantis_evm.o\
mantis_hif.o\
mantis_ca.o \
mantis_pcmcia.o \
mantis_input.o
mantis-objs := mantis_cards.o \
mantis_vp1033.o \
mantis_vp1034.o \
mantis_vp1041.o \
mantis_vp2033.o \
mantis_vp2040.o \
mantis_vp3030.o
hopper-objs := hopper_cards.o \
hopper_vp3028.o
obj-$(CONFIG_MANTIS_CORE) += mantis_core.o
obj-$(CONFIG_DVB_MANTIS)+= mantis.o
obj-$(CONFIG_DVB_HOPPER)+= hopper.o
ccflags-y += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
Bjørn
--
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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Em 14-08-2012 10:23, Mauro Carvalho Chehab escreveu:
> Em 14-08-2012 04:45, Manu Abraham escreveu:
>> On Tue, Aug 14, 2012 at 12:55 AM, Mauro Carvalho Chehab
>> wrote:
>>> Em 10-08-2012 20:55, Manu Abraham escreveu:
>>>> Mauro,
>>>>
>>>> Please revert this patch. Patch is incorrect. There is the VP-20300,
>>>> VP-20330, VP-2040, with differences in tuner types TDA10021, TDA10023,
>>>> MK-I, MK-II and MK-III. I have detailed this issue in an earlier mail.
>>>> Terratec Cinregy C is VP-2033 and not VP-2040.
>>>
>>> Well, as I don't have this board, you think that it is a VP-2033 while
>>> Igor thinks it is a VP-2040, I can't tell who is right on that.
>>
>> You don't need all the cards to apply changes, that's how the Linux
>> patchland works.
>>
>> I have "all" Mantis based devices here. So I can say with clarity that
>> Terratec Cinergy C is VP-2033. I authored the whole driver for the
>> chipset manufacturer and the card manufacturer and still in touch with
>> all of them and pretty sure what is what.
>>
>> Any idiot can send any patch, that's why you need to ask the persons
>> who added particular changes in that area.
>
> Yes, you authored the driver, but that doesn't necessarily means that
> you'll have all clones of VP-2033/VP-2040.
>
>> Do you want me to add
>> myself to MAINTAINERS to make it a bit more clearer, if that's what
>> you prefer ?
>
> If you're wiling to maintain it, not holding patches for more than the
> few days required for their review, then YES!!!
>
> Please add yourself to the MAINTAINERS for the drivers you're willing
> to maintain and submit me such patch for upstream merging.
>
>> Please revert this change.
>
> I'll do.
Hmm... there's something wrong: this would be the revert patch, as produced
by git revert:
diff --git a/drivers/media/pci/mantis/mantis_cards.c
b/drivers/media/pci/mantis/mantis_cards.c
index 0207d1f..095cf3a 100644
--- a/drivers/media/pci/mantis/mantis_cards.c
+++ b/drivers/media/pci/mantis/mantis_cards.c
@@ -275,7 +275,7 @@ static struct pci_device_id mantis_pci_table[] = {
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C, &vp2033_config),
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C, &vp2040_config),
MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
- MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
+ MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T, &vp3030_config),
{ }
};
diff --git a/drivers/media/pci/mantis/mantis_core.c
b/drivers/media/pci/mantis/mantis_core.c
index 684d906..22524a8 100644
--- a/drivers/media/pci/mantis/mantis_core.c
+++ b/drivers/media/pci/mantis/mantis_core.c
@@ -121,7 +121,7 @@ static void mantis_load_config(struct mantis_pci *mantis)
mantis->hwconfig = &vp2033_mantis_config;
break;
case MANTIS_VP_2040_DVB_C: /* VP-2040 */
- case CINERGY_C: /* VP-2040 clone */
+ case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
case TECHNISAT_CABLESTAR_HD2:
mantis->hwconfig = &vp2040_mantis_config;
break;
There's something wrong there: the comments at "mantis_core", before this
patch, is saying that TERRATEC_CINERGY_C_PCI is a VP-2040 clone.
That doesn't look right: this card is either a VP-2033 clone (as stated on
mantis_cards), or a VP-2040 (as stated on mantis_core).
So, please write me a patch syncing both places with the correct information.
Thanks!
Mauro
--
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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Em 14-08-2012 04:45, Manu Abraham escreveu: > On Tue, Aug 14, 2012 at 12:55 AM, Mauro Carvalho Chehab > wrote: >> Em 10-08-2012 20:55, Manu Abraham escreveu: >>> Mauro, >>> >>> Please revert this patch. Patch is incorrect. There is the VP-20300, >>> VP-20330, VP-2040, with differences in tuner types TDA10021, TDA10023, >>> MK-I, MK-II and MK-III. I have detailed this issue in an earlier mail. >>> Terratec Cinregy C is VP-2033 and not VP-2040. >> >> Well, as I don't have this board, you think that it is a VP-2033 while >> Igor thinks it is a VP-2040, I can't tell who is right on that. > > You don't need all the cards to apply changes, that's how the Linux > patchland works. > > I have "all" Mantis based devices here. So I can say with clarity that > Terratec Cinergy C is VP-2033. I authored the whole driver for the > chipset manufacturer and the card manufacturer and still in touch with > all of them and pretty sure what is what. > > Any idiot can send any patch, that's why you need to ask the persons > who added particular changes in that area. Yes, you authored the driver, but that doesn't necessarily means that you'll have all clones of VP-2033/VP-2040. > Do you want me to add > myself to MAINTAINERS to make it a bit more clearer, if that's what > you prefer ? If you're wiling to maintain it, not holding patches for more than the few days required for their review, then YES!!! Please add yourself to the MAINTAINERS for the drivers you're willing to maintain and submit me such patch for upstream merging. > Please revert this change. I'll do. Regards, Mauro -- 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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
On Tue, Aug 14, 2012 at 12:55 AM, Mauro Carvalho Chehab wrote: > Em 10-08-2012 20:55, Manu Abraham escreveu: >> Mauro, >> >> Please revert this patch. Patch is incorrect. There is the VP-20300, >> VP-20330, VP-2040, with differences in tuner types TDA10021, TDA10023, >> MK-I, MK-II and MK-III. I have detailed this issue in an earlier mail. >> Terratec Cinregy C is VP-2033 and not VP-2040. > > Well, as I don't have this board, you think that it is a VP-2033 while > Igor thinks it is a VP-2040, I can't tell who is right on that. You don't need all the cards to apply changes, that's how the Linux patchland works. I have "all" Mantis based devices here. So I can say with clarity that Terratec Cinergy C is VP-2033. I authored the whole driver for the chipset manufacturer and the card manufacturer and still in touch with all of them and pretty sure what is what. Any idiot can send any patch, that's why you need to ask the persons who added particular changes in that area. Do you want me to add myself to MAINTAINERS to make it a bit more clearer, if that's what you prefer ? Please revert this change. Manu -- 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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Em 10-08-2012 20:55, Manu Abraham escreveu:
> Mauro,
>
> Please revert this patch. Patch is incorrect. There is the VP-20300,
> VP-20330, VP-2040, with differences in tuner types TDA10021, TDA10023,
> MK-I, MK-II and MK-III. I have detailed this issue in an earlier mail.
> Terratec Cinregy C is VP-2033 and not VP-2040.
Well, as I don't have this board, you think that it is a VP-2033 while
Igor thinks it is a VP-2040, I can't tell who is right on that.
I need either you to change your mind or to get a third developer to
point who is right in order to address it.
In any case, no harm is done, as both have exactly the same code.
That's why the better is to just drop one of the drivers, while
both are identical.
Regards,
Mauro
>
> Thanks!
>
>
> On Sat, Aug 11, 2012 at 1:34 AM, Mauro Carvalho Chehab
> wrote:
>> This is an automatic generated email to let you know that the following
>> patch were queued at the
>> http://git.linuxtv.org/media_tree.git tree:
>>
>> Subject: [media] mantis: Terratec Cinergy C PCI HD (CI)
>> Author: Igor M. Liplianin
>> Date:Wed May 9 07:23:14 2012 -0300
>>
>> This patch seems for rectifying a typo. But actually the difference between
>> mantis_vp2040.c and mantis_vp2033.c code is a card name only.
>>
>> Signed-off-by: Igor M. Liplianin
>> Signed-off-by: Mauro Carvalho Chehab
>>
>> drivers/media/dvb/mantis/mantis_cards.c |2 +-
>> drivers/media/dvb/mantis/mantis_core.c |2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> ---
>>
>> http://git.linuxtv.org/media_tree.git?a=commitdiff;h=9fa4d6a102ebb06663a03554b57fb93ad618b72e
>>
>> diff --git a/drivers/media/dvb/mantis/mantis_cards.c
>> b/drivers/media/dvb/mantis/mantis_cards.c
>> index 095cf3a..0207d1f 100644
>> --- a/drivers/media/dvb/mantis/mantis_cards.c
>> +++ b/drivers/media/dvb/mantis/mantis_cards.c
>> @@ -275,7 +275,7 @@ static struct pci_device_id mantis_pci_table[] = {
>> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C,
>> &vp2033_config),
>> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C,
>> &vp2040_config),
>> MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
>> - MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
>> + MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
>> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T,
>> &vp3030_config),
>> { }
>> };
>> diff --git a/drivers/media/dvb/mantis/mantis_core.c
>> b/drivers/media/dvb/mantis/mantis_core.c
>> index 22524a8..684d906 100644
>> --- a/drivers/media/dvb/mantis/mantis_core.c
>> +++ b/drivers/media/dvb/mantis/mantis_core.c
>> @@ -121,7 +121,7 @@ static void mantis_load_config(struct mantis_pci *mantis)
>> mantis->hwconfig = &vp2033_mantis_config;
>> break;
>> case MANTIS_VP_2040_DVB_C: /* VP-2040 */
>> - case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
>> + case CINERGY_C: /* VP-2040 clone */
>> case TECHNISAT_CABLESTAR_HD2:
>> mantis->hwconfig = &vp2040_mantis_config;
>> break;
>>
>> ___
>> linuxtv-commits mailing list
>> linuxtv-comm...@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linuxtv-commits
> --
> 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
>
--
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: [git:v4l-dvb/for_v3.7] [media] mantis: Terratec Cinergy C PCI HD (CI)
Mauro,
Please revert this patch. Patch is incorrect. There is the VP-20300,
VP-20330, VP-2040, with differences in tuner types TDA10021, TDA10023,
MK-I, MK-II and MK-III. I have detailed this issue in an earlier mail.
Terratec Cinregy C is VP-2033 and not VP-2040.
Thanks!
On Sat, Aug 11, 2012 at 1:34 AM, Mauro Carvalho Chehab
wrote:
> This is an automatic generated email to let you know that the following patch
> were queued at the
> http://git.linuxtv.org/media_tree.git tree:
>
> Subject: [media] mantis: Terratec Cinergy C PCI HD (CI)
> Author: Igor M. Liplianin
> Date:Wed May 9 07:23:14 2012 -0300
>
> This patch seems for rectifying a typo. But actually the difference between
> mantis_vp2040.c and mantis_vp2033.c code is a card name only.
>
> Signed-off-by: Igor M. Liplianin
> Signed-off-by: Mauro Carvalho Chehab
>
> drivers/media/dvb/mantis/mantis_cards.c |2 +-
> drivers/media/dvb/mantis/mantis_core.c |2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> ---
>
> http://git.linuxtv.org/media_tree.git?a=commitdiff;h=9fa4d6a102ebb06663a03554b57fb93ad618b72e
>
> diff --git a/drivers/media/dvb/mantis/mantis_cards.c
> b/drivers/media/dvb/mantis/mantis_cards.c
> index 095cf3a..0207d1f 100644
> --- a/drivers/media/dvb/mantis/mantis_cards.c
> +++ b/drivers/media/dvb/mantis/mantis_cards.c
> @@ -275,7 +275,7 @@ static struct pci_device_id mantis_pci_table[] = {
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C,
> &vp2033_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C,
> &vp2040_config),
> MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
> - MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
> + MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T,
> &vp3030_config),
> { }
> };
> diff --git a/drivers/media/dvb/mantis/mantis_core.c
> b/drivers/media/dvb/mantis/mantis_core.c
> index 22524a8..684d906 100644
> --- a/drivers/media/dvb/mantis/mantis_core.c
> +++ b/drivers/media/dvb/mantis/mantis_core.c
> @@ -121,7 +121,7 @@ static void mantis_load_config(struct mantis_pci *mantis)
> mantis->hwconfig = &vp2033_mantis_config;
> break;
> case MANTIS_VP_2040_DVB_C: /* VP-2040 */
> - case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
> + case CINERGY_C: /* VP-2040 clone */
> case TECHNISAT_CABLESTAR_HD2:
> mantis->hwconfig = &vp2040_mantis_config;
> break;
>
> ___
> linuxtv-commits mailing list
> linuxtv-comm...@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linuxtv-commits
--
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: [PATCH] Terratec Cinergy C PCI HD (CI)
On Wed, May 9, 2012 at 4:53 PM, Igor M. Liplianin wrote: > This patch seems for rectifying a typo. But actually the difference between > mantis_vp2040.c and mantis_vp2033.c code is a card name only. > > Signed-off-by: Igor M. Liplianin Do you have a card with the tda10021 or the tda10023 ? -- 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: Re: [PATCH] Terratec Cinergy C PCI HD (CI)
On 9 мая 2012 20:57:49 Bjørn Mork wrote:
> "Igor M. Liplianin" writes:
> > This patch seems for rectifying a typo. But actually the difference
> > between
> > mantis_vp2040.c and mantis_vp2033.c code is a card name only.
>
> Yes, there are major code duplication issues in this driver.
>
> > Signed-off-by: Igor M. Liplianin
> > diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_cards.c
> > --- a/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May 09 01:37:05
> > 2012 +0300 +++ b/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May
> > 09
> > 14:04:31 2012 +0300 @@ -276,7 +276,7 @@
> >
> > MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C, &vp2033_config),
> > MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C, &vp2040_config),
> > MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
> >
> > - MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
> > + MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
> >
> > MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T, &vp3030_config),
> > { }
> >
> > };
>
> What's the point? It's a constructed difference. Makes more sense to
> refactor and merge all the duplicated code instead of maintaining this
> meaningless code split.
>
> > diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_core.c
> > --- a/linux/drivers/media/dvb/mantis/mantis_core.c Wed May 09 01:37:05
> > 2012 +0300 +++ b/linux/drivers/media/dvb/mantis/mantis_core.c Wed May
> > 09
> > 14:04:31 2012 +0300 @@ -121,7 +121,7 @@
> >
> > mantis->hwconfig = &vp2033_mantis_config;
> > break;
> >
> > case MANTIS_VP_2040_DVB_C: /* VP-2040 */
> >
> > - case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
> > + case CINERGY_C: /* VP-2040 clone */
> >
> > case TECHNISAT_CABLESTAR_HD2:
> > mantis->hwconfig = &vp2040_mantis_config;
> > break;
>
> And this file should never have been merged into the mainline kernel at
> all. If you wonder how a bug like that could survive without being
> noticed, then the explanation is simple: This code has never been built
> as part of the driver in the mainline kernel.
>
> I tried submitting a cleanup patch to have it removed a long time ago:
> http://patchwork.linuxtv.org/patch/3680/
Oh, I wasn't aware of that.
> but it doesn't seem to have gone anywhere, like most of the patches for
> this driver - silently ignored until everyone forgets it and moves on.
>
> The code could certainly benefit from a major cleanup, but I don't see
> how that would ever happen. It sort of works. Better leave it there
> and spend valuable time elsewhere.
This patch is just a remainder. Seriously, I don't anticipate something.
Igor.
>
>
>
> Bjørn
--
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
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: [PATCH] Terratec Cinergy C PCI HD (CI)
"Igor M. Liplianin" writes:
> This patch seems for rectifying a typo. But actually the difference between
> mantis_vp2040.c and mantis_vp2033.c code is a card name only.
Yes, there are major code duplication issues in this driver.
> Signed-off-by: Igor M. Liplianin
> diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_cards.c
> --- a/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May 09 01:37:05
> 2012 +0300
> +++ b/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May 09 14:04:31
> 2012 +0300
> @@ -276,7 +276,7 @@
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C, &vp2033_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C, &vp2040_config),
> MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
> - MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
> + MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
> MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T, &vp3030_config),
> { }
> };
What's the point? It's a constructed difference. Makes more sense to
refactor and merge all the duplicated code instead of maintaining this
meaningless code split.
> diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_core.c
> --- a/linux/drivers/media/dvb/mantis/mantis_core.cWed May 09 01:37:05
> 2012 +0300
> +++ b/linux/drivers/media/dvb/mantis/mantis_core.cWed May 09 14:04:31
> 2012 +0300
> @@ -121,7 +121,7 @@
> mantis->hwconfig = &vp2033_mantis_config;
> break;
> case MANTIS_VP_2040_DVB_C: /* VP-2040 */
> - case TERRATEC_CINERGY_C_PCI:/* VP-2040 clone */
> + case CINERGY_C: /* VP-2040 clone */
> case TECHNISAT_CABLESTAR_HD2:
> mantis->hwconfig = &vp2040_mantis_config;
> break;
And this file should never have been merged into the mainline kernel at
all. If you wonder how a bug like that could survive without being
noticed, then the explanation is simple: This code has never been built
as part of the driver in the mainline kernel.
I tried submitting a cleanup patch to have it removed a long time ago:
http://patchwork.linuxtv.org/patch/3680/
but it doesn't seem to have gone anywhere, like most of the patches for
this driver - silently ignored until everyone forgets it and moves on.
The code could certainly benefit from a major cleanup, but I don't see
how that would ever happen. It sort of works. Better leave it there
and spend valuable time elsewhere.
Bjørn
--
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
[PATCH] Terratec Cinergy C PCI HD (CI)
This patch seems for rectifying a typo. But actually the difference between
mantis_vp2040.c and mantis_vp2033.c code is a card name only.
Signed-off-by: Igor M. Liplianin diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_cards.c
--- a/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May 09 01:37:05 2012 +0300
+++ b/linux/drivers/media/dvb/mantis/mantis_cards.c Wed May 09 14:04:31 2012 +0300
@@ -276,7 +276,7 @@
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2033_DVB_C, &vp2033_config),
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_2040_DVB_C, &vp2040_config),
MAKE_ENTRY(TECHNISAT, CABLESTAR_HD2, &vp2040_config),
- MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2033_config),
+ MAKE_ENTRY(TERRATEC, CINERGY_C, &vp2040_config),
MAKE_ENTRY(TWINHAN_TECHNOLOGIES, MANTIS_VP_3030_DVB_T, &vp3030_config),
{ }
};
diff -r 990a92e2410f linux/drivers/media/dvb/mantis/mantis_core.c
--- a/linux/drivers/media/dvb/mantis/mantis_core.c Wed May 09 01:37:05 2012 +0300
+++ b/linux/drivers/media/dvb/mantis/mantis_core.c Wed May 09 14:04:31 2012 +0300
@@ -121,7 +121,7 @@
mantis->hwconfig = &vp2033_mantis_config;
break;
case MANTIS_VP_2040_DVB_C: /* VP-2040 */
- case TERRATEC_CINERGY_C_PCI: /* VP-2040 clone */
+ case CINERGY_C: /* VP-2040 clone */
case TECHNISAT_CABLESTAR_HD2:
mantis->hwconfig = &vp2040_mantis_config;
break;
Re: AW: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hi, Does this patch works also for kernel 2.6.38 ? Kind regards David -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
On Sunday 29 May 2011 14:11:23 Bjørn Mork wrote: > Willem van Asperen writes: > > Actually, doing this on s2-liplianin-41388e396e0f (the one I downloaded > > today) gets: > > $ grep mantis_ca_init *.c > > > > mantis_ca.c:int mantis_ca_init(struct mantis_pci *mantis) > > mantis_dvb.c: mantis_ca_init(mantis); > > > > And in the function __devinit mantis_dvb_init(struct mantis_pci *mantis) > > it actually says: > > > > ... > > dvb_net_init(&mantis->dvb_adapter, &mantis->dvbnet, &mantis->demux.dmx); > > tasklet_init(&mantis->tasklet, mantis_dma_xfer, (unsigned long) mantis); > > mantis_frontend_init(mantis); > > mantis_ca_init(mantis); > > > > return 0; > > ... > > > > So it seems that this mantis_ca_init call is actually made nowadays. > > In the s2-liplianin yes. Not in mainline. Investigating the > differences might be useful. Indeed. % modprobe -r mantis % modprobe mantis gives: May 29 14:37:51 mythbox kernel: Mantis :03:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 May 29 14:37:51 mythbox kernel: DVB: registering new adapter (Mantis DVB adapter) May 29 14:37:52 mythbox kernel: DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... Nothing about CA -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
Willem van Asperen writes: > Actually, doing this on s2-liplianin-41388e396e0f (the one I downloaded > today) > gets: > $ grep mantis_ca_init *.c > > mantis_ca.c:int mantis_ca_init(struct mantis_pci *mantis) > mantis_dvb.c: mantis_ca_init(mantis); > > And in the function __devinit mantis_dvb_init(struct mantis_pci *mantis) it > actually says: > > ... > dvb_net_init(&mantis->dvb_adapter, &mantis->dvbnet, &mantis->demux.dmx); > tasklet_init(&mantis->tasklet, mantis_dma_xfer, (unsigned long) mantis); > mantis_frontend_init(mantis); > mantis_ca_init(mantis); > > return 0; > ... > > So it seems that this mantis_ca_init call is actually made nowadays. In the s2-liplianin yes. Not in mainline. Investigating the differences might be useful. Bjørn -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
On Saturday 28 May 2011 10:33:16 Bjørn Mork wrote: > Marc Coevoet writes: > > Op 27-05-11 21:48, Willem van Asperen schreef: > >> a) CAM support is currently not implemented for terratec HD > > > > For all cards? > > The CA code in the mantis driver isn't actually hooked into the driver > anywhere, so that't correct: No CAM will currently work with the > Terratec Cinergy C HD. > > Exported, but never called: > > bjorn@canardo:/usr/local/src/git/linux-2.6/drivers/media/dvb/mantis$ grep > mantis_ca_init *.c mantis_ca.c:int mantis_ca_init(struct mantis_pci > *mantis) > mantis_ca.c:EXPORT_SYMBOL_GPL(mantis_ca_init); Actually, doing this on s2-liplianin-41388e396e0f (the one I downloaded today) gets: $ grep mantis_ca_init *.c mantis_ca.c:int mantis_ca_init(struct mantis_pci *mantis) mantis_dvb.c: mantis_ca_init(mantis); And in the function __devinit mantis_dvb_init(struct mantis_pci *mantis) it actually says: ... dvb_net_init(&mantis->dvb_adapter, &mantis->dvbnet, &mantis->demux.dmx); tasklet_init(&mantis->tasklet, mantis_dma_xfer, (unsigned long) mantis); mantis_frontend_init(mantis); mantis_ca_init(mantis); return 0; ... So it seems that this mantis_ca_init call is actually made nowadays. I'll do some more digging -- check the /var/log/messages file for output of the mantis initialization -- and report back. Willem -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
On Saturday 28 May 2011 10:33:16 Bjørn Mork wrote: > Marc Coevoet writes: > > Op 27-05-11 21:48, Willem van Asperen schreef: > >> a) CAM support is currently not implemented for terratec HD > > > > For all cards? > > The CA code in the mantis driver isn't actually hooked into the driver > anywhere, so that't correct: No CAM will currently work with the > Terratec Cinergy C HD. > > Exported, but never called: > > bjorn@canardo:/usr/local/src/git/linux-2.6/drivers/media/dvb/mantis$ grep > mantis_ca_init *.c mantis_ca.c:int mantis_ca_init(struct mantis_pci > *mantis) > mantis_ca.c:EXPORT_SYMBOL_GPL(mantis_ca_init); > > > I don't know why, but I assume it's the same as with the remote control > code that was recently fixed Christoph Pinkl: The code probably wasn't > considered production ready when the driver was merged, and was therefore > "temporarily" disabled until it could be fixed. > > > Bjørn Can anyone confirm this and, if so, is someone working on getting this fixed? Like I said, happy to dig in and see if I can help here. But I would at least need to know what the current status is and an idea where the problem(s) sit. Regards, Willem -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
Marc Coevoet writes: > Op 27-05-11 21:48, Willem van Asperen schreef: >> >> a) CAM support is currently not implemented for terratec HD > > For all cards? The CA code in the mantis driver isn't actually hooked into the driver anywhere, so that't correct: No CAM will currently work with the Terratec Cinergy C HD. Exported, but never called: bjorn@canardo:/usr/local/src/git/linux-2.6/drivers/media/dvb/mantis$ grep mantis_ca_init *.c mantis_ca.c:int mantis_ca_init(struct mantis_pci *mantis) mantis_ca.c:EXPORT_SYMBOL_GPL(mantis_ca_init); I don't know why, but I assume it's the same as with the remote control code that was recently fixed Christoph Pinkl: The code probably wasn't considered production ready when the driver was merged, and was therefore "temporarily" disabled until it could be fixed. Bjørn -- 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: [linux-dvb] Terratec Cinergy C HD - CAM support.... Need help?
Op 27-05-11 21:48, Willem van Asperen schreef: a) CAM support is currently not implemented for terratec HD For all cards? I use TNT/dvb sticks, and you should be able to decode HD video with a so called "no hd" usb stick. Because it is a question of software, not hardware. Maybe, if one CAM card works, you should look for it ... Marc -- The "Penguin" has arrived - and he's not going away - ever. What's on Shortwave guide: choose an hour, go! http://shortwave.tk 700+ Radio Stations on SW http://swstations.tk 300+ languages on SW http://radiolanguages.tk -- 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
Terratec Cinergy C HD - CAM support.... Need help?
Hi All, I need something but willing to help out! I just got my Terratec Cinergy C HD card. After relatively minor issues I got the card running on my Mandriva 2010.2 (kernel 2.6.33) myth box. But... I am getting my DVB-C signal from the Ziggo (former Casema) network. I found a post that claims that all channels are encrypted (except for Nederland 1). Even though these are the standard channels that you also get when you just have an analog subscription. So. I need CAM support. After a couple of nights swimming the net I come to the conclusion that a) CAM support is currently not implemented b) This support has been not implemented for quite some time c) There are more people that would like it to work... So, dear people, is anyone working on getting the CAM to work on the Terratec Cinergy C HD card, but having problems? Is there any way, shape or form that I can assist in getting this support done? Or have we given up on this card and should I just take my loss and go for another card... If so, which one? Thanks, Willem -- 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: AW: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
On Sun, 22 May 2011, Christoph Pinkl wrote: > I've removed the rc_keyup call as the timeout release the key > automatically. This seems to work better. Yes it does! Thank you very much. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- 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
AW: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hello, I've removed the rc_keyup call as the timeout release the key automatically. This seems to work better. I also added the possibility to define different keytables for boards with different subsystems as Lou mentioned. Regards Chris mantis_ir.patch Description: Binary data
Re: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
I noticed that too on the C code: If keypress comes from the remote control, driver does both "push down" and "release" immediately. Some years ago I made a version that did something like this: I measured that a remote control sends "key pressed" in about 20ms cycles. Thus I decided that the driver can do following: Whe key '1' is pressed initially, send "key 1 pressed to input layer". If within 30ms a '1 pressed' comes from the remote control, driver keeps '1' as pressed (do nothing for input layer). If there won't come a '1 pressed' from remote within 30ms, then driver sends "key 1 unpressed to input layer". I don't know if there is any reusable algorithm (easilly usable code) for remote control drivers for this. Regards, Marko Ristola 21.05.2011 10:23, Adrian C. kirjoitti: > Haven't noticed earlier that every button press is executed twice, until > I did some testing with Oxine. Not sure how much Lirc is to blame for > this, and for button 0 not working. I will move to the Lirc list. > > Thanks again for the patch. > -- 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: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Haven't noticed earlier that every button press is executed twice, until I did some testing with Oxine. Not sure how much Lirc is to blame for this, and for button 0 not working. I will move to the Lirc list. Thanks again for the patch. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- 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: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hello, I got 2.6.39 so I tried this, on Technisat SkyStar2 HD2. Device showed up as /dev/input/event3. ir-keytable does not show any protocols for it: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver mantis_core, table rc-terratec-cinergy-s2-hd Supported protocols: Enabled protocols: Repeat delay = 500 ms, repeat period = 33 ms I moved lircd to devinput driver, and downloaded this[1] to use as lircd.conf. Restarted lircd and started irw. Only half of the buttons on my universal remote control (very suitable for VDR) show up. Then I tried the original Technisat TTS35AI and almost all keys registered, all but button "0". 1. http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- 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: AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
On Fri, 13 May 2011, Christoph Pinkl wrote: > Would be nice to get some Feedback. Hello, thanks for the patch. I've been waiting for 2.6.39 to hit the testing repository of my distribution before testing. Should happen any day. I need that version because of sound driver fixes. I have the SS2 HD2, will report how it goes. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- 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
AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hello Chris
This applies fine against 2.6.39 stable, but the Twinhan VP-1041 uses the
keymap of Twinhan DTV CAB CI, so it's not a perfect fit for the Terratec
Cinergy S2 HD keymap. I assume from earlier postings in vdr-portal [1] Cinergy
S2 HD and Skystar 2 HD do share the same keymappings.
Here's a paste of the VP-1041 keymap, as it used to work with s2-liplianin:
/* Twinhan VP-1041 */
static struct ir_scancode ir_codes_mantis_vp1041[] = {
{ 0x29, KEY_POWER},
{ 0x28, KEY_FAVORITES},
{ 0x30, KEY_TEXT},
{ 0x17, KEY_INFO}, /* Preview */
{ 0x23, KEY_EPG},
{ 0x3b, KEY_F22}, /* Record List */
{ 0x3c, KEY_1},
{ 0x3e, KEY_2},
{ 0x39, KEY_3},
{ 0x36, KEY_4},
{ 0x22, KEY_5},
{ 0x20, KEY_6},
{ 0x32, KEY_7},
{ 0x26, KEY_8},
{ 0x24, KEY_9},
{ 0x2a, KEY_0},
{ 0x33, KEY_CANCEL},
{ 0x2c, KEY_BACK},
{ 0x15, KEY_CLEAR},
{ 0x3f, KEY_TAB},
{ 0x10, KEY_ENTER},
{ 0x14, KEY_UP},
{ 0x0d, KEY_RIGHT},
{ 0x0e, KEY_DOWN},
{ 0x11, KEY_LEFT},
{ 0x21, KEY_VOLUMEUP},
{ 0x35, KEY_VOLUMEDOWN},
{ 0x3d, KEY_CHANNELDOWN},
{ 0x3a, KEY_CHANNELUP},
{ 0x2e, KEY_RECORD},
{ 0x2b, KEY_PLAY},
{ 0x13, KEY_PAUSE},
{ 0x25, KEY_STOP},
{ 0x1f, KEY_REWIND},
{ 0x2d, KEY_FASTFORWARD},
{ 0x1e, KEY_PREVIOUS}, /* Replay |< */
{ 0x1d, KEY_NEXT}, /* Skip >| */
{ 0x0b, KEY_CAMERA},/* Capture */
{ 0x0f, KEY_LANGUAGE}, /* SAP */
{ 0x18, KEY_MODE}, /* PIP */
{ 0x12, KEY_ZOOM}, /* Full screen */
{ 0x1c, KEY_SUBTITLE},
{ 0x2f, KEY_MUTE},
{ 0x16, KEY_F20}, /* L/R */
{ 0x38, KEY_F21}, /* Hibernate */
{ 0x37, KEY_SWITCHVIDEOMODE}, /* A/V */
{ 0x31, KEY_AGAIN}, /* Recall */
{ 0x1a, KEY_KPPLUS},/* Zoom+ */
{ 0x19, KEY_KPMINUS}, /* Zoom- */
{ 0x27, KEY_RED},
{ 0x0C, KEY_GREEN},
{ 0x01, KEY_YELLOW},
{ 0x00, KEY_BLUE},
};
struct ir_scancode_table ir_codes_mantis_vp1041_table = {
.scan = ir_codes_mantis_vp1041,
.size = ARRAY_SIZE(ir_codes_mantis_vp1041),
};
EXPORT_SYMBOL_GPL(ir_codes_mantis_vp1041_table);
Maybe someone else can confirm this?
Regards
Lou@vdr-portal
[1] http://www.vdr-portal.de/board18-vdr-hardware/board13-
fernbedienungen/95304-falsches-mapping-mit-fb-von-skystar-hd2-unter-linux/
> Hello,
>
> This patch is a rework of a old patch I've posted some time ago.
> It adds support for Remote-Control in the mantis driver and implements the
> new rc-API.
> The patch enables rc for the cards
> - vp1041
> - vp2033
> - vp2040
>
> It's only tested with a Terratec Cinergy S2 HD.
> Would be nice to get some Feedback.
>
> Regards
> Chris
--
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
AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hello, This patch is a rework of a old patch I've posted some time ago. It adds support for Remote-Control in the mantis driver and implements the new rc-API. The patch enables rc for the cards - vp1041 - vp2033 - vp2040 It's only tested with a Terratec Cinergy S2 HD. Would be nice to get some Feedback. Regards Chris mantis_ir.patch Description: Binary data
AW: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hello, I've decided to rework my patch once again and send it to the list. It adds support for Remote-Control in the mantis driver and implements the new rc-API. The patch enables rc for the cards - vp1041 - vp2033 - vp2040 It's only tested with a Terratec Cinergy S2 HD Regards Chris I've reworked my patch using at home for > -Ursprüngliche Nachricht- > Von: linux-media-ow...@vger.kernel.org [mailto:linux-media- > ow...@vger.kernel.org] Im Auftrag von Adrian C. > Gesendet: Dienstag, 10. Mai 2011 23:30 > An: linux-media@vger.kernel.org > Betreff: Re: Remote control not working for Terratec Cinergy C (2.6.37 > Mantis driver) > > On Fri, 6 May 2011, Marko Ristola wrote: > > > The hardware device is active (it is enabled, messages are sent from > > the remote to the Kernel Mantis software driver. The bytes can be > > logged into /var/log/messages file. > > > > That's all the driver is designed to do at this point. > > It doesn't sound promising. Thanks for the update Marko. > > -- > Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 > PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 > -- > 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 mantis_ir.patch Description: Binary data
Re: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
On Fri, 6 May 2011, Marko Ristola wrote: > The hardware device is active (it is enabled, messages are sent from > the remote to the Kernel Mantis software driver. The bytes can be > logged into /var/log/messages file. > > That's all the driver is designed to do at this point. It doesn't sound promising. Thanks for the update Marko. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- 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: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
04.05.2011 01:42, Adrian C. kirjoitti: > On Wed, 2 Mar 2011, Marko Ristola wrote: > >> So this means, that my remote control works, pressing key with hex >> value 0x26 works. > > It works. > >> Unfortunately mantis_uart.c doesn't have IR input initialization at >> all > > But it does not work. How can it work and not work at the same time? The hardware device is active (it is enabled, messages are sent from the remote to the Kernel Mantis software driver. The bytes can be logged into /var/log/messages file. That's all the driver is designed to do at this point. > > > I have the Skystar HD2 (b), subsystem: 1ae4:0003 now, same chipset as > Cinergy S2 and some others, VP-1041. Lirc failed with my old COM > receiver so I tried to use the cards IR as fall-back, and of course I > failed again. This was on 2.6.38.4. > > Only information I found is 1 year old[1]. "IR was in flux" but it still > doesn't work even though mantis pulls in all those ir-* modules, no > input device is created. > > Can someone fill us in, please, will it be supported this year? Would you please ask from Manu Abraham. Maybe he gets paid for doing it. I have experimented with my remote control too a few years ago, but I think it is good if Manu gets it as a job. Regards, Marko Ristola > > > 1. http://www.mail-archive.com/linux-media@vger.kernel.org/msg14641.html > -- > 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 > -- 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: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
On Wed, 2 Mar 2011, Marko Ristola wrote: > So this means, that my remote control works, pressing key with hex > value 0x26 works. It works. > Unfortunately mantis_uart.c doesn't have IR input initialization at > all But it does not work. How can it work and not work at the same time? I have the Skystar HD2 (b), subsystem: 1ae4:0003 now, same chipset as Cinergy S2 and some others, VP-1041. Lirc failed with my old COM receiver so I tried to use the cards IR as fall-back, and of course I failed again. This was on 2.6.38.4. Only information I found is 1 year old[1]. "IR was in flux" but it still doesn't work even though mantis pulls in all those ir-* modules, no input device is created. Can someone fill us in, please, will it be supported this year? 1. http://www.mail-archive.com/linux-media@vger.kernel.org/msg14641.html -- 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: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
02.03.2011 11:12, Jonas Hanschke kirjoitti: Thanks for answering, Marko. And sorry for asking a maybe stupid question - how do I turn on the debug output? There is no such option in make menuconfig, and modinfo -p mantis only returns: verbose:verbose startup messages, default is 1 (yes) I emailed this to Manu Abraham too, because he is the main author for mantis drivers. You can do: rmmod mantis modprobe mantis verbose=7 I have hardware: [ 4487.836265] Mantis :05:05.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18 [ 4487.837955] DVB: registering new adapter (Mantis DVB adapter) [ 4487.869550] IR RC5(x) protocol handler initialized [ 4487.923905] IR RC6 protocol handler initialized [ 4487.940785] IR JVC protocol handler initialized [ 4487.953168] IR Sony protocol handler initialized [ 4487.974220] lirc_dev: IR Remote Control driver registered, major 249 [ 4487.990015] IR LIRC bridge handler initialized [ 4488.697914] TDA10021: i2c-addr = 0x0c, id = 0x7c [ 4488.697931] DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)... [ 4831.498140] Mantis :05:05.0: PCI INT A disabled Here is what comes with verbose=7: ... [ 4890.486686] -- Stat=<4000800> Mask=<800> -- [ 4890.486695] mantis_uart_read (0): Reading ... <26> [ 4890.486704] mantis_uart_work (0): UART BUF:0 <26> [ 4890.486708] [ 4890.486714] mantis_uart_read (0): Reading ... <26> [ 4890.486719] mantis_uart_work (0): UART BUF:0 <26> So this means, that my remote control works, pressing key with hex value 0x26 works. Unfortunately mantis_uart.c doesn't have IR input initialization at all, so the remote control button press is just ignored in mantis_uart.c:mantis_uart_work() function. So this is partially implemented in mantis driver, No UART can work with Mantis in vanilla kernel. You can try to check mantis directory and mantis_uart.c, and see if there are some input_device_XXX functions. A good reference for implementation might be media/dvb/ttpci/av7110_ir.c: it looks like a working implementation with input device support. Regards, Marko Ristola In general, should the remote control appear as an input device (like it used to with the old, not-merged mantis driver) or is it possible that the approach has changed to an LIRC-driver where no input device is created? Also: your mail suggests that support may just be broken in the mainline kernel. In that case the info from the DVB wiki would just be incorrect and I would be looking for a solution that does not exist - is that just a hunch or do you acutally know it's not working? Jonas 2011/3/1 Marko Ristola: 28.02.2011 19:26, Jonas Hanschke kirjoitti: Hi, despite lots of time spent tinkering around and looking for help on the web, I've had no success in getting to work the remote control of my DVB-C card. It is a Terratec Cinergy C: http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C and am using the Mantis driver. Since it was merged into the kernel tree in 2.6.33, watching TV works without patches, but the remote control does not, although it is supposed to be supported, according to the link above. Kernel is a vanilla 2.6.37.2 with custom configuration on an old AMD Athlon XP machine, running debian Squeeze. When I modprobe the Mantis driver, the following IR-modules are pulled in automagically: ir_lirc_codec lirc_dev ir_core However, no input device is created during module loading. dmesg output: Mantis :01:0a.0: PCI INT A ->Link[APC1] ->GSI 16 (level, high) -> IRQ 16 DVB: registering new adapter (Mantis DVB adapter) IR LIRC bridge handler initialized DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... Am I missing some additional modules? Are there any dependencies on other kernel config options that are not handled automatically by make menuconf? If additional information is needed, I will be happy to provide it. However, I am not sure what is useful and what is not and did not want to bloat this message. Before merging into v4l-dvb, doing modprobe mantis was enough. I don't know how it should work with recent kernels. I haven't seen remote control working lately. Turning mantis module debug options on gives some information what is happening into /var/log/messages. Regards, Marko Ristola Thanks in advance, Jonas -- 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 -- 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 -- 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: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Thanks for answering, Marko. And sorry for asking a maybe stupid question - how do I turn on the debug output? There is no such option in make menuconfig, and modinfo -p mantis only returns: verbose:verbose startup messages, default is 1 (yes) In general, should the remote control appear as an input device (like it used to with the old, not-merged mantis driver) or is it possible that the approach has changed to an LIRC-driver where no input device is created? Also: your mail suggests that support may just be broken in the mainline kernel. In that case the info from the DVB wiki would just be incorrect and I would be looking for a solution that does not exist - is that just a hunch or do you acutally know it's not working? Jonas 2011/3/1 Marko Ristola : > 28.02.2011 19:26, Jonas Hanschke kirjoitti: >> >> Hi, >> >> despite lots of time spent tinkering around and looking for help on >> the web, I've had no success in getting to work the remote control of >> my DVB-C card. >> >> It is a Terratec Cinergy C: >> http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C >> >> and am using the Mantis driver. Since it was merged into the kernel >> tree in 2.6.33, watching TV works without patches, but the remote >> control does not, although it is supposed to be supported, according >> to the link above. >> >> Kernel is a vanilla 2.6.37.2 with custom configuration on an old AMD >> Athlon XP machine, running debian Squeeze. >> >> >> When I modprobe the Mantis driver, the following IR-modules are pulled >> in automagically: >> ir_lirc_codec >> lirc_dev >> ir_core >> >> However, no input device is created during module loading. dmesg output: >> Mantis :01:0a.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> >> IRQ 16 >> DVB: registering new adapter (Mantis DVB adapter) >> IR LIRC bridge handler initialized >> DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... >> >> Am I missing some additional modules? Are there any dependencies on >> other kernel config options that are not handled automatically by make >> menuconf? >> >> If additional information is needed, I will be happy to provide it. >> However, I am not sure what is useful and what is not and did not want >> to bloat this message. > > Before merging into v4l-dvb, doing modprobe mantis was enough. > I don't know how it should work with recent kernels. > I haven't seen remote control working lately. > > Turning mantis module debug options on gives some information > what is happening into /var/log/messages. > > Regards, > Marko Ristola > >> >> Thanks in advance, >> >> Jonas >> -- >> 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 >> > > -- 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: Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
28.02.2011 19:26, Jonas Hanschke kirjoitti: Hi, despite lots of time spent tinkering around and looking for help on the web, I've had no success in getting to work the remote control of my DVB-C card. It is a Terratec Cinergy C: http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C and am using the Mantis driver. Since it was merged into the kernel tree in 2.6.33, watching TV works without patches, but the remote control does not, although it is supposed to be supported, according to the link above. Kernel is a vanilla 2.6.37.2 with custom configuration on an old AMD Athlon XP machine, running debian Squeeze. When I modprobe the Mantis driver, the following IR-modules are pulled in automagically: ir_lirc_codec lirc_dev ir_core However, no input device is created during module loading. dmesg output: Mantis :01:0a.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> IRQ 16 DVB: registering new adapter (Mantis DVB adapter) IR LIRC bridge handler initialized DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... Am I missing some additional modules? Are there any dependencies on other kernel config options that are not handled automatically by make menuconf? If additional information is needed, I will be happy to provide it. However, I am not sure what is useful and what is not and did not want to bloat this message. Before merging into v4l-dvb, doing modprobe mantis was enough. I don't know how it should work with recent kernels. I haven't seen remote control working lately. Turning mantis module debug options on gives some information what is happening into /var/log/messages. Regards, Marko Ristola Thanks in advance, Jonas -- 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 -- 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
Remote control not working for Terratec Cinergy C (2.6.37 Mantis driver)
Hi, despite lots of time spent tinkering around and looking for help on the web, I've had no success in getting to work the remote control of my DVB-C card. It is a Terratec Cinergy C: http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C and am using the Mantis driver. Since it was merged into the kernel tree in 2.6.33, watching TV works without patches, but the remote control does not, although it is supposed to be supported, according to the link above. Kernel is a vanilla 2.6.37.2 with custom configuration on an old AMD Athlon XP machine, running debian Squeeze. When I modprobe the Mantis driver, the following IR-modules are pulled in automagically: ir_lirc_codec lirc_dev ir_core However, no input device is created during module loading. dmesg output: Mantis :01:0a.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> IRQ 16 DVB: registering new adapter (Mantis DVB adapter) IR LIRC bridge handler initialized DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... Am I missing some additional modules? Are there any dependencies on other kernel config options that are not handled automatically by make menuconf? If additional information is needed, I will be happy to provide it. However, I am not sure what is useful and what is not and did not want to bloat this message. Thanks in advance, Jonas -- 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: Terratec Cinergy C DVB-C card problems
Rune Evjen writes: > For some reason this module is not automatically loaded during boot > with ubuntu, but I added 'modprobe mantis' to /etc/rc.local so that it > loads during bootup. The mantis driver in linux 2.6.33-2.6.35-rc1 is still missing this patch: http://jusst.de/hg/mantis-v4l-dvb/raw-rev/3731f71ed6bf You can apply that on top of your Ubuntu 2.6.33 kernel if you want to add auto loading. Bjørn -- 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
Terratec Cinergy C DVB-C card problems
> Hi, > > I've got a terratec cinergy c dvb-c card, fresh install of ubuntu > 10.04 lucid i386. Card is here: > > http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C > > I followed the install instructions under "Driver", installing the one from > > http://mercurial.intuxication.org/hg/s2-liplianin > > dmesg output afterwards: > > http://dpaste.com/202745/ > > and lsmod/lspci: > > http://dpaste.com/202150/ > > The previous install that worked nicely was hardy, using > mantis-a9ecd19a37c9 that refused to compile with lucid's more recent > kernel. Any ideas? > > Billy > -- > 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 Hi, The Mantis drivers are available in the Ubuntu kernel 2.6.33. I installed this kernel on top of lucid using this PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/ Unfortunately, this kernel is built without the mantis module, after installing the kernel I also compiled the kernel source and copied the mantis modules into the /lib/modules/2.6.33-020633- generic/misc/ directory and ran 'depmod -a' I compiled the following modules to make it work: -rw-r--r-- 1 root root 10412 2010-05-27 18:15 hopper.ko -rw-r--r-- 1 root root 45620 2010-05-27 18:15 mantis_core.ko -rw-r--r-- 1 root root 25624 2010-05-27 18:15 mantis.ko -rw-r--r-- 1 root root 25244 2010-05-27 18:21 mb86a16.ko This is probably not the best approach, but it works. For some reason this module is not automatically loaded during boot with ubuntu, but I added 'modprobe mantis' to /etc/rc.local so that it loads during bootup. Best regards, Rune -- 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: Terratec Cinergy C DVB-C card problems
Billy Brumley writes: > I've got a terratec cinergy c dvb-c card, fresh install of ubuntu > 10.04 lucid i386. Card is here: > > http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C I don't know what's wrong with your installation, but you may want to try installing the mantis driver without completely replacing the dvb-core. FYI, the mantis driver will be included in the next Debian 2.6.32 based kernel release thanks to the excellent Debian kernel team: http://bugs.debian.org/57724 . I guess that means that it will be available in Unbuntu soon as well. Anyway, the patch from that bug report should easily apply to any 2.6.32 kernel without having to mess with the whole DVB system. Bjørn -- 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
Terratec Cinergy C DVB-C card problems
Hi, I've got a terratec cinergy c dvb-c card, fresh install of ubuntu 10.04 lucid i386. Card is here: http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C I followed the install instructions under "Driver", installing the one from http://mercurial.intuxication.org/hg/s2-liplianin dmesg output afterwards: http://dpaste.com/202745/ and lsmod/lspci: http://dpaste.com/202150/ The previous install that worked nicely was hardy, using mantis-a9ecd19a37c9 that refused to compile with lucid's more recent kernel. Any ideas? Billy -- 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: Remote for Terratec Cinergy C PCI HD (DVB-C)
On Mon, Jan 25, 2010 at 9:22 PM, MartinG wrote: > Hi, I've got the exact same device as you, use the s2-liplianin > driver, and after reading your post I tried the remote as well. > But how do I configure it? Some of the keys are working (arrow keys, > numeric keys, Home, volume, mute), but not all. > Is the remote handled as an input device by X itself? So what file(s) > do I need to change/update? > > If you have some working config files, or a nice link, I'd appreciate it :) Replying to myself; I found that 'xev' give the keycodes for most of the keys, but not eg. the "OK" key, wich is quite important. Is there a way to add those? Something I can contribute? Where? :) And by the way - I too really appreciate the work on the mantis driver! Best, MartinG -- 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: Remote for Terratec Cinergy C PCI HD (DVB-C)
On Thu, Jan 21, 2010 at 6:33 PM, Hans-Peter Wolf wrote: > Hi, > > I got it finally running! I just took the last s2-liplianin source and it > was detected automatically: > > I: Bus=0001 Vendor= Product= Version=0001 > N: Name="Mantis VP-2040 IR Receiver" > P: Phys=pci-:01:06.0/ir0 > S: Sysfs=/devices/virtual/input/input5 > U: Uniq= > H: Handlers=kbd event5 > B: EV=13 > B: KEY=108fc330 2842041 0 200018000 21804801 9e96c0 > ffc > > Strange, that it didn't work with v4l-dvb sources. > > Thank you very much. I really appreciate your work! Hi, I've got the exact same device as you, use the s2-liplianin driver, and after reading your post I tried the remote as well. But how do I configure it? Some of the keys are working (arrow keys, numeric keys, Home, volume, mute), but not all. Is the remote handled as an input device by X itself? So what file(s) do I need to change/update? If you have some working config files, or a nice link, I'd appreciate it :) Best, MartinG -- 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: Remote for Terratec Cinergy C PCI HD (DVB-C)
Hi, I got it finally running! I just took the last s2-liplianin source and it was detected automatically: I: Bus=0001 Vendor= Product= Version=0001 N: Name="Mantis VP-2040 IR Receiver" P: Phys=pci-:01:06.0/ir0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=13 B: KEY=108fc330 2842041 0 200018000 21804801 9e96c0 ffc Strange, that it didn't work with v4l-dvb sources. Thank you very much. I really appreciate your work! Regards Hans-Peter Hans-Peter Wolf schrieb: Hi, I installed the mantis driver from the v4l-dvb mercurial repository and got my tv-card Terratec Cinergy C PCI HD running successfully. However, I cannot find any information if the included remote, which also directly connected to the PCI card, is also working. The dmesg output gives me these lines at the startup (not comparable to the lines listed on linuxtv.org): [7.402278] Mantis :01:06.0: PCI INT A -> Link[LNKA] -> GSI 16 (level, low) -> IRQ 16 [7.403356] DVB: registering new adapter (Mantis DVB adapter) [8.322027] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... (I also had to add the module 'mantis' to /etc/modules to run it automatically at startup. Is this normal?) I also tried cat /proc/bus/input/devices but couldn't find a plausible device (output attached below). Can anyone tell me how to find out if the device is properly installed? Or better: How to install the remote device? Is there any special module required? Thank you very much in advance! Hans-Peter cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10 0 I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name="Macintosh mouse button emulation" P: Phys= S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=mouse0 event2 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=/video/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/device:13/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=3 B: KEY=3f000b 0 0 0 I: Bus=0003 Vendor=046d Product=c01f Version=0110 N: Name="Logitech USB-PS/2 Optical Mouse" P: Phys=usb-:00:02.0-6/input0 S: Sysfs=/devices/pci:00/:00:02.0/usb3/3-6/3-6:1.0/input/input4 U: Uniq= H: Handlers=mouse1 event4 B: EV=17 B: KEY=f 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=046a Product=0011 Version=0110 N: Name="HID 046a:0011" P: Phys=usb-:00:04.0-6/input0 S: Sysfs=/devices/pci:00/:00:04.0/usb4/4-6/4-6:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=7 I: Bus=0001 Vendor=10ec Product=0888 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci:00/:00:07.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=40001 B: SND=6 -- 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
Remote for Terratec Cinergy C PCI HD (DVB-C)
Hi, I installed the mantis driver from the v4l-dvb mercurial repository and got my tv-card Terratec Cinergy C PCI HD running successfully. However, I cannot find any information if the included remote, which also directly connected to the PCI card, is also working. The dmesg output gives me these lines at the startup (not comparable to the lines listed on linuxtv.org): [7.402278] Mantis :01:06.0: PCI INT A -> Link[LNKA] -> GSI 16 (level, low) -> IRQ 16 [7.403356] DVB: registering new adapter (Mantis DVB adapter) [8.322027] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... (I also had to add the module 'mantis' to /etc/modules to run it automatically at startup. Is this normal?) I also tried cat /proc/bus/input/devices but couldn't find a plausible device (output attached below). Can anyone tell me how to find out if the device is properly installed? Or better: How to install the remote device? Is there any special module required? Thank you very much in advance! Hans-Peter cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10 0 I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name="Macintosh mouse button emulation" P: Phys= S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=mouse0 event2 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=/video/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/device:13/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=3 B: KEY=3f000b 0 0 0 I: Bus=0003 Vendor=046d Product=c01f Version=0110 N: Name="Logitech USB-PS/2 Optical Mouse" P: Phys=usb-:00:02.0-6/input0 S: Sysfs=/devices/pci:00/:00:02.0/usb3/3-6/3-6:1.0/input/input4 U: Uniq= H: Handlers=mouse1 event4 B: EV=17 B: KEY=f 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=046a Product=0011 Version=0110 N: Name="HID 046a:0011" P: Phys=usb-:00:04.0-6/input0 S: Sysfs=/devices/pci:00/:00:04.0/usb4/4-6/4-6:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=7 I: Bus=0001 Vendor=10ec Product=0888 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci:00/:00:07.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=40001 B: SND=6 -- 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: Terratec Cinergy C PCI HD - different subsystems
On Tue, Jan 5, 2010 at 7:43 PM, Hemmelig Konto wrote: > Hi there > > I'm the owner of two Terratec Cinergy C PCI HD cards. > > I'm running on vanilla kernel 2.6.32.0 x64 and is using the s2-liblianin > driver. > > My problem is that the driver only see 1 of my 2 cards. > When I investigate the cards, I see that they have a different > subsystem identifiers : 153b:1178 which works, and 153b.01788 which > doesn't work. There are no visible difference between the card, as far > as I can see. > > How do I get the driver to "attach" to both the cards so I can get > both "adapter0" and "adapter1" - today it is only "adapter0" ? > > Please help !!! Does this help http://jusst.de/hg/mantis-v4l-dvb ? Regards, Manu -- 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
Terratec Cinergy C PCI HD - different subsystems
Hi there I'm the owner of two Terratec Cinergy C PCI HD cards. I'm running on vanilla kernel 2.6.32.0 x64 and is using the s2-liblianin driver. My problem is that the driver only see 1 of my 2 cards. When I investigate the cards, I see that they have a different subsystem identifiers : 153b:1178 which works, and 153b.01788 which doesn't work. There are no visible difference between the card, as far as I can see. How do I get the driver to "attach" to both the cards so I can get both "adapter0" and "adapter1" - today it is only "adapter0" ? Please help !!! /Ole W lspci -vnn output : 06:00.0 Multimedia controller [0480]: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] [1822:4e35] (rev 01) Subsystem: TERRATEC Electronic GmbH Device [153b:0178] Flags: bus master, medium devsel, latency 64, IRQ 16 Memory at edfff000 (32-bit, prefetchable) [size=4K] Kernel modules: mantis 06:01.0 Multimedia controller [0480]: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] [1822:4e35] (rev 01) Subsystem: TERRATEC Electronic GmbH Device [153b:1178] Flags: bus master, medium devsel, latency 64, IRQ 17 Memory at fdffe000 (32-bit, prefetchable) [size=4K] Kernel driver in use: Mantis Kernel modules: mantis dmesg output : Mantis :06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mantis :06:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 irq: 17, latency: 64 memory: 0xfdffe000, mmio: 0xc9001178e000 found a VP-2040 PCI DVB-C device on (06:01.0), Mantis Rev 1 [153b:1178], irq: 17, latency: 64 memory: 0xfdffe000, mmio: 0xc9001178e000 MAC Address=[00:08:ca:1e:88:83] mantis_alloc_buffers (1): DMA=0x37c6 cpu=0x880037c6 size=65536 mantis_alloc_buffers (1): RISC=0x37c06000 cpu=0x880037c06000 size=1000 DVB: registering new adapter (Mantis dvb adapter) input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input4 HDA Intel :01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 HDA Intel :01:00.1: setting latency timer to 64 mantis_frontend_init (1): Probing for CU1216 (DVB-C) TDA10023: i2c-addr = 0x0c, id = 0x7d mantis_frontend_init (1): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c mantis_frontend_init (1): Mantis DVB-C Philips CU1216 frontend attach success DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... mantis_ca_init (1): Registering EN50221 device mantis_ca_init (1): Registered EN50221 device mantis_hif_init (1): Adapter(1) Initializing Mantis Host Interface input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input5 Mantis VP-2040 IR Receiver: unknown key for scancode 0x Mantis VP-2040 IR Receiver: unknown key: key=0x00 down=1 Mantis VP-2040 IR Receiver: unknown key: key=0x00 down=0 -- 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: Terratec Cinergy C HD tuning problems
On Wed, Aug 19, 2009 at 11:10 PM, wrote: > I'm having some problems with my Terratec Cinergy C PCI DVB-C card. > ... > /var/log/syslog (when tuning stops working): >... > kernel: [55168.360122] mantis_ack_wait (0): Slave RACK Fail ! Hi, I have the same problem: Terratec Cinergy HD DVB-C PCI Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) VP-2040 PCI DVB-C device TDA10023 MythTV chokes after a while because of the error described above. Also, when I use w_scan, it is not able to scan (tune) for new channels. Similar problem is mentioned here: http://thread.gmane.org/gmane.linux.drivers.dvb/47829 These are my bits: s2-liplianin from http://mercurial.intuxication.org/hg/s2-liplianin (03 Jun) kernel-2.6.29.6-217.2.16.fc11.x86_64 Any hints on how to get this working appreciated. Removing and reinserting the mantis module doesn't seem to help for me. -MartinG -- 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
Terratec Cinergy C HD, PCI, DVB-C support in mainstream kernel
Hi I've read somewhere (can't remember where), that the Terratec Cinergy C HD card is now supported in the official linux kernel tree. Is this true or do I still need to compile the required modules myself? Thank you for your answers and please CC me, as I am not subscribed to this list. Best regards, Fabio Berta -- 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
Terratec Cinergy C HD tuning problems
Hello, I'm having some problems with my Terratec Cinergy C PCI DVB-C card. I installed the mantis driver via DKMS, following the instructions at http://www.linuxtv.org/wiki/index.php/Mantis_with_DKMS The card is recognized, and it even works, but after a while (typically 5 to 20 minutes) the card no longer tunes to any channels and the scan command no longer works. If I modprobe -r and modprobe -i the mantis module everything works again for a while, until the same thing happens. So I assume this is something driver related? Any help would be appreciated, I will be happy to provide any additional information if needed. Some information that may or may not be useful: uname -a : Linux ss-home-server 2.6.28-14-server #47-Ubuntu SMP Sat Jul 25 02:03:55 UTC 2009 x86_64 GNU/Linux lsmod | grep mantis : mantis 53892 4 lnbp21 11008 1 mantis mb86a1630464 1 mantis stb610016388 1 mantis tda10021 15364 1 mantis tda10023 15748 1 mantis ir_common 65924 1 mantis stb089945060 1 mantis stv029919720 1 mantis dvb_core 111792 2 mantis,stv0299 dmesg (after reloading mantis module): [50413.810181] mantis_core_exit (0): DMA engine stopping [50413.810185] mantis_dma_exit (0): DMA=0x3794 cpu=0x88003794 size=65536 [50413.810191] mantis_dma_exit (0): RISC=0x37953000 cpu=0x880037953000 size=1000 [50413.810195] mantis_hif_exit (0): Adapter(0) Exiting Mantis Host Interface [50413.810200] mantis_ca_exit (0): Unregistering EN50221 device [50413.810712] mantis_pci_remove (0): Removing -->Mantis irq: 21, latency: 32 [50413.810714] memory: 0xd080, mmio: 0xc200101ce000 [50413.810729] Mantis :02:00.0: PCI INT A disabled [50414.116512] Mantis :02:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [50414.117498] irq: 21, latency: 32 [50414.117499] memory: 0xd080, mmio: 0xc200104fe000 [50414.117502] found a VP-2040 PCI DVB-C device on (02:00.0), [50414.117504] Mantis Rev 1 [153b:1178], irq: 21, latency: 32 [50414.117507] memory: 0xd080, mmio: 0xc200104fe000 [50414.120219] MAC Address=[00:08:ca:1e:10:7a] [50414.120238] mantis_alloc_buffers (0): DMA=0x3794 cpu=0x88003794 size=65536 [50414.120245] mantis_alloc_buffers (0): RISC=0xb58a4000 cpu=0x8800b58a4000 size=1000 [50414.120248] DVB: registering new adapter (Mantis dvb adapter) [50414.670213] mantis_frontend_init (0): Probing for CU1216 (DVB-C) [50414.673722] TDA10023: i2c-addr = 0x0c, id = 0x7d [50414.673724] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c [50414.673727] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success [50414.673731] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... [50414.673789] mantis_ca_init (0): Registering EN50221 device [50414.673865] mantis_ca_init (0): Registered EN50221 device [50414.673874] mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface [50414.673934] input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input11 [50414.840123] Mantis VP-2040 IR Receiver: unknown key: key=0x00 raw=0x00 down=1 [50414.940104] Mantis VP-2040 IR Receiver: unknown key: key=0x00 raw=0x00 down=0 /var/log/syslog (when tuning stops working): kernel: [55125.206428] mantis start feed & dma kernel: [55125.206633] mantis stop feed and dma kernel: [55125.206641] mantis start feed & dma kernel: [55125.206719] mantis stop feed and dma kernel: [55125.206736] mantis start feed & dma vdr: [16282] frontend 0 lost lock on channel 80, tp 162 vdr: [16282] frontend 0 timed out while tuning to channel 80, tp 162 kernel: [55141.275154] mantis stop feed and dma vdr: [16282] frontend 0 timed out while tuning to channel 70, tp 234 kernel: [55168.360122] mantis_ack_wait (0): Slave RACK Fail ! vdr: [16282] frontend 0 timed out while tuning to channel 84, tp 242 vdr: [16282] frontend 0 timed out while tuning to channel 90, tp 250 kernel: [55202.040188] mantis_ack_wait (0): Slave RACK Fail ! Regards, Daniel Sjöblom PS. The repository I checked out from http://mercurial.intuxication.org/hg/s2-liplianin was (and still is) broken. A bad merge in v4l/Kconfig, lines 3164-3168. -- 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
Terratec Cinergy C
I just got a Terratec Cinergy C PCI HD CI, and as often happens, I notice problems right after the buy. In this case, it seems that CAM support is not available. While preparing to return the card, I wanted to check whether the support is expected soon. However, I have not been able to learn what the issues are from reading the archives. Can someone enlighten me? As a matter of principle, I would prefer getting this to work, so if I can help out with testing or even programming, do let me know. 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
CAM support for Terratec Cinergy C PCI HD CI
Hi all, I just bought a http://www.terratec.net/en/products/Cinergy_C_PCI_HD_CI_1612.html which reports as follows under Linux: 00:0f.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: TERRATEC Electronic GmbH Device 1178 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Link[LNKB] -> GSI 5 (level, low) -> IRQ 5 [ 16.741228] irq: 5, latency: 32 [ 16.741230] memory: 0xeb408000, mmio: 0xe0852000 [ 16.741237] found a VP-2040 PCI DVB-C device on (00:0f.0), [ 16.741241] Mantis Rev 1 [153b:1178], irq: 5, latency: 32 [ 16.741247] memory: 0xeb408000, mmio: 0xe0852000 [ 16.744411] MAC Address=[00:08:ca:1d:bc:ae] [ 16.744535] mantis_alloc_buffers (0): DMA=0x1eab cpu=0xdeab size=65536 [ 16.744551] mantis_alloc_buffers (0): RISC=0x1eb86000 cpu=0xdeb86000 size=1000 [ 16.744559] DVB: registering new adapter (Mantis dvb adapter) [ 17.264189] mantis_frontend_init (0): Probing for CU1216 (DVB-C) [ 17.267687] TDA10023: i2c-addr = 0x0c, id = 0x7d [ 17.267695] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c [ 17.267702] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success [ 17.267712] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... [ 17.268183] mantis_ca_init (0): Registering EN50221 device [ 17.319032] mantis_ca_init (0): Registered EN50221 device [ 17.319055] mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface I could not find any posts indicating that CAM support for this card has been implemented yet and a `gnutv -cammenu` just hangs forever. The CAM is a Conax 4.00e, btw. I'm wondering if there is someone working on implementing this and if I could help somehow by donating such a card to a developer? Would that help? Please let me know. Thanks, Marc -- 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: mantis build error on vanilla kernel 2.6.28.6 [Re: Terratec Cinergy C HD (PCI, DVB-C): how to make it work?]
Am Samstag, den 21.02.2009, 01:06 +0100 schrieb MartinG:
> On Sat, Feb 21, 2009 at 12:22 AM, hermann pitton
> wrote:
> > you can see changes on saa7134-alsa here.
> > http://linuxtv.org/hg/v4l-dvb/log/359d95e1d541/linux/drivers/media/video/saa7134/saa7134-alsa.c
> >
> > Likely this kernel backport is missing.
> > http://linuxtv.org/hg/v4l-dvb/rev/b4d664a2592a
>
> Thank you for your reply!
>
> I think I got it working, thanks to you. This is what I did (on the
> vanilla 2.6.28.6 kernel):
> $ cd mantis-5292a47772ad/
> $ make distclean clean
> $ cp v4l/saa7134-alsa.c v4l/saa7134-alsa.c.orig
> $ emacs -nw v4l/saa7134-alsa.c
> Patch according to:
> http://linuxtv.org/hg/v4l-dvb/diff/b4d664a2592a/linux/drivers/media/video/saa7134/saa7134-alsa.c
> $ make -j2
> (works)
>
> # make install
>
> remove all other (dvb) modules
>
> # modprobe mantis
>
> This gave me at least
> /dev/dvb/adapter0/{demux0,dvr0,frontend0,net0}
>
> But then the computer froze when I did:
> # scandvb dvb-apps/util/scan/dvb-c/no-Oslo-Get
> scanning dvb-apps/util/scan/dvb-c/no-Oslo-Get
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 24100 690 0 5
> initial transponder 27200 690 0 5
> initial transponder 28000 690 0 5
> initial transponder 29000 690 0 5
> initial transponder 29800 690 0 5
> initial transponder 30600 690 0 5
> initial transponder 31400 690 0 5
> initial transponder 32200 690 0 5
> initial transponder 33000 690 0 5
> initial transponder 33800 690 0 5
> initial transponder 34600 690 0 5
> initial transponder 35400 690 0 5
> initial transponder 36200 690 0 5
> initial transponder 37000 690 0 5
> initial transponder 37800 690 0 5
> initial transponder 38600 690 0 5
> initial transponder 39400 690 0 5
> initial transponder 41000 690 0 5
> initial transponder 44200 6952000 0 5
> initial transponder 48200 690 0 5
> initial transponder 49800 690 0 5
> >>> tune to: 24100:INVERSION_AUTO:690:FEC_NONE:QAM_256
>
> (total freeze here, not even ssh access to the box)
>
> I think I had the scandvb tool from a binary install, maybe I'll try
> to compile from sources.
> And I'll try to read some more docs.
>
> Thank you for helping me out on this!
>
> -MartinG
I am sorry for that.
To give an example.
If we are seated in a chair looking to the wall in front of us or better
to the horizon in the height of our eyes, without moving our eyes we can
see something like 180 degrees horizontally.
If we move our eyes we can see already a lot in our backs, if we move
our heads we can see already almost all in our backs, to move the body
is a further step only taken if really needed.
Now, from the first just sitting there, the vertical reception is a
little different, at least for me. Without moving the eyes we can see
our feet, not that sharp, but enough to be aware of.
In the upper direction it seems to be a little bit different, only the
half of what is present on the bottom is visible without moving ...
This seems to be a part of the conditio humanum we share with others :)
It is the same with out of kernel drivers.
Await Manu's instructions what to use for testing and if a 2.6.28 is
safe.
Cheers,
Hermann
--
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: mantis build error on vanilla kernel 2.6.28.6 [Re: Terratec Cinergy C HD (PCI, DVB-C): how to make it work?]
On Sat, Feb 21, 2009 at 12:22 AM, hermann pitton
wrote:
> you can see changes on saa7134-alsa here.
> http://linuxtv.org/hg/v4l-dvb/log/359d95e1d541/linux/drivers/media/video/saa7134/saa7134-alsa.c
>
> Likely this kernel backport is missing.
> http://linuxtv.org/hg/v4l-dvb/rev/b4d664a2592a
Thank you for your reply!
I think I got it working, thanks to you. This is what I did (on the
vanilla 2.6.28.6 kernel):
$ cd mantis-5292a47772ad/
$ make distclean clean
$ cp v4l/saa7134-alsa.c v4l/saa7134-alsa.c.orig
$ emacs -nw v4l/saa7134-alsa.c
Patch according to:
http://linuxtv.org/hg/v4l-dvb/diff/b4d664a2592a/linux/drivers/media/video/saa7134/saa7134-alsa.c
$ make -j2
(works)
# make install
remove all other (dvb) modules
# modprobe mantis
This gave me at least
/dev/dvb/adapter0/{demux0,dvr0,frontend0,net0}
But then the computer froze when I did:
# scandvb dvb-apps/util/scan/dvb-c/no-Oslo-Get
scanning dvb-apps/util/scan/dvb-c/no-Oslo-Get
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 24100 690 0 5
initial transponder 27200 690 0 5
initial transponder 28000 690 0 5
initial transponder 29000 690 0 5
initial transponder 29800 690 0 5
initial transponder 30600 690 0 5
initial transponder 31400 690 0 5
initial transponder 32200 690 0 5
initial transponder 33000 690 0 5
initial transponder 33800 690 0 5
initial transponder 34600 690 0 5
initial transponder 35400 690 0 5
initial transponder 36200 690 0 5
initial transponder 37000 690 0 5
initial transponder 37800 690 0 5
initial transponder 38600 690 0 5
initial transponder 39400 690 0 5
initial transponder 41000 690 0 5
initial transponder 44200 6952000 0 5
initial transponder 48200 690 0 5
initial transponder 49800 690 0 5
>>> tune to: 24100:INVERSION_AUTO:690:FEC_NONE:QAM_256
(total freeze here, not even ssh access to the box)
I think I had the scandvb tool from a binary install, maybe I'll try
to compile from sources.
And I'll try to read some more docs.
Thank you for helping me out on this!
-MartinG
--
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: mantis build error on vanilla kernel 2.6.28.6 [Re: Terratec Cinergy C HD (PCI, DVB-C): how to make it work?]
Hi, Am Freitag, den 20.02.2009, 21:29 +0100 schrieb MartinG: > Ok, I was told at #linuxtv on freenode to use a vanilla kernel, so I did: > > $ wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.6.tar.bz2 > $ tar xjf linux-2.6.28.6.tar.bz2 > $ cd linux-2.6.28.6/ > $ make menuconfig > $ sudo make modules_install install > (reboot) > > $ wget -c http://jusst.de/hg/mantis/archive/tip.tar.bz2 > $ tar xjf tip.tar.bz2 > $ cd mantis-5292a47772ad/ > $ make > ... > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c: In > function 'snd_card_saa7134_hw_params': > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:496: > error: implicit declaration of function 'snd_assert' > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:497: > error: expected expression before 'return' > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:498: > error: expected expression before 'return' > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:499: > error: expected expression before 'return' > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c: In > function 'snd_card_saa7134_new_mixer': > /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:950: > error: expected expression before 'return' > make[3]: *** [/home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.o] > Error 1 > make[2]: *** [_module_/home/gronslet/Download/mantis-5292a47772ad/v4l] Error 2 > make[2]: Leaving directory `/mythmedia/buffer/linux-2.6.28.6' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/home/gronslet/Download/mantis-5292a47772ad/v4l' > make: *** [all] Error 2 > > > What did I miss here? > > -MartinG you can see changes on saa7134-alsa here. http://linuxtv.org/hg/v4l-dvb/log/359d95e1d541/linux/drivers/media/video/saa7134/saa7134-alsa.c Likely this kernel backport is missing. http://linuxtv.org/hg/v4l-dvb/rev/b4d664a2592a Cheers, Hermann -- 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
mantis build error on vanilla kernel 2.6.28.6 [Re: Terratec Cinergy C HD (PCI, DVB-C): how to make it work?]
Ok, I was told at #linuxtv on freenode to use a vanilla kernel, so I did: $ wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.6.tar.bz2 $ tar xjf linux-2.6.28.6.tar.bz2 $ cd linux-2.6.28.6/ $ make menuconfig $ sudo make modules_install install (reboot) $ wget -c http://jusst.de/hg/mantis/archive/tip.tar.bz2 $ tar xjf tip.tar.bz2 $ cd mantis-5292a47772ad/ $ make ... /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c: In function 'snd_card_saa7134_hw_params': /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:496: error: implicit declaration of function 'snd_assert' /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:497: error: expected expression before 'return' /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:498: error: expected expression before 'return' /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:499: error: expected expression before 'return' /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c: In function 'snd_card_saa7134_new_mixer': /home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.c:950: error: expected expression before 'return' make[3]: *** [/home/gronslet/Download/mantis-5292a47772ad/v4l/saa7134-alsa.o] Error 1 make[2]: *** [_module_/home/gronslet/Download/mantis-5292a47772ad/v4l] Error 2 make[2]: Leaving directory `/mythmedia/buffer/linux-2.6.28.6' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/gronslet/Download/mantis-5292a47772ad/v4l' make: *** [all] Error 2 What did I miss here? -MartinG -- 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
Terratec Cinergy C HD (PCI, DVB-C): how to make it work?
Hi all, I'm new to this list and new to DVB in general. I've just bought a Terratec Cinergy C HD DVB-C card, since I've read it is working in Linux. However, I've got into some trouble when trying to compile the modules. I've read http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_C_DVB-C where it is suggested to use the s2-liplianin driver from http://mercurial.intuxication.org/hg/s2-liplianin (a bit strange, as that seems to be a DVB-S2 driver, while this card is DVB-C...) Anyway, it failed building. So I tried the mantis driver from http://jusst.de/hg/mantis, but also failed: $ make make -C /home/gronslet/Download/mantis/v4l make[1]: Entering directory `/home/gronslet/Download/mantis/v4l' No version yet, using 2.6.29-rc2 make[1]: Leaving directory `/home/gronslet/Download/mantis/v4l' make[1]: Entering directory `/home/gronslet/Download/mantis/v4l' scripts/make_makefile.pl Updating/Creating .config Preparing to compile for kernel version 2.6.29 Created default (all yes) .config file ./scripts/make_myconfig.pl make[1]: Leaving directory `/home/gronslet/Download/mantis/v4l' make[1]: Entering directory `/home/gronslet/Download/mantis/v4l' perl scripts/make_config_compat.pl /lib/modules/2.6.29-rc2/source ./.myconfig ./config-compat.h creating symbolic links... ln -sf . oss Kernel build directory is /lib/modules/2.6.29-rc2/build make -C /lib/modules/2.6.29-rc2/build SUBDIRS=/home/gronslet/Download/mantis/v4l modules make[2]: Entering directory `/mythmedia/buffer/drm-2.6' CC [M] /home/gronslet/Download/mantis/v4l/tuner-xc2028.o In file included from /home/gronslet/Download/mantis/v4l/tuner-xc2028.h:11, from /home/gronslet/Download/mantis/v4l/tuner-xc2028.c:22: /home/gronslet/Download/mantis/v4l/dvb_frontend.h:52: error: field 'fe_params' has incomplete type /home/gronslet/Download/mantis/v4l/dvb_frontend.h:297: warning: 'struct dvbfe_info' declared inside parameter list /home/gronslet/Download/mantis/v4l/dvb_frontend.h:297: warning: its scope is only this definition or declaration, which is probably not what you want /home/gronslet/Download/mantis/v4l/dvb_frontend.h:298: warning: 'enum dvbfe_delsys' declared inside parameter list /home/gronslet/Download/mantis/v4l/dvb_frontend.h:299: warning: 'enum dvbfe_delsys' declared inside parameter list /home/gronslet/Download/mantis/v4l/dvb_frontend.h:316: error: field 'fe_events' has incomplete type /home/gronslet/Download/mantis/v4l/dvb_frontend.h:317: error: field 'fe_params' has incomplete type /home/gronslet/Download/mantis/v4l/dvb_frontend.h:354: warning: 'enum dvbfe_fec' declared inside parameter list /home/gronslet/Download/mantis/v4l/dvb_frontend.h:354: warning: 'enum dvbfe_modulation' declared inside parameter list /home/gronslet/Download/mantis/v4l/dvb_frontend.h:359: warning: 'enum dvbfe_delsys' declared inside parameter list make[3]: *** [/home/gronslet/Download/mantis/v4l/tuner-xc2028.o] Error 1 make[2]: *** [_module_/home/gronslet/Download/mantis/v4l] Error 2 make[2]: Leaving directory `/mythmedia/buffer/drm-2.6' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/gronslet/Download/mantis/v4l' make: *** [all] Error 2 I also tried: $ hg clone http://linuxtv.org/hg/v4l-dvb $ cd v4l-dvb $ make $ sudo make install and that worked. But it didn't install a "mantis" module, so I'm not sure what to modprobe... A reboot didn't give any interesting info from "dmesg" either, possibly except for this: w83627ehf: Found W83627DHG chip at 0x290 ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] ACPI: Device needs an ACPI driver The full dmesg output can be found here: http://fpaste.org/paste/4085 This is using a 2.6.29 kernel from git (since my first attempts using a Fedora kernel (and -headers, -devel) from the repos failed) Actually, I've also tried "make reload" (in the v4l-dvb directory), and gave a bunch of info/errors, see http://fpaste.org/paste/4086. Among them: ivtv: Start initialization, version 1.4.0 ivtv: End initialization So I guess my questions are: 1) what modules do I need to get this card working? 2) what is the latest kernel version known to work? 3) Is this the right place to ask? (If not, where? should I file a bug somewhere?) Some more info: # lspci -vnn -s 04:00.0 04:00.0 Multimedia controller [0480]: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] [1822:4e35] (rev01) Subsystem: TERRATEC Electronic GmbH Device [153b:1178] Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at fdfff000 (32-bit, prefetchable) [size=4K] # uname -r 2.6.29-rc2 (from commit 1de9e8e70f5acc441550ca75433563d91b269bbe Author: Linus Torvalds) Any suggestions appreciated! -MartinG -- 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
