Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764982AbXIMQdf (ORCPT ); Thu, 13 Sep 2007 12:33:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752334AbXIMQd0 (ORCPT ); Thu, 13 Sep 2007 12:33:26 -0400 Received: from rv-out-0910.google.com ([209.85.198.184]:58704 "EHLO rv-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392AbXIMQdZ (ORCPT ); Thu, 13 Sep 2007 12:33:25 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=twYSHVn6pdSrh83iwsaw+rSG9d6B+UgftQWmSExk4Z1cQIuY1exdvNJ8fG3+InqVATTgbHkqhSbthOevGtRBvZqh2HYMvkCGksl+XWGHQ1UOtcIiXTJaTLmvccQ33EAZbattL8wdZNudPKY76/4aDtVtuLXbt74WVlFsisKfwiQ= Message-ID: Date: Thu, 13 Sep 2007 18:32:57 +0200 From: "Markus Rechberger" To: "Manu Abraham" Subject: Re: [linux-dvb] [PATCH] Userspace tuner Cc: "Johannes Stezenbach" , linux-kernel@vger.kernel.org, video4linux-list@redhat.com, "linux-dvb@linuxtv.org" , akpm@linux-foundation.org In-Reply-To: <46E963CC.8010707@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46C1BCC5.9090709@amd.com> <1189626560.5160.57.camel@gaivota> <20070913131353.GB26972@linuxtv.org> <46E95C54.4060502@gmail.com> <46E963CC.8010707@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1546 Lines: 36 On 9/13/07, Manu Abraham wrote: > Markus Rechberger wrote: > > On 9/13/07, Manu Abraham wrote: > >>> It's only a step in development, I do not intend to keep the kernel > >>> stub in the end, but I do intend to keep and use the userspace drivers > >>> with i2c-dev in the long run, this requires a v4l/dvb library at the > front > >>> of everything. > >> Well, this was what adq and myself did with libdvbapi and mti, (much > >> before UIO was announced at LK.) It is not tied to I2C either. > >> > > > > I2C is the main communication path for it, although there are callback > > mechanisms available which add the possibility for different configuration > > paths. > > Sorry, i must say that what you said is wrong. > > The example implementation in libdvbapi/mti is I2C only with a STV0299 > on the TTPCI, if that was what you meant. > But if you need examples for every possible interface, then probably you > are out of luck. > I didn't comment the libdvbapi/mti driver. I'm quite confident that non I2C protocols can be handled by a callback function. In the end it's either a usb control command or pci mmio writes in the current usual cases and such calls could be handled behind a callback function which is implemented in the driver. Markus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/