| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
- Add bit flags for image aspects.
- Replace VkRect with VkRect2D and VkRect3D.
- Rename vkCmdClearDepthStencil to vkCmdClearDepthStencilImage
- Add vkCmdClearColorAttachment and vkCmdClearDepthStencilAttachment
Remaining to be done:
- Actually implement vkCmdClearColorAttachment,
vkCmdClearDepthStencilAttachment in the Intel ICD
- Enforce renderpass interactions: CmdClear*Attachment may only be
called within a renderpass; CmdClear*Image may only be called outside
a renderpass.
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
- Add infrastructure in vulkaninfo to dump features/limits. To be filled
out to dump everything interesting.
- Move existing limits from VkPhysicalDeviceInfo to
VkPhysicalDeviceLimits, and drop those that no longer exist.
- Adjust the drivers to fill out the above in their new location.
Other new features/limits still to be exposed by nulldrv and the intel
ICD.
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
With minimal changes to keep everything building and functioning.
|
|
Part of header revision 135 changes.
|
|
Moved the HOST_LOCAL memory property.
|
|
Took out VK_INDEX_TYPE_UINT8.
|
|
|
|
|
|
Usage was declared redundant.
|
|
Reworked memory properties and types and added support for multiple
heaps.
|
|
Updated tests and demos to properly use VkShaderModule.
Add support to shader_checker for shader module.
Doesn't do anything with the pName parameter.
|
|
Continue implementation of shader module.
|
|
Discovered an issue where a layer was doing cleanup
in it's DestroyDevice function but the CreateDevice
was never called.
This happened because the extension was only enabled
on the device chain and the device chain doesn't actually
call CreateDevice. That happens on the Instance chain.
Making it so that we can call down the device chain -
which is terminated by the ICD.
We need to know the real device object to construct the
device chain heiarchy and when calling down the device
chain it should end with the ICD doing the actual device
object creation.
This patch fixes the issue by using the
same process as CreateInstance. The loader will call
the ICD's CreateDevice and pass that in the *pDevice
argument. The layers then ignore the PhysicalDevice parameter
and use the *pDevice to access the device chain.
To prevent the ICD from being called twice needed to
stub in a special loader_GetDeviceChainProcAddr to provide
a stub for only CreateDevice as the end of the chain.
|
|
|
|
Discovered an issue where a layer was doing cleanup
in it's DestroyDevice function but the CreateDevice
was never called.
This happened because the extension was only enabled
on the device chain and the device chain doesn't actually
call CreateDevice. That happens on the Instance chain.
Making it so that we can call down the device chain -
which is terminated by the ICD.
We need to know the real device object to construct the
device chain heiarchy and when calling down the device
chain it should end with the ICD doing the actual device
object creation.
This patch fixes the issue by using the
same process as CreateInstance. The loader will call
the ICD's CreateDevice and pass that in the *pDevice
argument. The layers then ignore the PhysicalDevice parameter
and use the *pDevice to access the device chain.
To prevent the ICD from being called twice needed to
stub in a special loader_GetDeviceChainProcAddr to provide
a stub for only CreateDevice as the end of the chain.
integrate review feedback.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://cvs.khronos.org/bugzilla/show_bug.cgi?id=14014
Header and minimal code changes to include support for
multiple entrypoints in a shader module.
Driver implementation TBD.
|
|
https://cvs.khronos.org/bugzilla/show_bug.cgi?id=14016
|
|
|
|
NOTES:
1/ Some layers impact from vkGetFormatInfo ->
vkGetPhysicalDeviceFormatInfo; some checks are currently disabled in
ParamChecker pending discussion on the best way to do this. Similar
checks in Image layer implemented via additional layer_data member
to link back from VkDevice -> VkPhysicalDevice.
2/ VkPhysicalDeviceFeatures, VkPhysicalDeviceLimits members all zero
for now; also some further churn to be done to the contents of these
structures.
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
https://cvs.khronos.org/bugzilla/show_bug.cgi?id=13038
|
|
Bug# 13800
|
|
|
|
This is only used for getting display object which is no longer needed
since the GetDisplayInfoWSI() functions is removed
|
|
This entry point was a challenge for loader to handle correctly. Since it is
going away in the new WSI proposal remove it in all components.
|
|
Renamed depth-stencil minDepth and maxDepth to minDepthBounds and
maxDepthBounds.
|
|
|
|
Conflicts:
layers/draw_state.cpp
|
|
Remove pointSize and pointFadeThreshold from VkDynamicRsStateCreateInfo.
|
|
|
|
Conflicts:
layers/mem_tracker.cpp
|
|
Add error codes for messages the debug report layer
can generate.
|
|
No way to reliably dispatch this entry point in layers; will not be recursive.
Conflicts:
loader/loader.c
|
|
https://cvs.khronos.org/bugzilla/show_bug.cgi?id=13466
|
|
|
|
|
|
Implement proposal in comment #3.
Agreed in June '15 Khronos face-to-face
|
|
Right now only DrawState and ParamChecker implement this extension.
|
|
|
|
This patch starts restructuring the various components
(loader, driver, layers, etc.) to support global and
device extensions. Require GetProcAddr to access the
extension functions and related support.
|
