From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp-vbr9.xs4all.nl ([194.109.24.29]) by www.linuxtv.org with esmtp (Exim 4.63) (envelope-from ) id 1Kd25M-0008S3-HS for linux-dvb@linuxtv.org; Tue, 09 Sep 2008 14:12:45 +0200 Message-ID: <48C66829.1010902@grumpydevil.homelinux.org> Date: Tue, 09 Sep 2008 14:12:25 +0200 From: Rudy Zijlstra MIME-Version: 1.0 To: free_beer_for_all@yahoo.com References: <466109.26020.qm@web46101.mail.sp1.yahoo.com> In-Reply-To: <466109.26020.qm@web46101.mail.sp1.yahoo.com> Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Multiproto API/Driver Update List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: barry bouwsma wrote: > --- On Tue, 9/9/08, hermann pitton wrote: > > >> following your thoughts, you are likely right. DVB-T2 likely indicates >> that you need new hardware, like it is for sure on DVB-S2. >> > > Servus, > > Disclaimer: I'm only an outsider, not a programmer, and not > familiar with the digital broadcast specs or the DVB API, so > I will both not know what I'm talking about, and be asking > stupid questions. > > > I decided to look again at DVB-T2, as it's likely to be the > next change that will be in need of Linux support in a year > or so, at least in the UK, when hardware becomes available. > Likely true, DVB-T2 is well on the way in development. > My stupid question is, will DVB-T2, in Transport Stream mode, > be similar enough to existing DVB-T, apart from the extended > modulation parameters, that it can be fit into the existing > API, or am I overlooking something in my ignorance of the API? > TS is unchanged from DVB-T, simply higher capacity. The changes are in the modulation (and additional table entries) > This seems to me somewhat like the case of existing DVB-C, > where some hardware is incapable of 256QAM and so cannot tune > all the carriers, but I really haven't tried to understand > the API or how it can be extended without breaking things... > That is old... QAM256 is pretty standard now. Only rather old HW should be incapable of handling QAM-256. > > In looking at the Wikipedia article on DVB-T, it appears that > at least the following diffs to include/dvb/frontend.h might > be needed to support the additional possibilities that a DVB-T2 > tuner would be likely to support -- diff against the S2API, as > this file is unchanged in multiproto, while S2API already has > > the additional FEC values present... > From my understanding, S2API is a generic approach, and should not have troubles supporting these standards. > goto Disclaimer; > > DVB-C2, i do not expect to get beyond definition stage, as - unless someone is really willing to pay for it - it seems unlikely there will be a market for it. Too many significantly cheaper solutions to solve the problem on cable. Cheers, Rudy _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb