All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 75761] weston-launch no output - black screen
Date: Thu, 10 Apr 2014 23:52:21 +0000	[thread overview]
Message-ID: <bug-75761-8800-eGL1UaHz6u@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75761-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 433 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=75761

--- Comment #19 from Lubosz Sarnecki <lubosz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Reverting the patch on current Linux master
(4a4389abdd9822fdf3cc2ac6ed87eb811fd43acc) fixes the issue for me.

Apperently s->crtc needs to be hardcoded to -1 for the screen not to stay black
when launching weston.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1158 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-04-10 23:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-75761-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-75761-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-04-09  9:29   ` [Bug 75761] weston-launch no output - black screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-09  9:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-09  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 23:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 23:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-04-17 11:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-28 18:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-28 18:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-30  9:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  3:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  8:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  8:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31 11:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31 12:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 10:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 10:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 12:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-10  1:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15  0:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15 18:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 22:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 22:24   ` 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-75761-8800-eGL1UaHz6u@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.