Bug 91464 - Device ID 0x162B not handled
Summary: Device ID 0x162B not handled
Status: RESOLVED FIXED
Alias: None
Product: Beignet
Classification: Unclassified
Component: Beignet (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: ruiling
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-25 20:51 UTC by Jonathan Keatley
Modified: 2015-08-10 08:20 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jonathan Keatley 2015-07-25 20:51:42 UTC
I have an Intel NUC Core i7 with Iris 6100 graphics (NUC5i7RYH), and I have installed Ubuntu 15.04.  Here's the "uname -a" string:

  > Linux yorktown 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I built and tested Beignet latest master (834d0ae), and it wouldn't run any unit tests, failing with the following output:

  > platform number 1
  > platform_profile "FULL_PROFILE"
  > platform_name "Intel Gen OCL Driver"
  > platform_vendor "Intel"
  > platform_version "OpenCL 1.2 beignet 1.1 (git-834d0ae)"
  > platform_extensions "cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_spir cl_khr_icd"
  > cl_get_gt_device(): error, unknown device: 162b
  > error calling clGetDeviceIDs
  > Failed to initialize cl device.
  > 
  > summary:
  > ----------
  >   total: 762
  >   run: 0
  >   pass: 0
  >   fail: 0
  >   pass rate: 0.000000
Comment 1 Jonathan Keatley 2015-07-25 20:56:03 UTC
BTW, the Iris graphics 6100 chipset is a Broadwell GT3 device. It's characteristics are probably similar to the nearby Broadwell GT3 devices with IDs 1622, 1626, 162A, 162D, and 162E.
Comment 2 ruiling 2015-08-10 08:20:55 UTC
fix on master, see "runtime: add Broadwell deviceID 0x162B"


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.