Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualNik02

Posted 12 July 2012 - 06:46 AM

The handle is expected to be that of a native module (commonly a dll), which implements and exports the D3D driver entrypoints (there are lot of them).

All the stuff you need to implement is listed in the Windows DDK under the graphics drivers section. The basics of implementing a software driver are almost exactly same as implementing the user-mode portion of a hardware driver, though direct kernel access is not strictly necessary in pure software. In addition, software driver necessarily needs to implement the actual drawing operations such as the whole graphics pipeline, which would otherwise reside on GPU hardware.

I am under the impression that D3D 11.1 will be released on Vista and 7 as well, after '8' launches. This would enable you to use the WARP driver with 11.0 feature set.

#5Nik02

Posted 12 July 2012 - 06:44 AM

The handle is expected to be that of a native module (commonly a dll), which implements and exports the D3D driver entrypoints (there are lot of them).

All the stuff you need to implement is listed in the Windows DDK under the graphics drivers section. The basics of implementing a software driver are almost exactly same as implementing the user-mode portion of a hardware driver, though direct kernel access is not strictly necessary in pure software. In addition, software driver necessarily needs to implement the actual drawing operations such as the whole graphics pipeline, which would otherwise reside on GPU hardware.

#4Nik02

Posted 12 July 2012 - 06:41 AM

The handle is expected to be that of a native module (commonly a dll), which implements and exports the D3D driver entrypoints (there are lot of them).

All the stuff you need to implement is listed in the Windows DDK under the graphics drivers section. Implementing a software driver is almost exactly same as implementing the user-mode portion of a hardware driver, though direct kernel access is not strictly necessary in pure software.

#3Nik02

Posted 12 July 2012 - 06:38 AM

The handle is expected to be that of a native module (commonly a dll), which implements and exports the D3D driver entrypoints (there are lot of them).

All the stuff you need to implement is listed in the Windows DDK under the graphics drivers section.

#2Nik02

Posted 12 July 2012 - 06:34 AM

The handle is expected to be that of a native DLL, which implements and exports the D3D driver entrypoints (there are lot of them).

All the stuff you need to implement is listed in the Windows DDK under the graphics drivers section.

#1Nik02

Posted 12 July 2012 - 06:32 AM

The handle is expected to be that of a native DLL, which implements and exports the D3D driver entrypoints (there are lot of them).

PARTNERS