2019-01-23 19:06:14 +08:00
|
|
|
|
2018-02-28 04:58:29 +08:00
|
|
|
# Frequently asked questions
|
|
|
|
|
|
2020-02-28 16:30:11 +08:00
|
|
|
For OpenCL specific questions,
|
|
|
|
|
see the [OpenCL FAQ](https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md).
|
|
|
|
|
|
2018-02-28 04:58:29 +08:00
|
|
|
## OS support
|
|
|
|
|
|
|
|
|
|
### Which Linux versions does NEO support?
|
|
|
|
|
|
|
|
|
|
NEO should work on any modern Linux distribution (i.e. Ubuntu, Fedora, etc.)
|
|
|
|
|
with default / stock configuration (no kernel patches), assuming the underlying
|
2018-04-03 18:46:52 +08:00
|
|
|
kernel's drm subsystem is 4.7 or higher. Newer platforms will require a kernel version
|
2018-03-21 23:48:05 +08:00
|
|
|
that provides support for that platform (e.g. Coffee Lake requires kernel 4.14 or higher).
|
|
|
|
|
|
2020-03-05 15:15:11 +08:00
|
|
|
Our default (most frequent) validation config is currently Ubuntu 18.04 LTS (as of Q1'20).
|
2019-03-04 18:02:35 +08:00
|
|
|
|
2018-02-28 04:58:29 +08:00
|
|
|
### Does NEO support Microsoft Windows?
|
|
|
|
|
|
|
|
|
|
Our closed-source driver for Windows is using the same codebase. At this time,
|
2020-03-05 15:15:11 +08:00
|
|
|
we do not support compilation of the stack for Windows. It is our long-term
|
2018-02-28 04:58:29 +08:00
|
|
|
intention to offer that option.
|
|
|
|
|
|
|
|
|
|
### Why is the feature set different in latest Windows driver vs. latest NEO on github?
|
|
|
|
|
|
|
|
|
|
Our Windows release process takes up to several weeks before drivers are available through intel.com
|
|
|
|
|
and/or Windows update. Features available in github will be available on Windows later.
|
2019-02-18 23:07:45 +08:00
|
|
|
|
|
|
|
|
Note: Older platforms (e.g. Broadwell) are considered to be in maintenance mode for Windows.
|
2018-02-28 04:58:29 +08:00
|
|
|
|
|
|
|
|
## Platform support
|
|
|
|
|
|
|
|
|
|
### Which Intel platforms are supported by the driver?
|
|
|
|
|
|
|
|
|
|
See [README.md](https://github.com/intel/compute-runtime/blob/master/README.md).
|
|
|
|
|
|
2019-07-01 21:10:06 +08:00
|
|
|
### How can I check that my specific device is supported by the driver?
|
|
|
|
|
|
|
|
|
|
To check support for any device, you can follow these steps:
|
|
|
|
|
1. Go to [Ark]( https://ark.intel.com) and find your Device ID
|
|
|
|
|
1. Find the corresponding device ID label in [GMM]( https://github.com/intel/gmmlib/blob/master/Source/inc/common/igfxfmid.h)
|
2020-02-28 16:30:11 +08:00
|
|
|
1. Check if this device ID label is enumerated in the
|
|
|
|
|
[supported device list](https://github.com/intel/compute-runtime/blob/master/opencl/source/dll/linux/devices/devices_base.inl)
|
2019-07-01 21:10:06 +08:00
|
|
|
|
2018-02-28 04:58:29 +08:00
|
|
|
### When will support for platform X be added?
|
|
|
|
|
|
|
|
|
|
We will start adding platform support after platform is disclosed by Intel.
|
|
|
|
|
It is our intention to offer full support ahead of platform's market availability.
|
|
|
|
|
|
|
|
|
|
## Who are we?
|
|
|
|
|
|
2020-03-05 15:15:11 +08:00
|
|
|
The Compute Runtime team is part of VTT (Visual Technologies Team).
|
2018-04-09 17:40:32 +08:00
|
|
|
|
2020-03-05 15:15:11 +08:00
|
|
|
Most of our engineers are located in Poland and the United States.
|
