From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109345] drm-next-2018-12-14 -Linux PPC Date: Mon, 13 May 2019 14:20:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0619240778==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 300FE89E3B for ; Mon, 13 May 2019 14:20:00 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0619240778== Content-Type: multipart/alternative; boundary="15577572001.3FBd8d648.23846" Content-Transfer-Encoding: 7bit --15577572001.3FBd8d648.23846 Date: Mon, 13 May 2019 14:20:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D109345 Christian Zigotzky changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NOTABUG |--- --- Comment #46 from Christian Zigotzky --- (In reply to Michel D=C3=A4nzer from comment #45) > Reviewing the information, I'm afraid it's not clear that there's a bug h= ere. >=20 > 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. >=20 > Something like this in /etc/X11/xorg.conf should be enough to make Xorg u= se > the FirePro card: >=20 > Section "Device" > Identifier "whatever" > BusID "PCI:5@4096:0:0" > EndSection 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-1= 4'. The answer was: "No, the only changes were changes in comments, removing so= me unused code and changes in the shared ttm module that touched all drivers t= hat use ttm." This wasn't correct. I had to compile a lot of kernels and after that we kn= owed 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 rep= ort. Please give Allan the chance to test your solution. PLEASE check your code more carefully before you release it. There are a lo= t of endusers who uses this code in they daily work later. Cheers, Christian --=20 You are receiving this mail because: You are the assignee for the bug.= --15577572001.3FBd8d648.23846 Date: Mon, 13 May 2019 14:20:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated Christian Zigotzky changed bug 10934= 5
What Removed Added
Status RESOLVED REOPENED
Resolution NOTABUG ---

Comme= nt # 46 on bug 10934= 5 from Christian Zigotzky
(In reply to Michel D=C3=A4nzer from comment #45)
> Reviewing the information, I'm afraid it's not c=
lear that there's a bug here.
>=20
> The description says the FirePro is the secondary card in a PCIe 1x sl=
ot,
> 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.
>=20
> Something like this in /etc/X11/xorg.conf should be enough to make Xor=
g use
> the FirePro card:
>=20
> Section "Device"
>         Identifier "whatever"
>         BusID   "PCI:5@4096:0:0"
> EndSection

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-1=
4'.
The answer was: "No, the only changes were changes in comments, removi=
ng some
unused code and changes in the shared ttm module that touched all drivers t=
hat
use ttm."

This wasn't correct. I had to compile a lot of kernels and after that we kn=
owed
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 rep=
ort.

Please give Allan the chance to test your solution.

PLEASE check your code more carefully before you release it. There are a lo=
t of
endusers who uses this code in they daily work later.

Cheers,
Christian


You are receiving this mail because:
  • You are the assignee for the bug.
= --15577572001.3FBd8d648.23846-- --===============0619240778== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0619240778==--