2019-01-23 12:06:14 +01:00
|
|
|
|
2018-02-27 21:58:29 +01:00
|
|
|
# Frequently asked questions
|
|
|
|
|
|
2020-02-28 09:30:11 +01:00
|
|
|
For OpenCL specific questions,
|
|
|
|
|
see the [OpenCL FAQ](https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md).
|
|
|
|
|
|
2018-02-27 21:58:29 +01: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 12:46:52 +02:00
|
|
|
kernel's drm subsystem is 4.7 or higher. Newer platforms will require a kernel version
|
2018-03-21 16:48:05 +01:00
|
|
|
that provides support for that platform (e.g. Coffee Lake requires kernel 4.14 or higher).
|
|
|
|
|
|
2019-02-18 16:07:45 +01:00
|
|
|
Our default (most frequent) validation config is currently (as of Q4'18) Ubuntu 18.04 LTS.
|
2018-02-27 21:58:29 +01:00
|
|
|
|
2019-03-04 11:02:35 +01:00
|
|
|
Note: Neo will not work correctly on legacy kernels with Intel patches (e.g. 4.7.0.intel.r4.0).
|
|
|
|
|
|
2018-02-27 21:58:29 +01:00
|
|
|
### Does NEO support Microsoft Windows?
|
|
|
|
|
|
|
|
|
|
Our closed-source driver for Windows is using the same codebase. At this time,
|
|
|
|
|
we do not support compilation of the OpenCL stack for Windows. It is our long-term
|
|
|
|
|
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 16:07:45 +01:00
|
|
|
|
|
|
|
|
Note: Older platforms (e.g. Broadwell) are considered to be in maintenance mode for Windows.
|
2018-02-27 21:58:29 +01: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 15:10:06 +02: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 09:30:11 +01: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 15:10:06 +02:00
|
|
|
|
2018-02-27 21:58:29 +01: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-02-28 09:30:11 +01:00
|
|
|
NEO OpenCL team is part of VTT (Visual Technologies Team).
|
2019-02-18 16:07:45 +01:00
|
|
|
Historically, our team was responsible for delivery of the closed source OpenCL driver for Windows, Linux, and Android.
|
2018-02-27 21:58:29 +01:00
|
|
|
|
|
|
|
|
Most of the developers are located in Poland (UTC+1 timezone).
|
2018-04-09 11:40:32 +02:00
|
|
|
|
|
|
|
|
### I would like to join your team. How can I apply for a job?
|
|
|
|
|
|
|
|
|
|
1. Go to: https://jobs.intel.com/ListJobs/All/Search/city/Gdansk/
|
|
|
|
|
1. Filter for OpenCL in the job title
|
2019-12-09 13:01:39 +01:00
|
|
|
1. Browse the descriptions looking for positions mentioning this GitHub repository
|
