All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Mason <slash.tmp@free.fr>
Cc: linux-media <linux-media@vger.kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: Automatic device driver back-porting with media_build
Date: Thu, 17 Dec 2015 12:08:30 -0200	[thread overview]
Message-ID: <20151217120830.0fc27f01@recife.lan> (raw)
In-Reply-To: <5672BE15.9070006@free.fr>

Em Thu, 17 Dec 2015 14:52:21 +0100
Mason <slash.tmp@free.fr> escreveu:

> Hello Mauro,
> 
> On 17/12/2015 13:55, Mauro Carvalho Chehab wrote:
> 
> > Mason wrote:
> > 
> >> I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here:
> >> http://linuxtv.org/wiki/index.php/TechnoTrend_TT-TVStick_CT2-4400
> >>
> >> According to the article, the device is supported since kernel 3.19
> >> and indeed, if I use a 4.1 kernel, I can pick CONFIG_DVB_USB_DVBSKY
> >> and everything seems to work.
> >>
> >> Unfortunately (for me), I've been asked to make this driver work on
> >> an ancient 3.4 kernel.
> >>
> >> The linuxtv article mentions:
> >>
> >> "Drivers are included in kernel 3.17 (for version 1) and 3.19 (for version 2).
> >> They can be built with media_build for older kernels."
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>
> >> This seems to imply that I can use the media_build framework to
> >> automatically (??) back-port a 3.19 driver to a 3.4 kernel?
> > 
> > "automatically" is a complex word ;)
> 
> If I get it working, I think you can even say "auto-magically" ;-)
> 
> >> This sounds too good to be true...
> >> How far back can I go?
> > 
> > The goal is to allow compilation since 2.6.32, but please notice that
> > not all drivers will go that far. Basically, when the backport seems too
> > complex, we just remove the driver from the list of drivers that are
> > compiled for a given legacy version.
> > 
> > Se the file v4l/versions.txt to double-check if the drivers you need
> > have such restrictions. I suspect that, in the specific case of
> > DVB_USB_DVBSKY, it should compile.
> 
> That is great news.
> 
> > That doesn't mean that it was tested there. We don't test those
> > backports to check against regressions. We only work, at best
> > effort basis, to make them to build. So, use it with your own
> > risk. If you find any problems, feel free to send us patches
> > fixing it.
> 
> My first problem is that compilation fails on the first file ;-)
> See attached log.
> 
> My steps are:
> 
> cd media_build/linux
> make tar DIR=/tmp/sandbox/media_tree
> make untar
> cd ..
> make release DIR=/tmp/sandbox/custom-linux-3.4
> make
> 
> I will investigate and report back.

Then I guess you're not using vanilla 3.4 Kernel, but some heavily
modified version. You're on your own here.

Regards,
Mauro

  reply	other threads:[~2015-12-17 14:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:13 Automatic device driver back-porting with media_build Mason
2015-12-17 12:55 ` Mauro Carvalho Chehab
2015-12-17 13:52   ` Mason
2015-12-17 14:08     ` Mauro Carvalho Chehab [this message]
2015-12-17 14:30       ` Mason
2015-12-17 14:55         ` Mauro Carvalho Chehab
2015-12-17 15:32           ` Mason
2015-12-17 16:09             ` Mauro Carvalho Chehab
2015-12-17 16:48               ` Mason
2015-12-18 10:37                 ` Mauro Carvalho Chehab
2015-12-18 11:01                   ` Mason
2015-12-17 17:03               ` Mason
2015-12-17 17:17                 ` Mason
2015-12-18 10:44                 ` Mason
2015-12-18 11:03                   ` Mauro Carvalho Chehab
2015-12-18 11:22                     ` Mauro Carvalho Chehab
2015-12-18 12:10                       ` Mason
2015-12-18 12:59                         ` Mason
2015-12-18 13:40                           ` Mason
2015-12-18 15:13                             ` Mason
2015-12-18 17:10           ` Mason
2015-12-18 19:42             ` Mason
2015-12-28 10:44   ` Mason
2015-12-28 12:21     ` Mason
2015-12-28 13:02       ` 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=20151217120830.0fc27f01@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=slash.tmp@free.fr \
    /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.