About OS drivers


Let's discuss a little bit about drivers. No, not about vehicle drivers. About Operating Systems hardware drivers.

How the modern operating systems interact with the hardware devices? Well, the current approach is that every hardware device producer provides a specific OS driver, and every OS installs it. It is ok, it's working. But we found an another way to work with drivers.

In Roluan, the Operating System will not know absolutely nothing about hardware drivers software. No drivers software installation. Instead, it will use a generic software layer to interact with driver controller. That's all.
But wait, every driver has specific functionality. It needs to have specific software. Where it will be located and how it will interact with the OS?


The response is simple: the driver software will be stored in the hardware itself. And it will interact with OS through mentioned generic software layer. All devices has their own controllers where is stored some information about them. And the driver will be stored there too.

This approach will resolve many problems. Let's enumerate some of them:
- On a clean OS installation, no additional drivers software will be needed. All drivers will work from start.
- The updates will update the device controller, not the operating system. Again, all drivers will work.
- Reinstalling the system will be very easy, no need to have driver disks, no need to find them from internet and so on. And the most beautiful: if a driver was updated to last version before installation, even on clean install, the new driver software version will be used.
- The Operation System will remain clean. That means, there will be no multiple versions of drivers software.
- While programming, the direct access to hardware, which is a trend today, will not use multiple software layers. As a result, the computational speed will increase substantially.

There are many benefits of this approach. We will discuss them in future posts.