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: Sun, 13 Feb 2011 17:14:35 -0800 [thread overview]
Message-ID: <705ECE04-641E-4C3A-B3D3-B5D512AA98CF@gmail.com> (raw)
In-Reply-To: <AANLkTikrZZ6i6di-c0zBav0zT5OOvmOXvX7SAXTW18z+@mail.gmail.com>
On Feb 13, 2011, at 3:46 PM, Alex Deucher wrote:
> On Sun, Feb 13, 2011 at 12:28 AM, Justin Mattock
> <justinmattock@gmail.com> wrote:
>>
>> On Feb 11, 2011, at 5:15 PM, Alex Deucher wrote:
>>
>>> On Fri, Feb 11, 2011 at 10:57 AM, Justin Mattock
>>> <justinmattock@gmail.com> wrote:
>>>>
>>>>>
>>>>> Better yet, can you try the attached patch on top of 2.6.38-rc4 or
>>>>> newer?
>>>>>
>>>>> Alex
>>>>>
>>>>
>>>> o.k. applied that patch... unfortunately Im seeing the flickering
>>>> screen
>>>> and
>>>> the crud shows up..
>>>> initially during boot everything looked fine, its when I
>>>> suspended the
>>>> machine, upon wake-up
>>>> the flickering occurred.
>>>> kernel version is the current: 2.6.38-rc4-00107-gaa502b4
>>>
>>> Can you try this patch? Try uncommenting the following lines to see
>>> if either of those flags work any better. Try them individually and
>>> together if possible and report back which, if any, helps.
>>>
>>> /*pll->flags |= RADEON_PLL_PREFER_MINM_OVER_MAXP;*/
>>>
>>> /*if (ASIC_IS_AVIVO(rdev))
>>> pll->flags |= RADEON_PLL_USE_FRAC_FB_DIV;*/
>>>
>>> Thanks!
>>>
>>> Alex
>>>
>>>>
>>>> Justin P. Mattock
>>>>
>>> <0001-drm-radeon-kms-hopefully-fix-pll-issues-for-real-v2.patch>
>>
>>
>> alright.. again out of my office trying to make a living!!
>> Anyways I applied the two earlier patches, and added the previous
>> post's
>> patch as well
>> (everything runs o.k. s2r etc...)
>> I can try for the above and see if I can pinpoint the piece of code
>> that is
>> causing this(hopefully)
>
> The attached patch is what I'm proposing to go upstream. Please test
> and let me know if it works ok for you.
>
> Alex
alright... bisect done, but something went wrong(must redu later)..
Anyways with your patch applied
everything looks good
Justin P. Mattock
prev parent reply other threads:[~2011-02-14 1:14 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
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 [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=705ECE04-641E-4C3A-B3D3-B5D512AA98CF@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®