public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* Support for Terratec Cinergy 2400i DT in kernel 3.x
@ 2012-11-13  9:40 Frédéric
  2012-11-13 21:51 ` Patrice Chotard
  0 siblings, 1 reply; 6+ messages in thread
From: Frédéric @ 2012-11-13  9:40 UTC (permalink / raw)
  To: linux-media

Hi there,

This is my first post on this list; I hope I'm on the right place to discuss this problem. If 
not, feel free to tell me where I should post.

I bought this DVB-T dual tuner card, in order to put it in my HTPC (running geeXboX/XBMC).

As far as I know, there where only support (patches) for kernel 2.6.x; I didn't find anything 
for 3.x branch. So I tried to port the patches. And I think I got something... Well, maybe!

I followed the links on this wiki page:

    http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_2400i_DVB-T

It seems that the PCIe bridge used on this card needs a firmware in order to work; this is what 
the patch does. I used this files:

    http://wiki.ubuntuusers.de/_attachment?target=/Terratec_Cinergy_2400i_DT/ngene_p11.tar.gz

As my desktop PC runs under debian sid, I only have a 3.2 kernel, so this is the version I 
patched to test the driver.

I can provide all files needed, but I just want to know if the following messages sounds good 
or if there are still problems...

During boot, I get:

 nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
 ngene 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
 ngene: Found Terratec Integra/Cinergy2400i Dual DVB-T
 ngene 0000:03:00.0: setting latency timer to 64
 ngene: Device version 1
 ngene: Loading firmware file ngene_17.fw.
 cxd2099_attach: driver disabled by Kconfig
 DVB: registering new adapter (nGene)
 DVB: registering adapter 0 frontend 0 (Micronas DRXD DVB-T)...
 DVB: registering new adapter (nGene)
 DVB: registering adapter 1 frontend 0 (Micronas DRXD DVB-T)...

Then, when I launch w_scan, I get this from kernel:

 drxd: deviceId = 0000
 DRX3975D-A2
 read deviation -520
 drxd: deviceId = 0000
 DRX3975D-A2
 read deviation -333

and this from w_scan (no antenna pluged):

 $ w_scan -ft -cFR
 w_scan version 20120605 (compiled for DVB API 5.4)
 using settings for FRANCE
 DVB aerial
 DVB-T FR
 scan type TERRESTRIAL, channellist 5
 output format vdr-1.6
 output charset 'UTF-8', use -C <charset> to override
 Info: using DVB adapter auto detection.
         /dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-) ¹
         /dev/dvb/adapter1/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-) ¹
 Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
 -_-_-_-_ Getting frontend capabilities-_-_-_-_ 
 Using DVB API 5.4
 frontend 'Micronas DRXD DVB-T' supports
 INVERSION_AUTO
 QAM_AUTO
 TRANSMISSION_MODE_AUTO
 GUARD_INTERVAL_AUTO
 HIERARCHY_AUTO
 FEC_AUTO
 FREQ (47.12MHz ... 855.25MHz)
 -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
 Scanning 8MHz frequencies...
 474000: (time: 00:00) 
 474166: (time: 00:03) 
 473834: (time: 00:05) 
 ...
 849834: (time: 09:57) 
 850332: (time: 09:59) 
 850498: (time: 10:02) 
 858000: (time: 10:04)   skipped: (freq 858000000 unsupported by driver)

 initial_tune:2265: Setting frontend failed QAM_AUTO f = 858000 kHz I999B8C999D999T999G999Y999
 858166: (time: 10:04)   skipped: (freq 858166000 unsupported by driver)

 initial_tune:2265: Setting frontend failed QAM_AUTO f = 858166 kHz I999B8C999D999T999G999Y999
 857834: (time: 10:04)   skipped: (freq 857834000 unsupported by driver)

 initial_tune:2265: Setting frontend failed QAM_AUTO f = 857834 kHz I999B8C999D999T999G999Y999
 858332: (time: 10:04)   skipped: (freq 858332000 unsupported by driver)

 initial_tune:2265: Setting frontend failed QAM_AUTO f = 858332 kHz I999B8C999D999T999G999Y999
 858498: (time: 10:04)   skipped: (freq 858498000 unsupported by driver)

 initial_tune:2265: Setting frontend failed QAM_AUTO f = 858498 kHz I999B8C999D999T999G999Y999

 ERROR: Sorry - i couldn't get any working frequency/transponder
  Nothing to scan!!

Reading all these logs, can you tell me if you see obvious problems? I'm neither a kernel guru 
(this is my first driver contact), nor a DVB-T user (so far!), so a lot of things are not clear 
to me.

Thanks for reading.

¹ first time w_scan is launched, these lines take 2-3 seconds, and I guess this is when the 
drxd kernel messages are output.

-- 
   Frédéric

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
  2012-11-13  9:40 Support for Terratec Cinergy 2400i DT in kernel 3.x Frédéric
@ 2012-11-13 21:51 ` Patrice Chotard
  2012-11-14  8:48   ` Frédéric
  0 siblings, 1 reply; 6+ messages in thread
From: Patrice Chotard @ 2012-11-13 21:51 UTC (permalink / raw)
  To: Frédéric; +Cc: linux-media


Hi Frédéric,

Two patches have been already submitted and are available since v3.7-rc1

media] ngene: add support for Terratec Cynergy 2400i Dual DVB-T  :
397e972350c42cbaf3228fe2eec23fecf6a69903

and

media] dvb: add support for Thomson DTT7520X :
5fb67074c6657edc34867cba78255b6f5b505f12

Reading your logs, everything seems OK, i think that with a plugged
antenna the w_scan should indicate that it founds at least some DVB-T
signals like these :

$ w_scan -ft -cFR
w_scan version 20120605 (compiled for DVB API 5.4)
using settings for FRANCE
DVB aerial
DVB-T FR
scan type TERRESTRIAL, channellist 5
output format vdr-1.6
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
	/dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-)
	/dev/dvb/adapter1/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-)
Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.6
frontend 'Micronas DRXD DVB-T' supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
FREQ (185.00MHz ... 855.25MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning 8MHz frequencies...
474000: (time: 00:03)
474166: (time: 00:05)
473834: (time: 00:08)
474332: (time: 00:10)
474498: (time: 00:13)
482000: (time: 00:15) (time: 00:16) signal ok:
	QAM_AUTO f = 482000 kHz I999B8C999D999T999G999Y999
undefined coderate HP
	new transponder:
	   (QAM_64   f = 4294967 kHz I999B8C999D0T8G32Y0) 0x405A
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
482166: (time: 00:30) (time: 00:31) signal ok:
	QAM_AUTO f = 482166 kHz I999B8C999D999T999G999Y999
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
481834: (time: 00:45) (time: 00:46) signal ok:
	QAM_AUTO f = 481834 kHz I999B8C999D999T999G999Y999
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
482332: (time: 01:00) (time: 01:01)
482498: (time: 01:02) (time: 01:04)
490000: (time: 01:05) (time: 01:06) signal ok:
	QAM_AUTO f = 490000 kHz I999B8C999D999T999G999Y999
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
undefined coderate HP
490166: (time: 01:20) (time: 01:21) signal ok:
	QAM_AUTO f = 490166 kHz I999B8C999D999T999G999Y999




Patrice

On 13/11/2012 10:40, Frédéric wrote:
> Hi there,
> 
> This is my first post on this list; I hope I'm on the right place to discuss this problem. If 
> not, feel free to tell me where I should post.
> 
> I bought this DVB-T dual tuner card, in order to put it in my HTPC (running geeXboX/XBMC).
> 
> As far as I know, there where only support (patches) for kernel 2.6.x; I didn't find anything 
> for 3.x branch. So I tried to port the patches. And I think I got something... Well, maybe!
> 
> I followed the links on this wiki page:
> 
>     http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_2400i_DVB-T
> 
> It seems that the PCIe bridge used on this card needs a firmware in order to work; this is what 
> the patch does. I used this files:
> 
>     http://wiki.ubuntuusers.de/_attachment?target=/Terratec_Cinergy_2400i_DT/ngene_p11.tar.gz
> 
> As my desktop PC runs under debian sid, I only have a 3.2 kernel, so this is the version I 
> patched to test the driver.
> 
> I can provide all files needed, but I just want to know if the following messages sounds good 
> or if there are still problems...
> 
> During boot, I get:
> 
>  nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
>  ngene 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
>  ngene: Found Terratec Integra/Cinergy2400i Dual DVB-T
>  ngene 0000:03:00.0: setting latency timer to 64
>  ngene: Device version 1
>  ngene: Loading firmware file ngene_17.fw.
>  cxd2099_attach: driver disabled by Kconfig
>  DVB: registering new adapter (nGene)
>  DVB: registering adapter 0 frontend 0 (Micronas DRXD DVB-T)...
>  DVB: registering new adapter (nGene)
>  DVB: registering adapter 1 frontend 0 (Micronas DRXD DVB-T)...
> 
> Then, when I launch w_scan, I get this from kernel:
> 
>  drxd: deviceId = 0000
>  DRX3975D-A2
>  read deviation -520
>  drxd: deviceId = 0000
>  DRX3975D-A2
>  read deviation -333
> 
> and this from w_scan (no antenna pluged):
> 
>  $ w_scan -ft -cFR
>  w_scan version 20120605 (compiled for DVB API 5.4)
>  using settings for FRANCE
>  DVB aerial
>  DVB-T FR
>  scan type TERRESTRIAL, channellist 5
>  output format vdr-1.6
>  output charset 'UTF-8', use -C <charset> to override
>  Info: using DVB adapter auto detection.
>          /dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-) ¹
>          /dev/dvb/adapter1/frontend0 -> TERRESTRIAL "Micronas DRXD DVB-T": good :-) ¹
>  Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
>  -_-_-_-_ Getting frontend capabilities-_-_-_-_ 
>  Using DVB API 5.4
>  frontend 'Micronas DRXD DVB-T' supports
>  INVERSION_AUTO
>  QAM_AUTO
>  TRANSMISSION_MODE_AUTO
>  GUARD_INTERVAL_AUTO
>  HIERARCHY_AUTO
>  FEC_AUTO
>  FREQ (47.12MHz ... 855.25MHz)
>  -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
>  Scanning 8MHz frequencies...
>  474000: (time: 00:00) 
>  474166: (time: 00:03) 
>  473834: (time: 00:05) 
>  ...
>  849834: (time: 09:57) 
>  850332: (time: 09:59) 
>  850498: (time: 10:02) 
>  858000: (time: 10:04)   skipped: (freq 858000000 unsupported by driver)
> 
>  initial_tune:2265: Setting frontend failed QAM_AUTO f = 858000 kHz I999B8C999D999T999G999Y999
>  858166: (time: 10:04)   skipped: (freq 858166000 unsupported by driver)
> 
>  initial_tune:2265: Setting frontend failed QAM_AUTO f = 858166 kHz I999B8C999D999T999G999Y999
>  857834: (time: 10:04)   skipped: (freq 857834000 unsupported by driver)
> 
>  initial_tune:2265: Setting frontend failed QAM_AUTO f = 857834 kHz I999B8C999D999T999G999Y999
>  858332: (time: 10:04)   skipped: (freq 858332000 unsupported by driver)
> 
>  initial_tune:2265: Setting frontend failed QAM_AUTO f = 858332 kHz I999B8C999D999T999G999Y999
>  858498: (time: 10:04)   skipped: (freq 858498000 unsupported by driver)
> 
>  initial_tune:2265: Setting frontend failed QAM_AUTO f = 858498 kHz I999B8C999D999T999G999Y999
> 
>  ERROR: Sorry - i couldn't get any working frequency/transponder
>   Nothing to scan!!
> 
> Reading all these logs, can you tell me if you see obvious problems? I'm neither a kernel guru 
> (this is my first driver contact), nor a DVB-T user (so far!), so a lot of things are not clear 
> to me.
> 
> Thanks for reading.
> 
> ¹ first time w_scan is launched, these lines take 2-3 seconds, and I guess this is when the 
> drxd kernel messages are output.
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
  2012-11-13 21:51 ` Patrice Chotard
@ 2012-11-14  8:48   ` Frédéric
  2012-11-14  9:36     ` Frédéric
  2012-11-14 20:46     ` Patrice Chotard
  0 siblings, 2 replies; 6+ messages in thread
From: Frédéric @ 2012-11-14  8:48 UTC (permalink / raw)
  To: Patrice Chotard; +Cc: linux-media

Le mardi 13 novembre 2012, Patrice Chotard a écrit :

> Two patches have been already submitted and are available since v3.7-rc1
> 
> media] ngene: add support for Terratec Cynergy 2400i Dual DVB-T  :
> 397e972350c42cbaf3228fe2eec23fecf6a69903
> 
> and
> 
> media] dvb: add support for Thomson DTT7520X :
> 5fb67074c6657edc34867cba78255b6f5b505f12

I had a look at your patches. I don't see the '.fw_version' param anymore in the 'ngene_info' 
structure... Is it normal?

-- 
   Frédéric

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
  2012-11-14  8:48   ` Frédéric
@ 2012-11-14  9:36     ` Frédéric
  2012-11-14 20:50       ` Patrice Chotard
  2012-11-14 20:46     ` Patrice Chotard
  1 sibling, 1 reply; 6+ messages in thread
From: Frédéric @ 2012-11-14  9:36 UTC (permalink / raw)
  To: Patrice Chotard; +Cc: linux-media

Le mercredi 14 novembre 2012, Frédéric a écrit :

> I had a look at your patches. I don't see the '.fw_version' param anymore
> in the 'ngene_info' structure... Is it normal?

I also noticed some differences in the PLL presets:

In your patch:

    .entries = {
            {  305000000, 166667, 0xb4, 0x12 },
            {  405000000, 166667, 0xbc, 0x12 },
            {  445000000, 166667, 0xbc, 0x12 },
            {  465000000, 166667, 0xf4, 0x18 },
            {  735000000, 166667, 0xfc, 0x18 },
            {  835000000, 166667, 0xbc, 0x18 },
            {  999999999, 166667, 0xfc, 0x18 },
    },

In original patch:

    if (freq<177000000 || freq>858000000)
        return -EINVAL;
    else if (freq<305000000) { c1=0xb4; c2=0x12; }
    else if (freq<405000000) { c1=0xbc; c2=0x12; }
    else if (freq<445000000) { c1=0xf4; c2=0x12; }
    else if (freq<465000000) { c1=0xfc; c2=0x12; }
    else if (freq<735000000) { c1=0xbc; c2=0x18; }
    else if (freq<835000000) { c1=0xf4; c2=0x18; }
    else { c1=0xfc; c2=0x18; }

-- 
   Frédéric

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
  2012-11-14  8:48   ` Frédéric
  2012-11-14  9:36     ` Frédéric
@ 2012-11-14 20:46     ` Patrice Chotard
  1 sibling, 0 replies; 6+ messages in thread
From: Patrice Chotard @ 2012-11-14 20:46 UTC (permalink / raw)
  To: Frédéric; +Cc: linux-media, rjkm, Mauro Carvalho Chehab

Hi Frédéric,

You are right, in the ngene initial commit
(dae52d009fc950b5c209260d50fcc000f5becd3c), no fw_version was set, so by
default the ngene_15.fw is selected.

But in the patch available here
http://wiki.ubuntuusers.de/_attachment?target=/Terratec_Cinergy_2400i_DT/ngene_p11.tar.gz,
fw_version = 17 was set in ngene_info_terratec struct.

Before submitting the ngene patch set i have done tests with all
available firmware without noticing any difference.

I really don't known what are the difference between ngene_15.fw and
ngene_17.fw

Perhaps Ralph or Mauro has the answer ?



On 14/11/2012 09:48, Frédéric wrote:
> Le mardi 13 novembre 2012, Patrice Chotard a écrit :
> 
>> Two patches have been already submitted and are available since v3.7-rc1
>>
>> media] ngene: add support for Terratec Cynergy 2400i Dual DVB-T  :
>> 397e972350c42cbaf3228fe2eec23fecf6a69903
>>
>> and
>>
>> media] dvb: add support for Thomson DTT7520X :
>> 5fb67074c6657edc34867cba78255b6f5b505f12
> 
> I had a look at your patches. I don't see the '.fw_version' param anymore in the 'ngene_info' 
> structure... Is it normal?
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
  2012-11-14  9:36     ` Frédéric
@ 2012-11-14 20:50       ` Patrice Chotard
  0 siblings, 0 replies; 6+ messages in thread
From: Patrice Chotard @ 2012-11-14 20:50 UTC (permalink / raw)
  To: Frédéric; +Cc: linux-media

Yes, there are differences, simply because algorithms which use these
tables are different ;-).


On 14/11/2012 10:36, Frédéric wrote:
> Le mercredi 14 novembre 2012, Frédéric a écrit :
> 
>> I had a look at your patches. I don't see the '.fw_version' param anymore
>> in the 'ngene_info' structure... Is it normal?
> 
> I also noticed some differences in the PLL presets:
> 
> In your patch:
> 
>     .entries = {
>             {  305000000, 166667, 0xb4, 0x12 },
>             {  405000000, 166667, 0xbc, 0x12 },
>             {  445000000, 166667, 0xbc, 0x12 },
>             {  465000000, 166667, 0xf4, 0x18 },
>             {  735000000, 166667, 0xfc, 0x18 },
>             {  835000000, 166667, 0xbc, 0x18 },
>             {  999999999, 166667, 0xfc, 0x18 },
>     },
> 
> In original patch:
> 
>     if (freq<177000000 || freq>858000000)
>         return -EINVAL;
>     else if (freq<305000000) { c1=0xb4; c2=0x12; }
>     else if (freq<405000000) { c1=0xbc; c2=0x12; }
>     else if (freq<445000000) { c1=0xf4; c2=0x12; }
>     else if (freq<465000000) { c1=0xfc; c2=0x12; }
>     else if (freq<735000000) { c1=0xbc; c2=0x18; }
>     else if (freq<835000000) { c1=0xf4; c2=0x18; }
>     else { c1=0xfc; c2=0x18; }
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-11-14 20:50 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-13  9:40 Support for Terratec Cinergy 2400i DT in kernel 3.x Frédéric
2012-11-13 21:51 ` Patrice Chotard
2012-11-14  8:48   ` Frédéric
2012-11-14  9:36     ` Frédéric
2012-11-14 20:50       ` Patrice Chotard
2012-11-14 20:46     ` Patrice Chotard

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox