From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 77069] New: Use semantic naming for microcode files
Date: Fri, 04 Apr 2014 20:52:14 +0000
Message-ID: <bug-77069-502@http.bugs.freedesktop.org/>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1399259948=="
Return-path: <dri-devel-bounces@lists.freedesktop.org>
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
 by gabe.freedesktop.org (Postfix) with ESMTP id 84EC26E13D
 for <dri-devel@lists.freedesktop.org>; Fri,  4 Apr 2014 13:52:14 -0700 (PDT)
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
 <mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel" <dri-devel-bounces@lists.freedesktop.org>
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org


--===============1399259948==
Content-Type: multipart/alternative; boundary="1396644734.cABEd350.22454"; charset="us-ascii"


--1396644734.cABEd350.22454
Date: Fri, 4 Apr 2014 20:52:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"

https://bugs.freedesktop.org/show_bug.cgi?id=77069

          Priority: medium
            Bug ID: 77069
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Use semantic naming for microcode files
          Severity: minor
    Classification: Unclassified
                OS: Linux (All)
          Reporter: nmschulte@gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

This is a rather trivial request, but it would help the uninitiated and long
term maintenance.

It would be nice if the microcode was more semantically named, rather than how
it exists now.

For example, I currently have an issue with UVD on a Radeon HD 8970M, which is
"Neptune XT" based (which is "Pitcairn" based), and I receive the following
logging:

[   15.942210] [drm] Loading PITCAIRN Microcode
[   15.966837] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_pfp.bin
[   15.976695] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_me.bin
[   15.996448] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_ce.bin
[   16.015403] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_rlc.bin
[   16.016529] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_mc.bin
[   16.026910] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_smc.bin
[   16.045744] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin

....

[   65.525470] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   66.537637] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   67.549797] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   68.561967] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   69.574142] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   70.586334] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   71.598533] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   72.610705] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   73.622877] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   74.635068] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   74.654938] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
[   74.654955] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).

At first glance, I'm thinking: well clearly TAHITI_uvd.bin is incorrect for
PITCAIRN Microcode, but that's not quite how things work.  It would be nice to
name the UVD microcode after the actual version of the platform the code is
targeting.  Perhaps this is simply a naming collision issue and the UVD
microcode naming is semantic within the context (that is: my Radeon HD 8970M
card really does run the TAHITI version of UVD), but that's doubtful and I
would suggest the names change to be more meaningful, :).

Another proposition is to skip the "fully semantic naming" idea above and just
use symlinks to bridge the two namespaces.

-- 
You are receiving this mail because:
You are the assignee for the bug.

--1396644734.cABEd350.22454
Date: Fri, 4 Apr 2014 20:52:14 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"

<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Use semantic naming for microcode files"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=77069">77069</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>dri-devel&#64;lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Use semantic naming for microcode files
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>minor
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>nmschulte&#64;gmail.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>DRM/Radeon
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This is a rather trivial request, but it would help the uninitiated and long
term maintenance.

It would be nice if the microcode was more semantically named, rather than how
it exists now.

For example, I currently have an issue with UVD on a Radeon HD 8970M, which is
&quot;Neptune XT&quot; based (which is &quot;Pitcairn&quot; based), and I receive the following
logging:

[   15.942210] [drm] Loading PITCAIRN Microcode
[   15.966837] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_pfp.bin
[   15.976695] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_me.bin
[   15.996448] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_ce.bin
[   16.015403] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_rlc.bin
[   16.016529] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_mc.bin
[   16.026910] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_smc.bin
[   16.045744] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin

....

[   65.525470] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   66.537637] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   67.549797] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   68.561967] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   69.574142] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   70.586334] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   71.598533] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   72.610705] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   73.622877] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   74.635068] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[   74.654938] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
[   74.654955] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).

At first glance, I'm thinking: well clearly TAHITI_uvd.bin is incorrect for
PITCAIRN Microcode, but that's not quite how things work.  It would be nice to
name the UVD microcode after the actual version of the platform the code is
targeting.  Perhaps this is simply a naming collision issue and the UVD
microcode naming is semantic within the context (that is: my Radeon HD 8970M
card really does run the TAHITI version of UVD), but that's doubtful and I
would suggest the names change to be more meaningful, :).

Another proposition is to skip the &quot;fully semantic naming&quot; idea above and just
use symlinks to bridge the two namespaces.</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>

--1396644734.cABEd350.22454--

--===============1399259948==
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

--===============1399259948==--