From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46862 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752542Ab1KNSnD (ORCPT ); Mon, 14 Nov 2011 13:43:03 -0500 Message-ID: <4EC16133.8090300@redhat.com> Date: Mon, 14 Nov 2011 16:42:59 -0200 From: Mauro Carvalho Chehab MIME-Version: 1.0 To: Manu Abraham CC: linux-media@vger.kernel.org Subject: Re: PATCH: Query DVB frontend capabilities References: <4EBBE336.8050501@linuxtv.org> <4EBC402E.20208@redhat.com> <4EBD6B61.7020605@redhat.com> <4EBFC6F3.50404@redhat.com> <4EC0FFCA.6060006@redhat.com> <4EC1445C.4030503@redhat.com> <4EC1590E.8040302@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Em 14-11-2011 16:30, Manu Abraham escreveu: > On Mon, Nov 14, 2011 at 11:38 PM, Mauro Carvalho Chehab > wrote: >> Yet, this doesn't require any changes at DVB API, as all that the demodulator >> need to know is the sub-carrier parameters (frequency, roll-off, symbol >> rate, etc). > > You do: this is why there were changes to the V3 API to accomodate > DVB-S2, which eventually became V5. The major change that underwent is > the addition of newer modulations. The demodulator need to be > explicitly told of the modulation. With some demodulators, the > modulation order could be detected from the PL signaling, rather than > the user space application telling it. DVB-S2 doesn't require DVB bandwidth to be specified. Regards, Mauro