linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Bjoern <lkml@call-home.ch>,
	Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Thomas Kaiser <thomas@kaiser-linux.li>
Subject: Re: ddbridge -- kernel 3.15.6
Date: Wed, 30 Jul 2014 16:00:54 +0300	[thread overview]
Message-ID: <53D8EC86.6020701@iki.fi> (raw)
In-Reply-To: <1406697205.2591.13.camel@bjoern-W35xSTQ-370ST>



On 07/30/2014 08:13 AM, Bjoern wrote:
>> Hello Rudy
>>
>> I use a similar card from Digital Devices with Ubuntu 14.04 and kernel 3.13.0-32-generic. Support for this card was not build into the kernel and I had to compile it myself. I had to use media_build_experimental from Mr. Endriss.
>>
>> http://linuxtv.org/hg/~endriss/media_build_experimental
>>
>> Your card should be supported with this version.
>>
>> Regards, Thomas
>
> Hi Rudy,
>
> What Thomas writes is absolutely correct...
>
> This is unfortunately the worst situation I've ever run across in
> Linux... There was a kernel driver that worked and was supported by
> Digital Devices. Then, from what I read, changes to how the V4L drivers
> have to be written was changed - Digital Devices doesn't like that and
> they force users to use "experimental" builds which are the "old
> style".
>
> This is total rubbish imo - if this is how it was decided that the
> drivers have to be nowadays then adjust them. Why am I paying such a lot
> of money others right, these DD cards are really not cheap?
>
> Some attempts have been made by people active here to adapt the drivers
> and make them work in newer kernels, but so far no one has succeeded.
> Last attempt was in Jan 2014 iirc, since then - silence.
>
> I wish I could help out, I can code but Linux is well just a bit more
> "difficult" I guess ;-)

I have one of such device too, but I have been too busy all the time 
with other drivers...

Basically these DTV drivers should be developed in a order, bridge 
driver first, then demod and tuner - for one single device. After it is 
committed in tree, you could start adding new devices and drivers. If 
you try implement too big bunch of things as a once, you will likely 
fail endless reviews and so.

I don't know what is change in development process which causes these 
problems. What I remember there has been only few big changes in recent 
years, change from Mercurial to Git and reorganization of directories/files.

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2014-07-30 13:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:28 ddbridge -- kernel 3.15.6 Rudy Zijlstra
     [not found] ` <6E594BCC1018445BA338AAABB100405C@ci5fish>
2014-07-18 14:31   ` Rudy Zijlstra
     [not found]     ` <BAE402E8671443828B8815421BDD81CD@ci5fish>
2014-07-18 15:39       ` Rudy Zijlstra
2014-07-18 16:27         ` Rudy Zijlstra
     [not found]           ` <B7F8B540D6D44D08A40DBFA9508FA901@ci5fish>
2014-07-18 21:16             ` Rudy Zijlstra
2014-07-19 17:49 ` Thomas Kaiser
2014-07-30  5:13   ` Bjoern
2014-07-30 13:00     ` Antti Palosaari [this message]
2014-07-30 20:52       ` Antti Palosaari
     [not found]         ` <1406753806.49348.YahooMailNeo@web162403.mail.bf1.yahoo.com>
2014-07-30 21:04           ` Antti Palosaari
2014-07-30 21:06         ` Rudy Zijlstra
     [not found]     ` <21465.62099.786583.416351@morden.metzler>
2014-08-01  4:54       ` Bjoern
2014-08-01  5:08         ` Georgi Chorbadzhiyski
2014-08-01  7:38           ` Thomas Kaiser
2014-08-02 11:02           ` Bjoern
2014-08-02 11:14             ` Bjoern
2014-08-02 15:22             ` Antti Palosaari
2014-08-02 16:35               ` Ralph Metzler
2014-07-30 21:03   ` Rudy Zijlstra
2014-07-31  7:01     ` Thomas Kaiser

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=53D8EC86.6020701@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=lkml@call-home.ch \
    --cc=rudy@grumpydevil.homelinux.org \
    --cc=thomas@kaiser-linux.li \
    /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).