From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 29384] Slow switch between TTY1-TTY6 with /dev/fb0 or X11
involved
Date: Tue, 3 Aug 2010 11:56:42 -0700 (PDT)
Message-ID: <20100803185642.EEBFD130108@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 29E0F9ED84
for ;
Tue, 3 Aug 2010 11:56:43 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=29384
--- Comment #10 from Alex Deucher 2010-08-03 11:56:42 PDT ---
(In reply to comment #9)
> I am awfully sorry, but I am not familiar with git/git-bitsect.
> Of course I will try every patch you can over and give you as much as possible
> details about the effect.
It's very easy. Assuming you have a git tree checked out:
git bisect start
git bisect good v2.6.34
git bisect bad v2.6.35
After that git will walk you through the rest. It will check out the
appropriate commit, at which point you can compile it, test it, and if it's
good, run:
git bisect good
and if it's bad:
git bisect bad
and git will select the next commit and the process continues. If there is a
commit that doesn't boot or build, you can skip it with:
git bisect skip
See this page for more info:
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.