https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #1 from taij...@posteo.de ---
OK, I think I've managed to narrow this one down a bit.
If I build the kernel from commit 09695ad78f1f5f315c7e9c5090f0c7b846a43690,
which is also tagged as 'drm-next-4.17', then everything is shiny. However, if
I go one step beyond that, which is commit
33d009cd889490838c5db9b9339856c9e3d3facc - being the rebasing of
drm-next-4.17-wip onto David Airlie's drm-next branch after he merged AMD's
drm-next-4.17 into his branch, then things to belly up and the kernel does not
boot anymore.
Now, what I do not get is how the rebase to a tree that includes stuff that is
not amdgpu would bork up the ability of amdgpu to load it's firmware?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
