From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: Sander Pientka <cumulus0007@gmail.com>,
linux-media@vger.kernel.org,
Douglas Landgraf <dougsland@gmail.com>
Subject: Re: Mercurial x git tree sync - was: Re: Remote control at Zolid Hybrid TV Tuner
Date: Thu, 13 May 2010 15:21:33 -0300 [thread overview]
Message-ID: <4BEC432D.5010501@redhat.com> (raw)
In-Reply-To: <1273772767.3195.21.camel@pc07.localdom.local>
hermann pitton wrote:
>> My view is that the backport tree is very useful to have a broader number
>> of people testing V4L/DVB code, as it can be applied against legacy kernels.
>> Of course, for this to work, people should quickly fix broken backports
>> (that means that not only Douglas should work on it, but other developers
>> are welcomed to contribute with backport fixes).
>
> For now, if not using git, Sander needs a 2.6.33 with recent v4l-dvb
> then to provide relevant debug output and eventually patches.
Until Douglas or someone fix the breakages with older kernels, yes.
> He has to
> check if his distribution has the minimal requirements for that one too.
In thesis, yes, but, unless he is running a really old distribution
(those that come with kernels lower than 2.6.16), it should be ok to
run 2.6.33 on it, provided that properly compiled with the minimum
requirements needed by the distro. Generally, "make oldconfig" do a
good job of enabling the needed bits, but sometimes, manual adjustments
at compilation parameters might be needed.
Well, if the distro is older than 2.6.16, it won't be capable of running
from -hg anyway (as the minimum supported kernel is 2.6.16). So, I don't
think that this would be a problem, in practice.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-05-13 18:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 19:16 Remote control at Zolid Hybrid TV Tuner Sander Pientka
2010-02-17 2:56 ` hermann pitton
[not found] ` <db09c9681002170838tdb15cbbu67cd45a518c11b4b@mail.gmail.com>
[not found] ` <1266445236.7202.17.camel@pc07.localdom.local>
2010-05-08 14:12 ` Sander Pientka
2010-05-12 9:02 ` hermann pitton
2010-05-12 18:59 ` Mauro Carvalho Chehab
2010-05-13 3:28 ` hermann pitton
2010-05-13 4:49 ` Mercurial x git tree sync - was: " Mauro Carvalho Chehab
2010-05-13 7:37 ` hermann pitton
2010-05-13 12:32 ` Mauro Carvalho Chehab
2010-05-13 17:46 ` hermann pitton
2010-05-13 18:21 ` Mauro Carvalho Chehab [this message]
2010-05-13 18:45 ` Mauro Carvalho Chehab
2010-05-14 21:09 ` hermann pitton
2010-05-15 0:52 ` hermann pitton
2010-05-13 20:15 ` Douglas Schilling Landgraf
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=4BEC432D.5010501@redhat.com \
--to=mchehab@redhat.com \
--cc=cumulus0007@gmail.com \
--cc=dougsland@gmail.com \
--cc=hermann-pitton@arcor.de \
--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 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.