Subject: Re: DVB at76c651.c driver seems to be dead code
From: Andreas Oberritter <obi@linuxtv.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Mws <mws@twisted-brains.org>, linux-dvb-maintainer@linuxtv.org,
       linux-kernel@vger.kernel.org
In-Reply-To: <20050211094934.GO2958@stusta.de>
References: <20050210235605.GN2958@stusta.de>
	 <200502110211.29055.mws@twisted-brains.org>
	 <20050211094934.GO2958@stusta.de>
Content-Type: text/plain
Date: Fri, 11 Feb 2005 13:23:24 +0100
Message-Id: <1108124605.3535.17.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1237
Lines: 31

On Fri, 2005-02-11 at 10:49 +0100, Adrian Bunk wrote:
> If I understand it correctly, there are several drivers that only make 
> sense if they are used together. at76c651.c alone makes zero sense?
> This means it would be highly appreciated to have all parts inside the 
> kernel at some time in the future.

It makes sense if
- the dbox2 core code gets merged into mainline, which is our goal, but
  can take a huge amount of time.
- someone rips off the frontend module of a dbox2 and puts it on his
  PCI DVB card because this Atmel chip rocks so much :-)
  It will require only very few changes to the PCI driver...
- or a company decides to use this chip on their brand new DVB-C device
  and john doe decides to write a Linux driver for it. He will then
  notice that there is already a driver for the frontend module and can
  therefore save a lot of work.

> Something different:
> The atmel at76c651 frontend driver is specific to the MPC823 
> architecture?

no.

Regards,
Andreas

-
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/