From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 58556] MacBook Pro 5, 1 with nVidia 9400m and 9600m, scrambled screen
Date: Sat, 08 Mar 2014 23:39:11 +0000 [thread overview]
Message-ID: <bug-58556-8800-WdVZa72J2O@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58556-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 923 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58556
--- Comment #26 from Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> ---
Hi Joanand,
Shouldn't the patch for driver/gpu/drm/nouveau/core/subdev/bar/nv50.c rather be
+ line 233: int ret, i;
+ line 351: for(i = 0; i < 8; i++)
+ line 352: nv_wr32(priv, 0x001900 + (i * 4), 0x00000000);
By the way, on top of which commit/kernel are you applying the patch?
Yeah, if you try with acceleration you end up with bug 27501
(https://bugs.freedesktop.org/show_bug.cgi?id=27501).
EFIFB should not be the problem: it is removed by nouveau at some point, to be
replaced by nouveaufb, which seems to be not rightly configured (or the
accesses to it), bringing screen corruption.
I have a 5,3 (iirc) MacBook Pro (mid 2009) 15.6", with the same graphic cards,
resolution is also 1440x900.
Pierre
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2033 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-03-08 23:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 7:23 [Bug 58556] New: MacBook Pro 5, 1 with nVidia 9400m and 9600m, scrambled screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-58556-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-01 18:31 ` [Bug 58556] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-17 21:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 22:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 11:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 13:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 13:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 17:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 22:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-25 17:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-06 13:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 13:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22 19:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 17:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 21:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-13 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03 22:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 20:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-09 11:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05 13:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-07 8:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-07 23:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-08 21:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-08 23:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-03-09 10:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-09 20:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-24 6:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-58556-8800-WdVZa72J2O@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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