Drivers programming

Which language generally all driver software is being created ?
can't we create our own drivers ?
How the drivers interact with the hardware ?
What's the general difference b/w general programming and driver programming ?

Windows Drivers are written with C/C++ with the Driver Development Kit.

Main difference is a error in the driver will cause a bluescreen rather then a friendly little fault box.

as it was said by BC_prog...?the windows drivers are written with c/c++ language ,the language created by Dennis Ritchie on the seventies in BELL:USA

Something is missing in your answers......
The little information what I knew is the answers given by u.....

The answers for the remaining questions are missed..........
I need explanation....

Which language generally all driver software is being created ?
can't we create our own drivers ?
What's the general difference b/w general programming and driver programming ?

3/4 solved.

I'm not satisfied with your answers.......
I need expert answer.

Can't we create our own drivers ?
How the drivers interact with the hardware ?

I'm not satisfied with your answers.......
I need expert answer.

THESE ARE THE EXPERTS!

If you aren't satisfied, nothing is preventing you from closing the window and never coming back.

You don't have any priviliges to say it. I didn't satisfied with the answers. I need an expert answer mean "I need more explanation with examples". If they know they certainly provide it, I know. There are lot of experts in the forum (100%) they'l give the better answer if they saw my post. You child don't be silly in giving such nasty posts........

Can't we create our own drivers ?

well you can but it's generally agreed that you would need to know what your doing. Any error caused by a driver will cause a kernel mode BSOD (the user mode fault dialog is the same thing as a BSOD, but since it was user mode code it was recoverable)

(windows for example would use the DDK and any stdcall capable language)

How the drivers interact with the hardware ?

This depends on the platform. many platforms implement a "hardware abstraction layer" which virtualizes calls to hardware components. Hardware is accessed just as it always has been- through mapped memory addresses, or mapped memory. One example being to store a memory block in mapped device memory and then call a hardware interrupt; the ahrdware device interprets the memory contents and performs a task, or performs a task with that memory (such as send it out to the network).


The main difficulty with your question is the assumption that drivers are the same under any architecture and operating System. This is not so. With Linux, there are a number of different technologies that can be leveraged to write a driver; DOS is another architecture altogether; your question has a different answer for each one.

The main difficulty with your question is the assumption that drivers are the same under any architecture and operating System.

Hey ! I know about this.... but I have a little curiosity especially for windows os how they are interacted. Thanks for your help.

I'm not satisfied with your answers.......

You have no manners.

Sorry, it will never happens.....