PFND3D11_1DDI_RESOURCEUPDATESUBRESOURCEUP - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D11_1DDI_RESOURCEUPDATESUBRESOURCEUP Pfnd3d111DdiResourceupdatesubresourceup;
VOID Pfnd3d111DdiResourceupdatesubresourceup(
D3D10DDI_HDEVICE unnamedParam1,
D3D10DDI_HRESOURCE unnamedParam2,
UINT unnamedParam3,
const D3D10_DDI_BOX *unnamedParam4,
const VOID *unnamedParam5,
UINT unnamedParam6,
UINT unnamedParam7,
UINT CopyFlags
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
updates a destination subresource region that stores constant buffers from a source system-memory region. Implemented by Windows Display Driver Model (WDDM) 1.2 and later user-mode display drivers.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2hDstResource
A handle to the destination resource to copy to.
unnamedParam3DstSubresource
An index that indicates the destination subresource to copy to.
unnamedParam4pDstBox [in, optional]
A pointer to a D3D10_DDI_BOX structure that specifies the region of the destination subresource to copy data to. If pDstBox is NULL, the driver should copy to the entire destination subresource.
unnamedParam5pSysMemUP [in]
A pointer to the beginning address of the source data that DefaultConstantBufferUpdateSubresourceUP(D3D11_1) uses to update the destination subresource.
unnamedParam6RowPitch
The offset, in bytes, to move to the next row of source data.
unnamedParam7DepthPitch
The offset, in bytes, to move to the next depth slice of source data.
CopyFlagsA value that specifies characteristics of copy operation as a bitwise OR of the values in the D3D11_1_DDI_COPY_FLAGS enumeration type.
The driver can use the pfnSetErrorCb callback function to set an error code.
The driver should not encounter any error, except for D3DDDIERR_DEVICEREMOVED. Therefore, if the driver passes any error, except for D3DDDIERR_DEVICEREMOVED, in a call to the pfnSetErrorCb function, the Direct3D runtime will determine that the error is critical. Even if the device was removed, the driver is not required to return D3DDDIERR_DEVICEREMOVED; however, if device removal interfered with the operation of DefaultConstantBufferUpdateSubresourceUP(D3D11_1) (which typically should not happen), the driver can return D3DDDIERR_DEVICEREMOVED.