<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:chzigotzky@xenosoft.de" title="Christian Zigotzky <chzigotzky@xenosoft.de>"> <span class="fn">Christian Zigotzky</span></a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345">bug 109345</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>NOTABUG
</td>
<td>---
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345#c46">Comment # 46</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345">bug 109345</a>
from <span class="vcard"><a class="email" href="mailto:chzigotzky@xenosoft.de" title="Christian Zigotzky <chzigotzky@xenosoft.de>"> <span class="fn">Christian Zigotzky</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=109345#c45">comment #45</a>)
<span class="quote">> Reviewing the information, I'm afraid it's not clear that there's a bug here.
>
> The description says the FirePro is the secondary card in a PCIe 1x slot,
> whereas the R7 is in the PCIe 16x slot. Thus it seems pretty clear that
> without explicit configuration, Xorg should be expected to come up on the
> R7. Arguably it was actually the previous behaviour that was buggy.
>
> Something like this in /etc/X11/xorg.conf should be enough to make Xorg use
> the FirePro card:
>
> Section "Device"
> Identifier "whatever"
> BusID "PCI:5@4096:0:0"
> EndSection</span >
Hi Michel,
Why did you close this bug report? Allan hasn't tested your solution yet.
My first question in this thread was, if you modified the behaviour of the
initialisation of two graphics cards in the DRM updates 'drm-next-2018-12-14'.
The answer was: "No, the only changes were changes in comments, removing some
unused code and changes in the shared ttm module that touched all drivers that
use ttm."
This wasn't correct. I had to compile a lot of kernels and after that we knowed
that you modified the behaviour of the initialisation of two graphics cards in
the DRM updates 'drm-next-2018-12-14'. And now you just closed this bug report.
Please give Allan the chance to test your solution.
PLEASE check your code more carefully before you release it. There are a lot of
endusers who uses this code in they daily work later.
Cheers,
Christian</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>