linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Marx <acc.for.news@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: pctv452e
Date: Wed, 04 Jul 2012 02:04:35 +0300	[thread overview]
Message-ID: <4FF37A83.2030707@iki.fi> (raw)
In-Reply-To: <oikac9-mbk.ln1@wuwek.kopernik.gliwice.pl>

On 07/03/2012 10:46 AM, Marx wrote:
> On 02.07.2012 18:33, Steve Hill wrote:
>> Can anyone give me any pointers that might help? I've searched and
>> searched and all I can see if people saying that it won't work since the
>> DVB-S2 code was integrated into the kernel tree, but I've not seen
>> anyone try to figure out _why_ it won't work.
>
> I'm on the same boat.
> I have 3 DVB-S2 cards, one of them is pctv452e, and none of them works
> reliable. Yes, it's very frustrating that card which claims linux
> support has this support broken. The problem is that community which
> uses DVB cards is much smaller then those using other equipment. So
> there are no test of every device in each kernel release.
> I'm reading this list for some time and often see patches which refactor
> some drivers, but the only check is compilation check.
> "totally rewritten DVB-USB-framework" will not help to have more drivers
> too. Makers of dvb cards often don't provide linux driver, or provide
> only once in form of patches. You will not apply such patch into new DVB
> stack. Makers must constantly refactor their drivers to suit new
> kernels, and there are only a few which do this. I don't know why they
> simply don't join this list and push drivers into kernel and then
> provide support.
> I don't know what's future of DVB stack, but I see that changes in DVB
> stack causes meany problems with drivers. Often driver is written once
> and later unsupported - changes make it non-functional and there is
> nobody who can fix it. Exactly like with pctv452e driver.

Your claims about my DVB-USB-framework work is quite bullshit. I am not 
going to convert all drivers to the new framework just doing compile 
tests. I am heavily aware it is too risky thus I implemented it as a 
alternative, converting drivers one by one when you have hardware in 
hands to test. If such big changes were made to the existing code surely 
there is breakages.

And it fixes some existing DVB-USB bugs, actually all I was aware. Also 
it removes all the hacks, and also bugs coming those hacks, from many 
drivers. Most notable complex AF9015 and AF9035. See AF9015 before 
change and after change - code size is reduced something like 25% and 
binary size too.

> Marx
>
> Ps. Steve, could you please give me full version of kernel which works
> with pctv452e?

As the new DVB-USB fixes many bugs I ask you to test it. I converted 
pctv452e driver for you:
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

Only PCTV device supported currently, not TechnoTrend at that time.


regards
Antti

-- 
http://palosaari.fi/



  reply	other threads:[~2012-07-03 23:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 16:33 pctv452e Steve Hill
2012-07-03  7:46 ` pctv452e Marx
2012-07-03 23:04   ` Antti Palosaari [this message]
2012-07-04  7:51     ` pctv452e Marx
2013-07-06 13:29 ` pctv452e Antti Palosaari
  -- strict thread matches above, loose matches on Subject: below --
2012-07-04 16:04 pctv452e Steve Hill
2012-07-04 16:22 ` pctv452e Antti Palosaari
2012-07-04 18:46   ` pctv452e Marx
2012-07-04 18:53   ` pctv452e André Weidemann
2012-07-04 19:01     ` pctv452e Antti Palosaari
2012-07-05 13:14       ` pctv452e Marx
2012-07-05 14:23         ` pctv452e Antti Palosaari
2012-07-06  6:13           ` pctv452e Marx
2012-07-06  9:34             ` pctv452e Antti Palosaari
2012-07-06 11:04               ` pctv452e Marx
2012-07-06 18:24                 ` pctv452e Antti Palosaari
2012-07-06 22:23                 ` pctv452e Marx
2012-07-07  0:00                   ` pctv452e Antti Palosaari
2012-07-07 23:07                     ` pctv452e Marx
2012-07-08 12:32                       ` pctv452e Antti Palosaari
2012-07-09  6:24                         ` pctv452e Marx
2012-07-09  8:42                           ` pctv452e Antti Palosaari
2012-07-09 16:44                             ` pctv452e Marx
2012-07-09 17:38                               ` pctv452e Antti Palosaari
2012-07-09 17:46                                 ` pctv452e Antti Palosaari
2012-07-10  6:39                                   ` pctv452e Marx
2012-07-10  9:33                                     ` pctv452e Antti Palosaari
2012-07-10 21:08                                       ` pctv452e Marx
2012-07-10 23:13                                         ` pctv452e Antti Palosaari
2012-07-11  6:25                                           ` pctv452e Marx
2012-07-11 10:00                                             ` pctv452e Antti Palosaari
2012-07-09 18:21                               ` pctv452e poma
2012-07-10  6:43                                 ` pctv452e Marx
2012-07-10 15:51                                   ` pctv452e poma
2012-07-10 15:58                                     ` pctv452e Devin Heitmueller
2012-07-10 22:54                                       ` pctv452e poma
2012-08-03 16:56   ` pctv452e Steve Hill

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=4FF37A83.2030707@iki.fi \
    --to=crope@iki.fi \
    --cc=acc.for.news@gmail.com \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).