From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Martin Dauskardt <martin.dauskardt@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: media_build: how can I test older drivers?
Date: Mon, 19 Mar 2012 19:48:10 -0300 [thread overview]
Message-ID: <4F67B7AA.7090000@redhat.com> (raw)
In-Reply-To: <201203191918.42972.martin.dauskardt@gmx.de>
Em 19-03-2012 15:18, Martin Dauskardt escreveu:
> To find the responsible patch for a regression, I need to test older drivers.
> (1, 3 or 6 months ago) How can I do this with media_build?
>
> I don't really understand how the build script works. It seems that it doesn't
> use the current media_tree.git, but loads instead a driver snapshot
> (http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2) which is at
> the moment from March 9.
In a matter of fact, it supports several different modes of work. The default one is
to download a tarball.
If you use:
$ ./build.sh --main-git
it will download a copy of the main tree, and compile using it as a reference.
Yet, bisecting is not trivial. You'll need to run git bisect under the subdir
where the tree was copied. Also, the compilation may fail, due to the backport
patches, that won't be synchronized, especially if you're using an old Kernel that
requires lots of backport patches to compile/work, as the backport patches always
consider the very latest version of the media_tree.
If you want to bisect, it is likely easier to clone the media_tree and bisect on
it directly.
>
> Can I simply change the name of the link for the bz2-package in
> linux/Makefile?
Regards,
Mauro
prev parent reply other threads:[~2012-03-19 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 18:18 media_build: how can I test older drivers? Martin Dauskardt
2012-03-19 22:48 ` Mauro Carvalho Chehab [this message]
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=4F67B7AA.7090000@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=martin.dauskardt@gmx.de \
/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).