All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Auer <vdr@helmutauer.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l-dvb - Is it still usable for a distribution ?
Date: Mon, 07 Jun 2010 23:33:26 +0200	[thread overview]
Message-ID: <4C0D65A6.5050502@helmutauer.de> (raw)
In-Reply-To: <4C0CF124.4010103@redhat.com>

Hello

>> Now with kernel 2.6.34 this doesn't work anymore, because v4l-dvb doesn't compile.
> 
> Douglas returned from this 2 week trip abroad and he is backporting the upstream stuff. Yesterday, he
> reported to me that the tree is now compiling with 2.6.34.
> 
Ok - I also got it compiling, but budget-ci is causing kernel oops (see other ML thread)
> 
>> The final question for me:
>> Does it make any sense anymore to stay with v4l-dvb or do I have to change to the kernel drivers ?
>> The major disadvantage of the kernel drivers is the fact that I cannot switch to newer dvb drivers, I am stuck to the ones included in the kernel.
> 
> Well, this is something that you need to answer by yourself ;)
> 
Thats not what I wanted to hear ;)

> I don't recommend using a random snapshot of the tree on a distro package, as regressions may
> happen during the development period.
> 
> Also, the backports are done at best efforts. There are no warranties, no QA and generally no 
> tests with real hardware when a backport is done. So, while we hope that the backport will work, 
> you may have a bug introduced on the backport stuff that may affect your card, not present
> upstream.
> 
> IMHO, the better is to just upgrade to the next stable kernel. 
> 
Ok -  that what I also thought
formerly v4l-dvb was the bleeding edge and the kernel draivers were about 2 Versions behind.
Now the kernel drivers are often the newer ones, so I have to switch.

> Another alternative is to manually apply on your distro the patches that you need there.
> All patches with c/c to stable@kernel.org are bug fixes that needs to be backported to older
> (stable) kernels. So, a good hint is to check for those stable patches. Unfortunately, not all
> developers remind to add a c/c to stable. I try to do my best to re-tag those emails when
> sending the patches upstream, but I generally opt to trust on the developers, since a fix may
> apply only at the latest upstream kernel.
> 
Thats surely an option, but an average user of my distri can't compile a kernel ;)
Emerging v4l-dvb is much easier ;)

-- 
Helmut Auer, helmut@helmutauer.de

  parent reply	other threads:[~2010-06-07 21:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 11:27 v4l-dvb - Is it still usable for a distribution ? vdr
2010-06-07 13:16 ` Mauro Carvalho Chehab
2010-06-07 13:49   ` Jarod Wilson
2010-06-07 21:25     ` Helmut Auer
2010-06-08  3:40       ` Jarod Wilson
2010-06-08  4:25         ` Helmut Auer
2010-06-08  8:56         ` vdr
2010-06-08 14:50           ` Mauro Carvalho Chehab
2010-06-07 21:33   ` Helmut Auer [this message]
2010-06-07 22:08     ` Mauro Carvalho Chehab

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=4C0D65A6.5050502@helmutauer.de \
    --to=vdr@helmutauer.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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.