All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: DVB at76c651.c driver seems to be dead code
Date: Fri, 11 Feb 2005 13:23:24 +0100	[thread overview]
Message-ID: <1108124605.3535.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20050211094934.GO2958@stusta.de>

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


  reply	other threads:[~2005-02-11 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 23:56 DVB at76c651.c driver seems to be dead code Adrian Bunk
2005-02-11  1:11 ` Mws
2005-02-11  9:49   ` Adrian Bunk
2005-02-11 12:23     ` Andreas Oberritter [this message]
2005-02-11  9:36 ` [linux-dvb-maintainer] " Holger Waechtler
2005-02-11 12:11   ` Andreas Oberritter
2006-01-06  0:35     ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1108124605.3535.17.camel@localhost.localdomain \
    --to=obi@linuxtv.org \
    --cc=bunk@stusta.de \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mws@twisted-brains.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.