From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755208AbYINPiS (ORCPT ); Sun, 14 Sep 2008 11:38:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752623AbYINPiI (ORCPT ); Sun, 14 Sep 2008 11:38:08 -0400 Received: from wx-out-0506.google.com ([66.249.82.228]:61790 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751952AbYINPiF (ORCPT ); Sun, 14 Sep 2008 11:38:05 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=vbJajPRWnFmj3mWDmP0MLPMy1X3gI0YFSIT6MyUyGsSb0oPyVJlMmM0/8gkOK93UPV 6m4U4h4fVzNM1QuB6Iy5qt15YJZY3MLBx2G1oyK3SWJVpP00q/jMxuiJDESqm5q/4BcF oIOL4mjzMNXHvAOycucKgipV4bWXG0GeA/HYk= Message-ID: Date: Sun, 14 Sep 2008 17:38:03 +0200 From: "Markus Rechberger" To: "Manu Abraham" Subject: Re: [linux-dvb] Multiproto API/Driver Update Cc: linux-dvb@linuxtv.org, "Rudy Zijlstra" , "Linux Kernel Mailing List" In-Reply-To: <48CC4D35.3000003@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <466109.26020.qm@web46101.mail.sp1.yahoo.com> <48C66829.1010902@grumpydevil.homelinux.org> <48CC42D8.8080806@gmail.com> <48CC4D35.3000003@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 14, 2008 at 1:31 AM, Manu Abraham wrote: > Markus Rechberger wrote: >> On Sun, Sep 14, 2008 at 12:46 AM, Manu Abraham wrote: >>> Markus Rechberger wrote: >>> >>>> How many devices are currently supported by the multiproto API >>>> compared with the s2 tree? >>> The initial set of DVB-S2 multistandard devices supported by the >>> multiproto tree is follows. This is just the stb0899 based dvb-s2 driver >>> alone. There are more additions by 2 more modules (not devices), but for >>> the simple comparison here is the quick list of them, for which some of >>> the manufacturers have shown support in some way. (There has been quite >>> some contributions from the community as well.): >>> >>> (Also to be noted is that, some BSD chaps also have shown interest in >>> the same) >>> >> >> they're heavy into moving the whole framework over as far as I've seen >> yes, also including yet unmerged drivers. > > > Using the same interface, the same applications will work there as well > which is a bonus, but isn't the existing user interface GPL ? (A bit > confused on that aspect) > > >>> * STB0899 based >>> >>> Anubis >>> Typhoon DVB-S2 PCI >>> >>> Azurewave/Twinhan >>> VP-1041 >>> VP-7050 >>> >>> Digital Now >>> AD SP400 >>> AD SB300 >>> >>> KNC1 >>> TV Station DVB-S2 >>> TV Station DVB-S2 Plus >>> >>> Pinnacle >>> PCTV Sat HDTV Pro USB 452e >>> >>> Satelco >>> TV Station DVB-S2 >>> Easywatch HDTV USB CI >>> Easywatch HDTV PCI >>> >>> Technisat >>> Skystar HD >>> Skystar HD2 >>> Skystar USB2 HDCI >>> >>> Technotrend >>> TT S2 3200 >>> TT S2 3600 >>> TT S2 3650 >>> >>> Terratec >>> Cinergy S2 PCI HD >>> Cinergy S2 PCI HDCI >>> >> >> those are pullable now against the current tree? > > > These devices, depend upon the DVB API update without which it wouldn't > work as they depend heavily on the DVB API framework. Without the > updated framework, it doesn't make any sense to pull them: they won't > even compile. The last but not least reason is that, the stb0899 driver > is a DVB-S2 multistandard device which requires DVB-S2/DSS support > additionally. > so the framework is available, and the drivers could be pushed in right afterwards, I wonder who is willing to port those drivers to the other API (including testing). It's not going to happen any time soon I guess, if there's not an agreement with Manu's work. Dumping this code would show another step of ignorance and selfishness against the people who worked on it. Markus