From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 82201] [HAWAII] GPU doesn't reclock, poor 3D performance Date: Sun, 12 Oct 2014 09:45:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2054287081==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DB0DF6E2A6 for ; Sun, 12 Oct 2014 02:45:09 -0700 (PDT) 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 --===============2054287081== Content-Type: multipart/alternative; boundary="1413107109.614acB0.27554"; charset="UTF-8" --1413107109.614acB0.27554 Date: Sun, 12 Oct 2014 09:45:09 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D82201 --- Comment #34 from Christian K=C3=B6nig --- (In reply to Kai from comment #33) > And I have non-reclocking GPU again. > Is there any data I can provide, that would help you tracking down, what > Windows is setting, that is preventing proper initialisation of the card = for > Linux? Well that could actually be perfectly normal behavior. For some hardware bl= ocks you can upload the firmware only once after a bootup. So what could happen is that the windows driver loads one version and the l= inux driver needs a different one. The same problems applies the other way aroun= d as well. --=20 You are receiving this mail because: You are the assignee for the bug. --1413107109.614acB0.27554 Date: Sun, 12 Oct 2014 09:45:09 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 34 on bug 82201<= /a> from Christian K=C3=B6nig 
(In reply to Kai from =
comment #33)
> And I have non-reclocking GPU again.
> Is there any data I can provide, that would help you tracking down, wh=
at
> Windows is setting, that is preventing proper initialisation of the ca=
rd for
> Linux?

Well that could actually be perfectly normal behavior. For some hardware bl=
ocks
you can upload the firmware only once after a bootup.

So what could happen is that the windows driver loads one version and the l=
inux
driver needs a different one. The same problems applies the other way aroun=
d as
well.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1413107109.614acB0.27554-- --===============2054287081== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============2054287081==--