From: Justin Mattock <justinmattock@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
airlied@redhat.com
Subject: Re: [BISECTED] commit 619efb1059 makes the MacBookPro2,2 screen flicker like its broken or half plugged in
Date: Wed, 9 Feb 2011 21:33:27 -0800 [thread overview]
Message-ID: <B44733BE-E28B-441E-9E6B-AE9B0C8D7E45@gmail.com> (raw)
In-Reply-To: <AANLkTimBwM=iacwPosrYXU_jN=DXnEkWL3jvFcarDN23@mail.gmail.com>
On Feb 9, 2011, at 2:09 PM, Alex Deucher wrote:
> On Tue, Feb 8, 2011 at 4:20 PM, Alex Deucher <alexdeucher@gmail.com>
> wrote:
>> On Tue, Feb 8, 2011 at 3:52 PM, Justin P. Mattock
>> <justinmattock@gmail.com> wrote:
>>> With the current HEAD Im getting screen flickering really bad to
>>> point where
>>> it looks like the screen is damaged and/or half plugged-in etc..
>>>
>>> the bisect pointed to here:
>>>
>>> commit 619efb105924d8cafa0c1dd9389e9ab506f5425d
>>>
>>> doing a git revert 619efb10592
>>> gets the screen working properly again.
>>> I havent looked much through the code to see if I can fix this.
>>> for the time
>>> being I'll revert this on my machine with the current, until later
>>> on.
>>
>> The attached patch should fix it assuming I got your pci ids correct.
>> I'm done with the pll stuff; too may fixes break other boards. Just
>> add a quirk table and be done with it.
>>
>
> The attached patch builds on the previous one and fixes an additional
> regression.
>
> Alex
>
> <0001-drm-radeon-kms-pll-quirk-cleanup.patch>
alright... didn't mean to keep you waiting(out of my office for most
of the day)..
Anyways patch applied, and everything looks good no screen jitters or
flickering etc..
Reported-and-Tested-by: Justin P. Mattock<justinmattock@gmail.com>
Thanks for sending this my way so my machine works..
cheers,
Justin P. Mattock
next prev parent reply other threads:[~2011-02-10 5:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:52 Justin P. Mattock
2011-02-08 21:20 ` Alex Deucher
2011-02-08 21:48 ` Justin Mattock
2011-02-09 22:09 ` Alex Deucher
2011-02-10 5:33 ` Justin Mattock [this message]
2011-02-11 6:59 ` Alex Deucher
2011-02-11 8:27 ` Alex Deucher
2011-02-11 15:57 ` Justin Mattock
2011-02-11 19:06 ` Alex Deucher
2011-02-12 1:15 ` Alex Deucher
2011-02-13 5:28 ` Justin Mattock
2011-02-13 23:46 ` Alex Deucher
2011-02-14 0:02 ` Justin Mattock
2011-02-14 1:14 ` Justin Mattock
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=B44733BE-E28B-441E-9E6B-AE9B0C8D7E45@gmail.com \
--to=justinmattock@gmail.com \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®