[linux-dvb] [PATCH] TT Budget 1500 S

Pavel Paprok ppaprok at applet.cz
Sun Feb 26 04:21:58 CET 2006


----- Original Message ----- 
From: "Perceval Anichini" <perceval.anichini at streamvision.fr>
To: <linux-dvb at linuxtv.org>
Sent: Wednesday, February 22, 2006 10:45 AM
Subject: Re: [linux-dvb] [PATCH] TT Budget 1500 S


>> Unfortunately, I'm not sure whether some LNB hardware might be damaged
>> if LLC is enabled for the wrong card. That's why I am very careful. ;-)
> I understand that :)
>
>> Hm - sounds like a hardware problem. Apparently the tuner needs a higher
>> voltage from the LNBP21 chip...
> Yep! Sounds the same to me !
>
>> The Technotrend/Nexus rev 2.3 cards use the same BSBE1/LNBP21 setup.
>> There were no problem reports although it is widely used with vdr.
>> Strange.
> If this is a hardware problem of the 1500S, this is normal :)
>
>> My sleep would be better if you could check that. ;-)
>> Anyway, if TT recommends that fix it should be safe.
> Ok.
>
>
>> Oops. ;-)
>>
>> Please test whether it works if you place something like
>> | if (budget->dev->pci->subsystem_device == 0x1017)
>> | lnbp21_enable_high_lnb_voltage(budget->dvb_frontend, 1)
>> after dvb_register_frontend().
> Yes, it is working like a charm. But don't you find
> it is a rather bad idea to write a structure like :
> switch (a)
> {
> case 0 :
> [...]
> }
>
> [...]
> if (a == 0)
> [...]
>
> I do understand that small patches are a good (and necessary !!!) thing
> so that it is easier to figure out that what's done is what it shall
> be... But in our case, I find this rather breaks the code structure :/
> That's why I prefered to handle the problem the way I did in my
> patches...
>
> Moreover, the budget.c and budget_ci.c structure is not the same. (And
> the same modification in budget_ci is even uglier !!!!), so maybe it
> would be a better idea to move first the code handling the card from
> budget.c to budget-ci.c, and then modify the LNB stuff ???????
>
> Am I write when I think that PCI subsystem ID 0x1017 is only
> the 1500 S card ????
> Wouldn't it be a good idea to start a README file in the ttpci tree
> which sums up the association PCI subsystem ID -> Full card name.
> I guess this does exists in the wiki or somewhere, but I didn't find
> it (to my great shame !)
>
>> > There is one more thing to do with this TT 1500 S card : move the code
>> > handling it in budget-ci -> it indeed has the CI part :)
>>
>> Does the card work if you simply move the 'case 0x1017'/'high voltage'
>> stuff to budget-ci?
> No, enabling the lnbp21 seems to be mandatory to make the card work
> properly... :(
>
>> Iirc there were some CI-related problems.
>> But if it works without CI these can be solved later...
> Yep. But as said above, maybe it would be a good thing to fix that
> now ???
> The patch only consists of duplicating the lnp21 stuff and the
> 0x1017 part from budget.c to budget-ci.c.
> I attach a (dirty) patch that does the job (but it needs both of my
> patch to be applied first), so that you can have an idea of the job to
> be done...

Hi,
last week ago I have tested my same card subid 0x1017, but with
optional CI extension board, after my own "moving" of code from
budget to budget-ci card start to work but was some "lost lock"
problems.. and you recommended me your patches... do you remember? :-)

So this week I start from scratch:  fresh v4l-dvb from mercurial
only with your 3 patches (ttpci-lnbp21-set-voltage-fixed-mask +
ttpci-tt-budget-1500s-fix + ttpci-1500s-moved-to-budget-ci)
to verify if my essential problem solved - but no, not solved.
later I also try to add 7146 dma buffer patch and set bigger
buffer but no luck.

As I found latter problem seems to start when interconnecting
S 1500 with the CI extension board:
- without CI extension board (interconnecting ribbon cable
unplugged) dvb card receiving all free programs stable and ok.
- when I connect CI board with ribbon cable, same free programs
still plays, but starts a "lost lock" and quality problems, on both
H and V polarization, even not depend if any CAM module
in CI slot inserted or removed.
- on encrypted program and CAM w/ valid crypto card inserted
encrypted program also starts to plays, but has a still same "lost lock"
problems as any free programs after connecting CI extension board.

Q: any idea why connecting of CI board even not used broke basic
free-to-air functionality above?

Q: may be a problem that a "enabling high lnb voltage : 1" after driver
initialization is followed "enabling high lnb voltage : 0" when first
tuning (time >= 3:00:12, but also after any next "lost lock" during
receiving!) ? :

Feb 26 02:59:23 dvbfm3 kernel: saa7146: register extension 'budget_ci dvb'.
Feb 26 02:59:23 dvbfm3 kernel: saa7146: found saa7146 @ mem df8c4000 
(revision 1, irq 209) (0x13c2,0x1017
).
Feb 26 02:59:23 dvbfm3 kernel: budget_ci: budget_ci_attach(): budget_ci: 
dd7d5800
Feb 26 02:59:23 dvbfm3 kernel: budget_core: ttpci_budget_init(): dev: 
de93d180, budget: dd7d5800
Feb 26 02:59:23 dvbfm3 kernel: budget_core: ttpci_budget_init(): budget: 
width = 376, height = 3840
Feb 26 02:59:23 dvbfm3 kernel: DVB: registering new adapter 
(TT-Budget/WinTV-NOVA-S/CI PCI (rev AL/alps b
sbe1 lnbp21 frontend)).
Feb 26 02:59:23 dvbfm3 kernel: adapter has MAC addr = 00:d0:5c:04:72:aa
Feb 26 02:59:23 dvbfm3 kernel: budget_core: budget_register(): budget: 
dd7d5800
Feb 26 02:59:23 dvbfm3 kernel: input: Budget-CI dvb ir receiver saa7146 (0) 
as /class/input/input5
Feb 26 02:59:23 dvbfm3 kernel: budget_ci: CI interface initialised
Feb 26 02:59:23 dvbfm3 kernel: budget_ci: lnbp21_enable_high_lnb_voltage_(): 
lnbp21_enable_high_lnb_volta
ge_ - enabling high lnb voltage : 1
Feb 26 02:59:23 dvbfm3 kernel: DVB: registering frontend 0 (ST STV0299 
DVB-S)...
Feb 26 02:59:25 dvbfm3 kernel: dvb_ca adapter 0: DVB CAM detected and 
initialised successfully
Feb 26 03:00:12 dvbfm3 kernel: budget_ci: lnbp21_enable_high_lnb_voltage_(): 
lnbp21_enable_high_lnb_volta
ge_ - enabling high lnb voltage : 0
Feb 26 03:00:12 dvbfm3 kernel: function : dvb_dvr_open
Feb 26 03:00:12 dvbfm3 kernel: budget_core: budget_start_feed(): budget: 
dd7d5800
Feb 26 03:00:12 dvbfm3 kernel: budget_core: start_ts_capture(): budget: 
dd7d5800
Feb 26 03:00:12 dvbfm3 kernel: budget_core: stop_ts_capture(): budget: 
dd7d5800
Feb 26 03:00:12 dvbfm3 kernel: budget_core: start_ts_capture(): budget: 
dd7d5800
Feb 26 03:00:12 dvbfm3 kernel: budget_core: stop_ts_capture(): budget: 
dd7d5800
Feb 26 03:00:12 dvbfm3 kernel: budget_core: start_ts_capture(): budget: 
dd7d5800

Q: may be a problem repeating "dvb_dvr_poll" messages randomly
during all dvb playing ? what it mean?

Feb 26 03:28:34 dvbfm3 kernel: function : dvb_dvr_poll
Feb 26 03:29:05 dvbfm3 last message repeated 8856 times
Feb 26 03:30:06 dvbfm3 last message repeated 17035 times
Feb 26 03:31:07 dvbfm3 last message repeated 17766 times
Feb 26 03:32:08 dvbfm3 last message repeated 17562 times
Feb 26 03:33:09 dvbfm3 last message repeated 17655 times
Feb 26 03:34:10 dvbfm3 last message repeated 17621 times
Feb 26 03:35:11 dvbfm3 last message repeated 17269 times
Feb 26 03:36:12 dvbfm3 last message repeated 16775 times
Feb 26 03:37:13 dvbfm3 last message repeated 16241 times
Feb 26 03:38:14 dvbfm3 last message repeated 16421 times
Feb 26 03:38:35 dvbfm3 last message repeated 2909 times
Feb 26 03:38:35 dvbfm3 kernel: budget_ci: lnbp21_enable_high_lnb_voltage_(): 
lnbp21_enable_high_lnb_voltage_ - enabling high lnb voltage : 0
Feb 26 03:38:36 dvbfm3 kernel: function : dvb_dvr_poll
Feb 26 03:39:07 dvbfm3 last message repeated 8558 times
Feb 26 03:39:56 dvbfm3 last message repeated 11145 times
Feb 26 03:39:57 dvbfm3 kernel: budget_ci: lnbp21_enable_high_lnb_voltage_(): 
lnbp21_enable_high_lnb_voltage_ - enabling high lnb voltage : 0
Feb 26 03:39:57 dvbfm3 kernel: function : dvb_dvr_poll

Q: last minor but very rare problem is that sometime I get error on setting
TONE or VOLTAGE on start of vlc, with (-1) value in brackets.
next start of vlc command in these cases often without repeating
same error...

[00000236] dvb access debug: trying to tune the frontend...
[00000236] dvb access debug: frequency 11836000 is in Ku-band
[00000236] dvb access debug: using inversion=2
[00000236] dvb access debug: using fec=9
[00000236] dvb access debug: using voltage=13
[00000236] dvb access debug: using tone=1
[00000236] dvb access error: ioctl FE_SET_TONE failed, tone=on (-1) Remote 
I/O error
[00000236] dvb access error: DVB-S: tuning failed

Thanks,
Pavel




More information about the linux-dvb mailing list