Extensible Driver Interface: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [unchecked revision] |
Content added Content deleted
m (Added link) |
No edit summary |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1:
{{Stub}}
The Extensible Driver Interface (EDI) is a driver interface that is intended to be portable between OSes while standardizing as little functionality as possible.
== Introduction ==
In 2006, Eli Gottlieb made EDI after deciding that [[UDI]] standardized too much. It is designed to be small, extensible, and require very little from the system providing the implementation
▲It is designed to require very little from the system providing the implementation, while still allowing for simple extension. This is done by using an object oriented model accessed using C functions, allowing drivers and operating systems in almost all languages to use it.
==
=== External Links ===
*[https://sourceforge.net/projects/glider-kernel/files/EDI%20Headers%20and%20Docs/ EDI Specification and sample driver]
*[https://www.osnews.com/story/16602/Introducing_the_Extensible_Driver_Interface OSNews article written by the creator of EDI]
=== Threads ===
*[[Topic:637|Project announcement]]
*[[Topic:16592|Discussion thread]]
[[Category:Driver Interfaces]]
[[Category:OS theory]]
|
Latest revision as of 16:27, 9 July 2023
This page is a stub.
You can help the wiki by accurately adding more contents to it.
The Extensible Driver Interface (EDI) is a driver interface that is intended to be portable between OSes while standardizing as little functionality as possible.
Introduction
In 2006, Eli Gottlieb made EDI after deciding that UDI standardized too much. It is designed to be small, extensible, and require very little from the system providing the implementation. This is done by using an object oriented model accessed using C functions, allowing drivers and operating systems in almost all languages to use it.