From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88501] AMD/ATI RS690M Console blanks to white
Date: Thu, 20 Nov 2014 17:33:21 +0000 [thread overview]
Message-ID: <bug-88501-2300-5eFRLfBgcz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-88501-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=88501
--- Comment #8 from business.kid@gmail.com ---
Yes. I tested in order
1. 3.18.0-rc4 with no patch - white 2nd time.
2. 3.18.0-rc4 with the boot option - dark every time
3. 3.18.0-rc4 with your patch applied and no boot option - white 2nd time
4. 3.18.0-rc4 with a syntax error :-/ module did not load.
5. 3.18.0-rc4 with the attached suggested fix, and no boot option. - dark every
time.
I have built ~ 20 kernels in the last few days, and am not keeping any of them.
The only reason I edited the patch was that I felt it unsafe to put an 'if'
below an 'else' in the same chain bracket. I have met some compilers that don't
respond to that as one would expect. I don't know what gcc does, and can't
swear that the logic follows correctly. I just tried it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-20 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:47 [Bug 88501] New: AMD/ATI RS690M Console blanks to white bugzilla-daemon
2014-11-19 15:51 ` [Bug 88501] " bugzilla-daemon
2014-11-19 16:15 ` bugzilla-daemon
2014-11-19 18:04 ` bugzilla-daemon
2014-11-19 18:17 ` bugzilla-daemon
2014-11-20 9:10 ` bugzilla-daemon
2014-11-20 15:40 ` bugzilla-daemon
2014-11-20 15:52 ` bugzilla-daemon
2014-11-20 17:33 ` bugzilla-daemon [this message]
2015-03-09 22:52 ` bugzilla-daemon
2015-03-10 0:27 ` bugzilla-daemon
2019-03-05 1:10 ` bugzilla-daemon
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-88501-2300-5eFRLfBgcz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.