From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194761] amdgpu driver breaks on Oland (SI)
Date: Fri, 20 Oct 2017 14:26:37 +0000 [thread overview]
Message-ID: <bug-194761-2300-YBjHTtCztC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194761
yousifjkadom@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yousifjkadom@yahoo.com
--- Comment #87 from yousifjkadom@yahoo.com ---
Hi. I have Lenovo ThinkPad e550 with 2 VGA:
1) shared: Intel Corporate HD 5500
2) dedicated VGA, Radeon R7 M265 2GB
I'm using Fedora 26 X64 bit on this laptop.
Currently, Linux kernel support Radeon R7 M265 (which is South Island), BUT
DISABLED BY DEFAULT BECAUSE THIS SUPPORT IS EXPERIMENTAL. So, currently, user
should use customized kernel to enable such support which beyond many users
like me .... Kindly, see this link:
https://forums.fedoraforum.org/showthread.php?t=315139
I asked in Fedora forum about this & they inform me that this bug (that you
kindly fixed it) is a blocker against enable kernel support for my Radeon VGA
by default.
I read that it is planned to enable kernel support by default in kernel 4.15.x
But, now I see that you kindly fixed this bug at kernel version 4.14.x !
Please is fixing this bug mean that kernel support for my Radeon R7 M265
dedicated VGA will be enabled by default or it will deferred till kernel 4.15.x
Best.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-20 14:26 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 8:57 [Bug 194761] New: amdgpu driver breaks on Oland (SI) bugzilla-daemon
2017-03-02 9:37 ` [Bug 194761] " bugzilla-daemon
2017-03-02 15:12 ` bugzilla-daemon
2017-03-02 16:16 ` bugzilla-daemon
2017-03-02 16:23 ` bugzilla-daemon
2017-03-02 16:24 ` bugzilla-daemon
2017-03-02 17:23 ` bugzilla-daemon
2017-03-15 11:30 ` bugzilla-daemon
2017-03-15 11:30 ` bugzilla-daemon
2017-05-19 6:16 ` bugzilla-daemon
2017-05-19 6:35 ` bugzilla-daemon
2017-05-19 9:43 ` bugzilla-daemon
2017-05-19 12:45 ` bugzilla-daemon
2017-05-22 2:32 ` bugzilla-daemon
2017-05-22 9:26 ` bugzilla-daemon
2017-05-22 9:34 ` bugzilla-daemon
2017-05-22 20:57 ` bugzilla-daemon
2017-05-23 14:58 ` bugzilla-daemon
2017-05-24 9:56 ` bugzilla-daemon
2017-05-24 11:49 ` bugzilla-daemon
2017-05-24 12:55 ` bugzilla-daemon
2017-05-26 2:05 ` bugzilla-daemon
2017-05-26 8:06 ` bugzilla-daemon
2017-05-26 8:25 ` bugzilla-daemon
2017-05-26 15:00 ` bugzilla-daemon
2017-05-26 16:38 ` bugzilla-daemon
2017-05-30 9:02 ` bugzilla-daemon
2017-05-30 13:19 ` bugzilla-daemon
2017-05-30 13:59 ` bugzilla-daemon
2017-05-30 14:41 ` bugzilla-daemon
2017-05-31 11:35 ` bugzilla-daemon
2017-06-01 11:53 ` bugzilla-daemon
2017-06-01 20:04 ` bugzilla-daemon
2017-06-02 2:28 ` bugzilla-daemon
2017-06-02 16:18 ` bugzilla-daemon
2017-06-02 20:26 ` bugzilla-daemon
2017-06-02 20:35 ` bugzilla-daemon
2017-06-03 10:27 ` bugzilla-daemon
2017-06-03 10:34 ` bugzilla-daemon
2017-06-03 10:37 ` bugzilla-daemon
2017-06-09 13:33 ` bugzilla-daemon
2017-06-09 13:45 ` bugzilla-daemon
2017-06-09 14:25 ` bugzilla-daemon
2017-06-09 14:28 ` bugzilla-daemon
2017-06-09 14:34 ` bugzilla-daemon
2017-06-09 15:06 ` bugzilla-daemon
2017-06-09 16:59 ` bugzilla-daemon
2017-06-09 17:37 ` bugzilla-daemon
2017-06-09 17:37 ` bugzilla-daemon
2017-06-09 18:40 ` bugzilla-daemon
2017-06-09 18:46 ` bugzilla-daemon
2017-06-09 18:46 ` bugzilla-daemon
2017-06-09 18:51 ` bugzilla-daemon
2017-06-09 18:57 ` bugzilla-daemon
2017-06-09 19:06 ` bugzilla-daemon
2017-06-09 19:08 ` bugzilla-daemon
2017-06-09 19:10 ` bugzilla-daemon
2017-06-09 19:11 ` bugzilla-daemon
2017-06-09 19:13 ` bugzilla-daemon
2017-06-09 19:17 ` bugzilla-daemon
2017-06-09 19:46 ` bugzilla-daemon
2017-06-09 19:52 ` bugzilla-daemon
2017-06-12 7:26 ` bugzilla-daemon
2017-06-12 7:39 ` bugzilla-daemon
2017-06-12 7:40 ` bugzilla-daemon
2017-06-12 7:40 ` bugzilla-daemon
2017-06-12 10:47 ` bugzilla-daemon
2017-06-12 11:09 ` bugzilla-daemon
2017-06-12 13:09 ` bugzilla-daemon
2017-06-15 14:12 ` bugzilla-daemon
2017-06-26 7:30 ` bugzilla-daemon
2017-06-26 12:30 ` bugzilla-daemon
2017-07-03 14:37 ` bugzilla-daemon
2017-07-03 15:04 ` bugzilla-daemon
2017-07-03 15:11 ` bugzilla-daemon
2017-07-06 15:35 ` bugzilla-daemon
2017-07-06 16:00 ` bugzilla-daemon
2017-07-07 22:12 ` bugzilla-daemon
2017-07-25 13:10 ` bugzilla-daemon
2017-07-28 9:06 ` bugzilla-daemon
2017-07-28 9:26 ` bugzilla-daemon
2017-07-28 14:16 ` bugzilla-daemon
2017-07-28 14:28 ` bugzilla-daemon
2017-07-28 14:31 ` bugzilla-daemon
2017-07-28 14:32 ` bugzilla-daemon
2017-07-28 17:00 ` bugzilla-daemon
2017-07-30 6:21 ` bugzilla-daemon
2017-07-31 14:17 ` bugzilla-daemon
2017-08-01 5:42 ` bugzilla-daemon
2017-08-23 14:47 ` bugzilla-daemon
2017-09-04 8:11 ` bugzilla-daemon
2017-09-11 15:39 ` bugzilla-daemon
2017-10-03 7:26 ` bugzilla-daemon
2017-10-20 14:26 ` bugzilla-daemon [this message]
2017-10-20 14:30 ` bugzilla-daemon
2017-10-20 19:20 ` bugzilla-daemon
2017-10-23 11:07 ` 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-194761-2300-YBjHTtCztC@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.