Defining a common minimal Kernel Programming Interface
Posted: Fri Mar 29, 2002 12:00 am
Hello, OS developers.
As there are more and more OS projects on the web and more and more hardware devices to support, i wondered wether we could cooperate and produce a sort of 'Standardized Kernel Programming Interface' (a kind of osdev api) for hardware device drivers, so that a wide range of kernels could share the same device drivers ...
the Osdev KPI could include informations such as:
- the binary format used for drivers (for instance, a ELF file having an init() and a reset() function)
- the environment that drivers will be able to use from the kernel (how to get memory, buffer-class memory, how to start a kernel thread, write to a log, etc.)
- a driver descriptor, that could be used by the kernel to access the driver (usual read/writes?)
Let me know how you feel about this ...
As there are more and more OS projects on the web and more and more hardware devices to support, i wondered wether we could cooperate and produce a sort of 'Standardized Kernel Programming Interface' (a kind of osdev api) for hardware device drivers, so that a wide range of kernels could share the same device drivers ...
the Osdev KPI could include informations such as:
- the binary format used for drivers (for instance, a ELF file having an init() and a reset() function)
- the environment that drivers will be able to use from the kernel (how to get memory, buffer-class memory, how to start a kernel thread, write to a log, etc.)
- a driver descriptor, that could be used by the kernel to access the driver (usual read/writes?)
Let me know how you feel about this ...