-------- Original Message --------
Subject: [ros-kernel] Re: How do device drivers fit into the project goal
Resent-Date: Sat, 17 Oct 1998 03:03:33 -0500
Resent-From: ros-kernel(a)sid-dis.com
Date: Sat, 17 Oct 1998 01:03:07 -0700 (PDT)
From: Jason Filby <jasonfilby(a)yahoo.com>
Reply-To: <ros-kernel(a)sid-dis.com>
To: ros-kernel(a)sid-dis.com
Hi,
---rex <rex(a)lvcablemodem.com> wrote:
I hope I'm not stepping on any toes, but I think
before Conner builds a fast but not necessarily
compatable video system, or Arindam builds a
compatable but not necessarily most effecient
network subsystem, perhaps we should reaffirm
the goal so noone takes the wrong path.
The goal states that WinNT drivers must be compatible with ReactOS. I
should be able to take a graphics or network driver that was written
for NT and use it with ReactOS. Compatibility is extremely important.
That said, ReactOS drivers don't necessarily have to run under NT. See
what I'm saying here? We MUST provide the mechanisms for NT drivers to
work - but CAN also add additional mechanisms that only ReactOS
drivers use so that they perform better.
Personally, I'd prefer that the mechanisms that allow NT drivers to
run 100% are implemented first -- then we can add our own mechanisms
that only drivers written to take advantage of them use. But you don't
necessarily have to go in that order.
At the end of the day, we'll run drivers for NT perfectly (1st
priority) and drivers for ReactOS even better (2nd priority).
I don't know if I explain this all clearly enough -- so, if not, just
tell me.
- Jason Filby
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at
http://mail.yahoo.com