From: "Alfredo Jesús Delaiti" <alfredodelaiti@netscape.net>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: mb86a20s and cx23885
Date: Wed, 17 Jul 2013 10:54:19 -0300 [thread overview]
Message-ID: <51E6A20B.8020507@netscape.net> (raw)
In-Reply-To: <20130716053030.3fda034e.mchehab@infradead.org>
Hi all
El 15/07/13 17:30, Mauro Carvalho Chehab escribió:
> Em Mon, 15 Jul 2013 16:30:18 -0300
> Alfredo Jesús Delaiti <alfredodelaiti@netscape.net> escreveu:
>
>> Hi all
>>
>> After some time trying to see what the problem is, I have found it is
>> not come the RF signal.
>>
>> I've gone back using a 3.2 kernel, after doing a couple of tests, the
>> board works :-)
>> When I try to apply these changes to a 3.4 or later kernel does not tune
>> plate.
>>
>> Between 3.2 and 3.4 kernel there are several changes to the drivers:
>> CX23885, xc5000 and mb86a20s. I tried to cancel several of them on a 3.4
>> kernel, but I can not make the card tune.
> If you know already that the breakage happened between 3.2 and 3.4, the better
> is to use git bisect to discover what patch broke it.
Mauro Thanks for the suggestion.
This weekend I have some time and I'll study how to implement it.
I guess it's do something similar to:
~ $ git clone git://linuxtv.org/media_build.git
~ $ cd media_build
~/media_build $./build --main-git
~/media_build $ cd media
~/media $ gedit drivers/media/video/foo.c
~/media $ make -C ../v4l
~/media $ make -C ../ install
~/media $ make -C .. rmmod
~/media $ modprobe foo
>
> You can do (using Linus git tree):
>
> git checkout v3.4
> git bisect bad
> git checkout good v3.2
Where is the git tree of Linus in <git://git.kernel.org/> or
<git://linuxtv.org/>?
Thanks again,
Alfredo
>
> git bisect will then do a binary search between those two kernels. All you
> have to do is to recompile the Kernel and test it. Then you'll tag the
> changeset as "bad" or "good", until the end of the search. In general, you'll
> discover the changeset responsible for the breakage after a few (8-10)
> interactions.
>
> For more reference, you can take a look, for example, at:
> http://git-scm.com/book/en/Git-Tools-Debugging-with-Git
>
> Regards,
> Mauro
>
> PS.: Someone should fix our wiki, as it is still pointing to hg bisect,
> instead of pointing to git bisect.
>
>> The changes I have applied to kernel 3.2 are:
>
next prev parent reply other threads:[~2013-07-17 14:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51054759.7050202@netscape.net>
2013-01-27 16:16 ` mb86a20s and cx23885 Mauro Carvalho Chehab
2013-01-27 21:48 ` Alfredo Jesús Delaiti
2013-01-27 21:52 ` Fwd: " Alfredo Jesús Delaiti
2013-01-28 10:23 ` Mauro Carvalho Chehab
2013-01-28 20:47 ` Alfredo Jesús Delaiti
2013-02-06 14:12 ` Alfredo Jesús Delaiti
2013-03-03 14:50 ` Alfredo Jesús Delaiti
2013-03-03 16:15 ` Mauro Carvalho Chehab
2013-03-04 23:09 ` Alfredo Jesús Delaiti
2013-03-03 16:40 ` Mauro Carvalho Chehab
2013-03-04 19:42 ` Mauro Carvalho Chehab
2013-03-05 0:00 ` Alfredo Jesús Delaiti
2013-03-05 2:30 ` Mauro Carvalho Chehab
2013-03-08 22:42 ` Alfredo Jesús Delaiti
2013-04-01 22:41 ` Alfredo Jesús Delaiti
2013-07-15 19:30 ` Alfredo Jesús Delaiti
2013-07-15 20:30 ` Mauro Carvalho Chehab
2013-07-17 13:54 ` Alfredo Jesús Delaiti [this message]
2013-07-17 19:23 ` Mauro Carvalho Chehab
2013-07-19 3:38 ` Alfredo Jesús Delaiti
2013-07-21 13:50 ` Alfredo Jesús Delaiti
2013-07-23 20:58 ` Alfredo Jesús Delaiti
2013-07-23 21:46 ` Alfredo Jesús Delaiti
2013-07-27 17:55 ` Alfredo Jesús Delaiti
[not found] ` <20130801090436.6dfa0f68@infradead.org>
2013-08-01 17:16 ` Alfredo Jesús Delaiti
2013-08-01 17:37 ` Mauro Carvalho Chehab
2013-08-01 18:09 ` Alfredo Jesús Delaiti
2013-08-01 18:48 ` Mauro Carvalho Chehab
2013-08-02 3:18 ` Alfredo Jesús Delaiti
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=51E6A20B.8020507@netscape.net \
--to=alfredodelaiti@netscape.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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 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).