All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Krishna Kishore <krishna.kishore@sasken.com>
Cc: Chris Lee <updatelee@gmail.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: stv090x vs stv0900 support
Date: Wed, 24 Jul 2013 20:52:55 +0300	[thread overview]
Message-ID: <51F01477.7050202@iki.fi> (raw)
In-Reply-To: <7CC27E99F1636344B0AC7B73D5BB86DE1485FEE5@exgmbxfz01.sasken.com>

On 07/24/2013 08:21 PM, Krishna Kishore wrote:
> My opinion is that, it is better to have only stv090x. Apart from minimizing the number of patches and ease of maintenance, it will avoid the confusion that I had When I started using prof 7500. I had to enable stv0900 and stb6100. I got confused on whether to enable stv0900 or to enable stv090x.
>
>
>
> -----Original Message-----
> From: linux-media-owner@vger.kernel.org [mailto:linux-media-owner@vger.kernel.org] On Behalf Of Chris Lee
> Sent: Wednesday, July 24, 2013 10:09 PM
> To: linux-media@vger.kernel.org
> Subject: stv090x vs stv0900 support
>
> Im looking for comments on these two modules, they overlap support for the same demods. stv0900 supporting stv0900 and stv090x supporting
> stv0900 and stv0903. Ive flipped a few cards from one to the other and they function fine. In some ways stv090x is better suited. Its a pain supporting two modules that are written differently but do the same thing, a fix in one almost always means it has to be implemented in the other as well.
>
> Im not necessarily suggesting dumping stv0900, but Id like to flip a few cards that I own over to stv090x just to standardize it. The Prof
> 7301 and Prof 7500.
>
> Whats everyones thoughts on this? It will cut the number of patch''s in half when it comes to these demods. Ive got alot more coming lol :)
>
> Chris


stv0900 is better separated from the tuner whilst stv090x has weird 
stv6110x_devctl structure. That's why I used stv0900 for anysee driver. 
I wonder is there something special supported by stv090x because normal 
tuner/demod callbacks are not enough.

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2013-07-24 17:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 16:39 stv090x vs stv0900 support Chris Lee
2013-07-24 17:21 ` Krishna Kishore
2013-07-24 17:52   ` Antti Palosaari [this message]
2013-07-24 21:56     ` Oliver Schinagl
2013-08-16  7:19 ` Mariusz Bialonczyk
2013-08-16 12:50   ` Chris Lee
2013-08-27  7:19     ` Krishna Kishore
2013-08-28 12:35       ` Krishna Kishore
2013-08-29 15:20         ` Krishna Kishore
2013-08-29 15:43           ` Greg KH

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=51F01477.7050202@iki.fi \
    --to=crope@iki.fi \
    --cc=krishna.kishore@sasken.com \
    --cc=linux-media@vger.kernel.org \
    --cc=updatelee@gmail.com \
    /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.