From: "Justin P. Mattock" <justinmattock@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
airlied@redhat.com, alexdeucher@gmail.com
Subject: [BISECTED] commit 619efb1059 makes the MacBookPro2,2 screen flicker like its broken or half plugged in
Date: Tue, 08 Feb 2011 12:52:19 -0800 [thread overview]
Message-ID: <4D51AD03.7030401@gmail.com> (raw)
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.
lspci -vv shows my card info(let me know if you need anymore)
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon
Mobility X1600] (prog-if 00 [VGA controller])
Subsystem: Apple Computer Inc. MacBook Pro
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 256 bytes
Interrupt: pin A routed to IRQ 42
Region 0: Memory at 40000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at 50300000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 50320000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
Justin P. Mattock
next reply other threads:[~2011-02-08 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:52 Justin P. Mattock [this message]
2011-02-08 21:20 ` [BISECTED] commit 619efb1059 makes the MacBookPro2,2 screen flicker like its broken or half plugged in 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
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=4D51AD03.7030401@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;
as well as URLs for NNTP newsgroup(s).