From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp27.orange.fr ([80.12.242.96]) by www.linuxtv.org with esmtp (Exim 4.63) (envelope-from ) id 1KiiWf-0004ah-Mx for linux-dvb@linuxtv.org; Thu, 25 Sep 2008 06:32:52 +0200 From: Christophe Thommeret To: Manu Abraham Date: Thu, 25 Sep 2008 06:31:50 +0200 References: <4724.24.120.242.223.1222313000.squirrel@webmail.xs4all.nl> <200809250604.44125.hftom@free.fr> <48DB0FDA.1000702@gmail.com> In-Reply-To: <48DB0FDA.1000702@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200809250631.50462.hftom@free.fr> Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] [ANNOUNCE] DVB API improvements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: Le Thursday 25 September 2008 06:13:14 Manu Abraham, vous avez =E9crit=A0: > Christophe Thommeret wrote: > > Le Thursday 25 September 2008 05:57:18 Manu Abraham, vous avez =E9crit : > >> Hans Verkuil wrote: > >>> Just work with Steve to convert the current devices in the multiproto > >>> tree to use this API. If there is anything missing kick Steve and he'= ll > >>> have to add whatever is needed. That's *his* responsibility and he > >>> accepted that during the discussions. > >> > >> With the multiproto tree, you _don't_need_ to convert any devices to u= se > >> the new infrastructure, whereas with S2API you need to do that. This is > >> a major drawback. In the multiproto tree, all devices work just without > >> any conversion of any kind, also it is completely backward compatible. > >> > >> The aspect of backward compatibility and drivers not getting converted > >> had been a major issue, when the original DVB-S2 discussions came up. > >> This had been a design goal for the multiproto tree. > > Please do not trim CC's. > > > I'm not sure to get you Manu. > > Do you mean that existing drivers have to be "converted" to work with > > s2api ? > > Yes, one of the existing drivers had to be converted. eg: CinergyT2 Ok, the cinergyT2 was indeed out of dvb-core, but a dvb-core driver already = exists, so no problem :) > Also, the stb0899 driver (from the multiproto tree) also needs to be > converted, as far as anyone who is able to see, or from the posts > themselves. Of course :) But this is not what i call an "existing" (in kernel) driver. > The CX24116 is already existing in the multiproto tree, from Steven > himself. I did not pull this driver into the tree that i used for > testing because of all those mails Steven wrote: just wanted to stay > clear of it. But somebody else is having the same tree. Eventhough many > people had asked me to pull that driver in, because of all those mails, > i just stood clear of it. > > You can read it from the public archives here on the same. I know the story Manu. But 2 years to get a new API is really too much. And during these 2 years, = 2 = different trees for 2 differents drivers was totally insane. We (applicatio= ns = devs) are always making our best to bring DVB to users as easily as possibl= e. = And trust me, the multiproto story has complicated users life A LOT. This must NEVER happen again. -- = Christophe Thommeret _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb