From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194559] amdgpu problems loading 2 firmwares on multi-smp system
Date: Tue, 14 Feb 2017 08:15:00 +0000 [thread overview]
Message-ID: <bug-194559-2300-8p27VHjoT5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194559-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194559
--- Comment #5 from fin4478@hotmail.com ---
(In reply to Janpieter Sollie from comment #3)
> it works! attached my config file of your drm-next kernel
> I don't know what needs to be done for you developers to integrate drm-next
> into the mainline kernel, but thank you!!!
Amd should warn not use stock kernels and tell how to use use ~agd5f wip
kernel and latest mesa git. Here is the page for you, dear Amd:
http://support.amd.com/en-us/download/linux
This and many other amdgpu bug reports prove my point.
--
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-02-14 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 14:34 [Bug 194559] New: amdgpu problems loading 2 firmwares on multi-smp system bugzilla-daemon
2017-02-12 16:09 ` [Bug 194559] " bugzilla-daemon
2017-02-13 3:28 ` bugzilla-daemon
2017-02-14 6:55 ` bugzilla-daemon
2017-02-14 7:59 ` bugzilla-daemon
2017-02-14 8:00 ` bugzilla-daemon
2017-02-14 8:02 ` bugzilla-daemon
2017-02-14 8:15 ` bugzilla-daemon [this message]
2017-02-14 8:32 ` bugzilla-daemon
2017-02-14 15:05 ` bugzilla-daemon
2017-02-14 15:18 ` bugzilla-daemon
2017-02-16 9:15 ` bugzilla-daemon
2017-02-28 9:42 ` bugzilla-daemon
2017-03-16 10:01 ` 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-194559-2300-8p27VHjoT5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox