Some of the drivers in the stack might participate by transforming the request from one format to another. The conventional way to visualize the stack is with the first participant at the top and the last participant at the bottom, as shown in this diagram. Not all drivers communicate directly with a device.įor a given I/O request (like reading data from a device), there are often several drivers, layered in a driver stack, that participate in the request. This means that the driver can be written by Microsoft, and the device designer does not have to provide a driver.
In many cases, a device is designed according to a published hardware standard. Not all drivers have to be written by the company that designed the device. Our explanation so far is oversimplified in several ways: After the driver gets the data from the device, it returns the data to the operating system, which returns it to the application.
#One drive microsoft what is it how to
The driver, which was written by the same company that designed and manufactured the device, knows how to communicate with the device hardware to get the data. The application calls a function implemented by the operating system, and the operating system calls a function implemented by the driver. In the most fundamental sense, a driver is a software component that lets the operating system and a device communicate with each other.įor example, suppose an application needs to read some data from a device. It is challenging to give a single precise definition for the term driver.
0 kommentar(er)
