[linux-dvb] Future of Multiproto

Manu Abraham abraham.manu at gmail.com
Fri Oct 12 09:56:21 CEST 2007

Johannes Stezenbach wrote:
> On Fri, Oct 12, 2007, Manu Abraham wrote:
>> Johannes Stezenbach wrote:
>>> Does that mean that Manu has no intentions to get
>>> his multiproto API changes merged?
>> It will be merged
> When? Why hasn't it been merged months ago when HVR4000 worked?

HVR4000 was struggling even recently howto handle pilots, because it 
had a hard time trying to figure out how pilots worked. Eventually, the 
implementation from the STB0899 had to be copied to the same, for it 
to work. The reason being CX24116 being mostly RE'd, AFAIH.

>>> (If so, then wtf was the point of doing them and keep
>>> everyone waiting? But I guess the "DVB API update" thread
>>> meant he isn't happy with it anymore.))
>> As i wrote, there are more things in the S2 specification, also 
>> currently stuff like proper statistics cannot be done for example
> As I tried to tell you in one of my replies in the "DVB API update"
> thread statistics is totally independent of DVB-S2. And the
> "more things" were not spelled out in detail by you -- and
> why don't you just fix the API if you know something is missing,
> instead of saying "something's missing, can't merge yet"?

Please, Just look at the changesets for the same.

> I just can't understand why you were dragging this out so long,
> usually I would expect the desire of any developer is to get
> the code merged ASAP. With a working HVR4000 driver you could've

FYI, the STB0899 driver is much older than the HVR4000 driver, it has 
been delayed because of

1) too much noise on the ML (you had bit much to do with it)
2) The feedback that resulted from the discussions on the ML, were 
not sufficient for a complete API, eventually STM chipped in, was a 
lot of struggle at my side too.

> got the API and dvb-core changes merged months ago -- which would've
> allowed you to merge the STB0899 driver in CONFIG_EXPERIMENTAL
> status to expose it to a wider audience if you'd wanted to.

Your earlier statements resulted thus:

* go experimental
* no experimental
* go experimental

Looks like some square wave function. Are harmonics expected ?

> Instead you seem to have the desire to work on your private branch
> forever, adding patch upon patch to make it as big and important
> as possible. 

Can you please point to the changesets which cause you to mention 
"adding patch upon patch to make it as big and important as possible" ?
If you can't point that, it is fairly evident that you are blindly accusing me 
and thereby blurting nonsense and sparking politics.

> Any not caring at all that you block Steve's work
> as a consequence.

hmm.. accusations again. ATM, Steve was/is prejudiced because of something 

> I asked you for your plans in this thread but I didn't get an answer.

I had mentioned the same earlier (not in this thread), maybe you missed 
those mails or that you like to read selectively.

The basic idea is that STM contributed to many stuff, including comments 
as how things should be done. Maybe you are not aware how you work 
with a vendor for their devices and or when you have taken support from 
them, you need their final approval.

Thus, before anything is done, i need to get a confirmation from STM as 
well. I have asked STM as well, please read the inlined mail.

-------- Original Message --------
Subject: STB0899 driver and mixed results
Date: Mon, 08 Oct 2007 16:35:11 +0400
From: Manu Abraham <abraham.manu at gmail.com>

--- snip ---

The STB0899 driver is finally getting to shape by now.
Currently supported hardware is like this, by the driver 
here: http://jusst.de/hg/multiproto/

Some cleanups etc pending on it.
The entire drivers can be downloaded from this 

URL: http://jusst.de/hg/multiproto/archive/tip.tar.gz

* KNC1 DVB-S2 Plus
* KNC1 DVB-S2 OEM (Also known as Satelco DVB-S2)
* Technotrend TT S2 3200
* Technisat DVB-S2 Skystar HD

The Technisat card, as it seems looks to be the same as 
that of the Technotrend TT S2 3200 card, except that it has 
a STB0899 with version C2L. Now i have a question (well, it's 
a problem that i am facing)

It goes like this

The KNC1 cards (both) and the Technotrend TT S2 3200 cards 
tune quite fine, and LOCK is almost immediate, less than half a 
second (impressive results)

i did make a small change, from the case where it selects between 
MCPC/SCPC config where it uses 2 different clocks, for the MCPC case 
i changed it from 99 MHz to 90 MHz which makes the tuning quite fast 
and a bit more reliable (ie no more LOCK failures on the KNC1 and the 
TT S2 3200 cards)

Now, on the Technisat Skystar HD card, there have been mixed 
results. One person got back stating that performance was real 
pathetic and LOCK 'ing time took minutes and or sometimes no 
LOCK's at all. Another person got back stating that he had 90% 
successful locks with DVB-S and 50% successful locks on DVB-S2 
both cases with the Technisat card.

--- snip ---


> Anyway, I don't know what has been said on irc and I can't
> be bothered to read the irc logs. I really don't care if the DVB-S2
> API is done one way or the other, if you can't cooperate with Steve
> then you have to compete with him. IMHO the first one to have a fully
> working API + driver ready for merging wins. That's what I vote for.

HVR4000 specific S2 API ? You might like to compare specs for the 
CX24116 and the STB0899. ;-)

> The requirements to make it mergable are still the same
> as in Nov. 2005 when the DVB-S2 API was discussed first:
> - don't break backwards compat
> - add complete support for all DVB-S2 features, or at least
>   allow missing features be added later in a backwards compatible way
> - don't be completely ugly (like the Reelbox hack)
> - don't repeat past mistakes and design it to allow easier backwards
>   compatible extensions in the future (like e.g. for DVB-H)

Please do check in the tree whether you still have anything to NACK. If it is 
ok, i will have another round of cleanups.


More information about the linux-dvb mailing list