Lines Matching full:drivers
42 - [Using Pre-Production ICDs or Software Drivers](#using-pre-production-icds-or-software-drivers)
60 …- [Version Negotiation Between the Loader and Drivers](#version-negotiation-between-the-loader-and…
61 - [Interfacing With Legacy Drivers or Loaders](#interfacing-with-legacy-drivers-or-loaders)
76 - [Requirements of Well-Behaved Drivers](#requirements-of-well-behaved-drivers)
88 identify various behavior associated with drivers, this is purely
91 Granted, the majority of drivers to this date are ICD drivers
96 Vulkan allows multiple drivers each with one or more devices
98 The loader is responsible for discovering available Vulkan drivers on
100 Given a list of available drivers, the loader can enumerate all the
103 The process in which the loader discovers the available drivers on a
115 drivers with either the `VK_DRIVER_FILES` or the older `VK_ICD_FILENAMES`
135 Driver in addition to the standard drivers (without replacing the standard
153 disable known drivers.
167 comma-delimited list of globs to search for in known drivers.
178 If no drivers are found with a manifest filename that matches any of the
185 comma-delimited list of globs to search for in known drivers.
196 If no drivers are found with a manifest filename that matches any of the
237 before all other drivers.
254 before all other drivers.
276 In order to find system-installed drivers, the Vulkan loader will read the JSON
288 In order to find available drivers (including installed ICDs), the
327 HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers
334 HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\Vulkan\Drivers
345 [HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\Drivers\]
368 Drivers should use the registry locations from the PnP Configuration
370 Typically, this is most important for drivers, and the location clearly
372 The `SOFTWARE\Khronos\Vulkan\Drivers` location is the older method for locating
373 drivers, but is the primary location for software based drivers.
415 <td>Compile-time option set to possible location of drivers
423 <td>Compile-time option set to possible location of drivers
515 System installed drivers will be ignored if drivers are found inside of the app
517 This is because there is not a standard mechanism in which to distinguish drivers
522 Drivers found through environment variables, such as `VK_DRIVER_FILES`, will be
523 used regardless of whether there are bundled drivers present or not.
557 provide a driver or drivers to the Loader during vkCreateInstance.
558 This allows drivers to be included with an application without requiring
564 from system installed drivers and environment variable specified drivers will
565 appear before any `VkPhysicalDevice`s that originate from drivers from the
601 direct_driver_list.pDrivers = &direct_loading_info; // can include multiple drivers here if so desi…
607 * `VK_DIRECT_DRIVER_LOADING_MODE_EXCLUSIVE_LUNARG` - specifies that the only drivers
609 * `VK_DIRECT_DRIVER_LOADING_MODE_INCLUSIVE_LUNARG` - specifies that drivers
611 any system installed drivers and environment variable specified drivers.
627 `VkDirectDriverLoadingListLUNARG` structure, then no system installed drivers
638 Exclusive mode will also disable MacOS bundle manifest discovery of drivers.
644 extensions that originate from `VkDirectDriverLoadingListLUNARG` drivers during
647 function pointer directly from the drivers the application provides to the loader
653 Alternatively, because the Application is providing drivers, it is reasonable for
655 provided drivers, preventing the need to manually query them.
660 those layers will not be able to remove unsupported extensions from drivers that
666 ### Using Pre-Production ICDs or Software Drivers
669 detect their drivers.
679 drivers.
681 In other words, only the drivers listed in `VK_DRIVER_FILES` will be
734 and just as accurate to use for other drivers.</td>
797 Added the `is_portability_driver` boolean field for drivers to self report that
810 Because of this, all drivers must export the following function that is
813 interface between the loader and drivers for version 1 and higher
861 Beginning with Vulkan 1.1, drivers are not allowed to return this error
863 This creates a problem when working with multiple drivers, where one is
868 version supported by the drivers on the system.
871 1.0 to any 1.0 drivers in order to prevent an error.
900 Some drivers may expose an instance extension that the loader is already
902 Other drivers on that same system may not support the same instance
915 This is done per driver since different drivers may support different instance
925 drivers which do support the extension natively.
926 In this fashion, the application will be unaware of what drivers are
932 Drivers that implement entrypoints which take a `VkPhysicalDevice` as the first
940 interface between the loader and drivers.
943 Instead, drivers *must* expose it through `vk_icdGetInstanceProcAddr`.
1050 detailed below, that Drivers may provide on Windows.
1052 interface between the loader and drivers.
1055 Instead, drivers *must* expose it through `vk_icdGetInstanceProcAddr`.
1081 drivers that support this function will be sorted.
1097 software implementations, this step is necessary to allow drivers to
1105 The specific requirements on all dispatchable objects created by drivers
1111 This implies three things for drivers:
1115 * **NOTE:** For any C\++ drivers that implement VK objects directly
1147 Normally, drivers handle object creation and destruction for various Vulkan
1159 functions without involving the drivers.
1171 3. Drivers can cast any `VkSurfaceKHR` object to a pointer to the
1191 associated with multiple drivers.
1223 #### Version Negotiation Between the Loader and Drivers
1225 All drivers supporting Loader and Driver Interface Version 2 or higher must
1229 interface between the loader and drivers.
1232 Instead, drivers *must* expose it through `vk_icdGetInstanceProcAddr`.
1274 #### Interfacing With Legacy Drivers or Loaders
1291 Drivers which export `vk_icdNegotiateLoaderICDInterfaceVersion` will have it
1313 While exporting these functions is no longer a requirement, drivers may still
1315 The changes in this version allow drivers provided through the
1331 an indication to drivers that the loader is now evaluating whether the API
1378 can't handle the apiVersion, and drivers should fail with
1403 drivers.
1404 However, some drivers *may* want to provide their own surface handles.
1424 Interface Version 2 requires that drivers export
1426 …on, see [Version Negotiation Between Loader and Drivers](#version-negotiation-between-loader-and-d…
1429 drivers must be created in accordance to the
1477 - Drivers creating new dispatchable objects via device extensions need
1500 which filters out any drivers that report support for the portability subset
1504 VkInstanceCreateInfo::flags, the loader does not load any drivers that declare
1505 themselves to be portability drivers.
1507 Drivers declare whether they are portability drivers or not in the Driver
1513 portability drivers. This was done to give a grace period for applications to
1519 and drivers.
1542 - Drivers: which will have the string `DRIVER_` as part of the policy number.
1554 which indicates which policy statements apply to drivers that are focused
1561 ### Requirements of Well-Behaved Drivers
1574 <td>A driver <b>must not</b> cause other drivers to fail, crash, or
1716 by the loader on the drivers behalf.
1742 tracking badly behaving drivers based on the driver vendor, driver
1790 drivers to export core entrypoints.
1834 This is to allow support for fully software drivers as well as
1843 <a href="#using-pre-production-icds-or-software-drivers">
1883 earlier because the responsibility for this check falls on the drivers.
1895 drivers support <i>only</i> Vulkan API version 1.0 while other drivers
1898 <i>VkApplicationInfo</i> to version 1.0 for all the drivers that are
1900 Otherwise, the drivers that support Vulkan API version 1.0 will
1902 <i>vkCreateInstance</i> since 1.0 drivers were not aware of future
1915 support</i> instance-level functionality that other drivers support;
1917 some fashion for the non-supporting drivers.
1933 drivers support which extensions.<br/>
1946 that <b>may</b> be shared by all underlying drivers.