https://bugs.freedesktop.org/show_bug.cgi?id=67051

--- Comment #26 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to comment #25)
> Hi Ilia,
> 
> I was once bisecting left and right.  Not in the past two years or so.
> I can be back in shape relatively easy (I suppose) but it would obviously
> save me
> a lot of time and effort if you can give me some quick, clear and precise
> instructions, including
> 
> 1.  Version to stay on (3.7.10, 3.8.0, 3.10.1 - I have them ready)
> 2.  If on 3.10.1 (my guess), which of the three patches should be on exactly

None of the above, you'll need a git tree. Whenever you see a version like
a.b.c with c != 0, it's not a "clean" version but one that contains backported
patches.

> 3.  How to get a good copy of the tree to work on locally

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

> 4.  How do I get to those commits (say,
> f7960736d0b8647fd149687d15deb79e47122d69)

cd linux
git checkout f7960736d0b8647fd149687d15deb79e47122d69

> 5.  (a) and (b):  what patches (if any)

None. It's a shortcut to the bisect, the two commits are sequential, and my
guess is that that's where things break. If I'm wrong, I'll have you do the
full bisect. Unfortunately both of the commits in (c) and (d) have known
defects, which is what the patches are for. It sounds like those patches are
incomplete, and I need to know which commit has left-over defects.

So basically you need to do

git checkout f7960736d0b8647fd149687d15deb79e47122d69
<build, test, make sure it works>

git checkout a4feaf4ea5359db96a253154eafca358d16152b2
<build, test, make sure it doesn't work>

<apply hdmi-1.patch>
<build, test, make sure it works>

git checkout 8e9e3d2deacc460fbb8a4691140318f6e85e6891
<verify that the hdmi-1.patch is still applied, if not, apply it>
<apply hdminva3.patch>
<build, test, see whether it works or not>

When testing whether things work, please record both whether you see the
correct data in eld, as well as whether sound plays.

-- 
You are receiving this mail because:
You are the assignee for the bug.