From owner-freebsd-hackers Sat Jul 26 22:09:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17660 for hackers-outgoing; Sat, 26 Jul 1997 22:09:21 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17617; Sat, 26 Jul 1997 22:07:58 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id LAA25603; Sun, 27 Jul 1997 11:09:08 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707270509.LAA25603@hq.icb.chel.su> Subject: Re: SVR4.2MP source code has become available recently? To: stesin@gu.net Date: Sun, 27 Jul 1997 11:09:08 +0600 (ESD) Cc: dyson@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Andrew Stesin" at Jul 26, 97 00:20:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > And they have some kind of "unified driver interface" spec for UW. > How nice would it be -- to have an ability to use hardware > vendor's own drivers for UW, compatible with that spec, > just out of the box. Aaghh, dreams, dreams... :( About the driver interface. They have the document named "Device Driver Interface", the current version (that will be implemented in SCO Gemini) is DDI 8. A good thing is this documents descripts not only the calls that driver must support but the functions it can use too. It is made to allow to link the drivers with compliance to different levels of DDI simultaneously. The linking is dynamic, the function names are substituted to reflect the DDI level. This has one important consequence: all you need to link in the SVR4 drivers is to have the DDI-compliant in-kernel library and a SVR4->BSD object file format converter. Of course, you'll need STREAMS to use the SVR4 network drivers. -SB