From owner-freebsd-hackers Sun Sep 20 21:27:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20946 for freebsd-hackers-outgoing; Sun, 20 Sep 1998 21:27:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20912 for ; Sun, 20 Sep 1998 21:27:33 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA03143; Sun, 20 Sep 1998 21:32:48 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809210432.VAA03143@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: More on the Intel-UNIX standard In-reply-to: Your message of "Mon, 21 Sep 1998 13:19:35 +1000." <98Sep21.131912est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 21:32:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 20 Sep 1998 00:26:18 -0500, "Pedro F. Giffuni" wrote: > >I'm concerned about the SNR in hackers, but I just couldn't resist > >asking if someone was aware and acting on this > > http://www.sco.com/udi/ > > This was mentioned by some Intel marketroids at the recent AUUG'98 > conference. There was a fair amount of discussion at a subsequent > Freenix BOF (which included Greg Lehey and Peter Wemm within the > FreeBSD group and Robert Hart from Red Hat, as well as assorted > users from the Linux community and all the *BSD groups). > > The almost unanimous concensus(*) was that it was a very bad move and > the Freenix community should resist it. The major problems seen by > the group were: > 1) Binary-only device drivers are a bad idea. It will reduce the chances > of us getting access to the hardware interface specs, and therefore > being able to build a device driver that works. > 2) Binary-only device drivers tie the hardware to the processor. This > reduces the portability of (eg) PCI cards. > 3) The difficulty of supporting the kernel services required for a UDI > driver. > 4) Increased finger-pointing when a device driver fails. Unless there's been a sudden change of direction in the last few months, UDI is source-level, not a binary-level interface. This invaliates 1) and 2). 3) is actually less of a problem than many people like to think; unlike most other driver models (eg. WDM) UDI has been designed by people that understand the issues. I can't see how 4) makes for "more" finger pointing, actually. I'd say it would lead to a net _reduction_, as there would be only one driver vendor. > (*) I think I was the only person who felt it had any merit at all. It sounds like at least the major participants in the discussion were working on partial or nonexistent background information. The very first sentence on the UDI homepage is: "This is the home page for Project UDI, a multi-company effort to define a Uniform Driver Interface, which provides an environment for portable driver code, and to establish program plans for deploying this technology." *sigh* -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message