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: Tue, 30 Apr 2019 16:00:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0562277998==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 54895891A1 for ; Tue, 30 Apr 2019 16:00:44 +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 --===============0562277998== Content-Type: multipart/alternative; boundary="15566400441.1932E.20776" Content-Transfer-Encoding: 7bit --15566400441.1932E.20776 Date: Tue, 30 Apr 2019 16:00:44 +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 --- Comment #16 from Christian Zigotzky --- (In reply to Michel D=C3=A4nzer from comment #15) > This is a platform specific issue. We cannot test on this platform, so > someone who can has to isolate the change causing the problem. I realize > this may suck, but it's reality. OK. Where could be the issue in these DRM updates? I think the issue is somewhere in the updated Core source files. I don=E2=80=99t think the issue= is in the driver updates. What do you think? --=20 You are receiving this mail because: You are the assignee for the bug.= --15566400441.1932E.20776 Date: Tue, 30 Apr 2019 16:00:44 +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

Comme= nt # 16 on bug 10934= 5 from Christian Zigotzky 
(In reply to Michel D=C3=A4nzer from comment #15)
> This is a platform specific issue. We cannot tes=
t on this platform, so
> someone who can has to isolate the change causing the problem. I reali=
ze
> this may suck, but it's reality.

OK. Where could be the issue in these DRM updates? I think the issue is
somewhere in the updated Core source files. I don=E2=80=99t think the issue=
 is in the
driver updates. What do you think?

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