From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 102528] Display messed up shortly after boot on laptop with GT218M
Date: Sun, 03 Sep 2017 18:46:45 +0000 [thread overview]
Message-ID: <bug-102528-8800-RvPgPjiJPV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102528-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 603 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102528
--- Comment #4 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Oh, and btw, additional GT21x issues exist. One is fixed in drm-next:
https://github.com/skeggsb/linux/commit/715e7d261dea75911c4dad468a1103168933d913
https://github.com/skeggsb/linux/commit/6b1277c837630749b55f743dd62023d9dd7a510a
But there's some stuff that remains in devinit, where certain things are
accessed before they're supposed to. Or something along those lines.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1567 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-09-03 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 14:18 [Bug 102528] New: Display messed up shortly after boot on laptop with GT218M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-102528-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-09-03 14:20 ` [Bug 102528] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 14:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 15:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-03 18:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-09-29 17:44 ` 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-102528-8800-RvPgPjiJPV@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.