Changes between Version 1 and Version 2 of Developer/Projects/Obsolete/RosettaOSDeviceDriverAPI


Ignore:
Timestamp:
Mar 10, 2010, 6:04:53 PM (10 years ago)
Author:
JoelSherrill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Obsolete/RosettaOSDeviceDriverAPI

    v1 v2  
    66'''Possible Mentors:''' Matthew Dillon of DragonFlyBSD.  Various core RTEMS developers.
    77
    8 '''Introduction:''' We want to shared code from the various BSD UNIX distributions at the kernel and device driver level.  We want to achieve this by defining a device driver support API that various OSes can write to.  The current notes and proposal at at the  [http://code.google.com/p/rosetta-os/wiki| Rosetta OS Wiki].  As this is a cross-platform effort, the project will likely start by helping Matthew Dillon implement the Device Driver API on DragonFlyBSD so network device drivers can run in user space.  This will help solidify and formalize the API.  From an RTEMS perspective, we would track the API and ensure we can implement it.  You could certainly begin to implement.  But until NIC drivers work in user space on DragonFlyBSD, it makes no sense to do anything more than unit test the RTEMS implementation of the Device Driver API.  After things work on DragonFlyBSD, you would compile ALL device driver code that Matthew Dillon can compile for user space for RTEMS and test what can be tested given available hardware and simulators.
     8'''Introduction:''' We want to shared code from the various BSD UNIX distributions at the kernel and device driver level.  We want to achieve this by defining a device driver support API that various OSes can write to.  The current notes and proposal at at the  [http://code.google.com/p/rosetta-os/wiki Rosetta OS Wiki].  As this is a cross-platform effort, the project will likely start by helping Matthew Dillon implement the Device Driver API on DragonFlyBSD so network device drivers can run in user space.  This will help solidify and formalize the API.  From an RTEMS perspective, we would track the API and ensure we can implement it.  You could certainly begin to implement.  But until NIC drivers work in user space on DragonFlyBSD, it makes no sense to do anything more than unit test the RTEMS implementation of the Device Driver API.  After things work on DragonFlyBSD, you would compile ALL device driver code that Matthew Dillon can compile for user space for RTEMS and test what can be tested given available hardware and simulators.
    99
    1010'''Goal:''' Implement Rosetta OS Device Driver API so that BSD, MINIX and RTEMS hackers can share code easily at the device driver and kernel level.
     
    2222
    2323
    24  *  [http://groups.google.com/group/rosetta-os| Rosetta OS Google Group]
    25  *  [http://code.google.com/p/rosetta-os/wiki| Rosetta OS Wiki]
     24 *  [http://groups.google.com/group/rosetta-os Rosetta OS Google Group]
     25 *  [http://code.google.com/p/rosetta-os/wiki Rosetta OS Wiki]
    2626
    2727'''Other sections:''' If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.