From owner-freebsd-current Mon Nov 23 08:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00479 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:17:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00471 for ; Mon, 23 Nov 1998 08:17:34 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA03041; Tue, 24 Nov 1998 03:16:57 +1100 Date: Tue, 24 Nov 1998 03:16:57 +1100 From: Bruce Evans Message-Id: <199811231616.DAA03041@godzilla.zeta.org.au> To: bde@zeta.org.au, mjacob@feral.com Subject: Re: Breakage in -current for the ALPHA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> They traditionally go in sys (e.g., ttycom.h). Of course, there is >> no such thing as a machine independant driver API. There isn't even >> such a thing as a machine independent driver API. > >Eh? The second sentence might have been 'machine *dependent*'? > >In either case, what do you mean? There most certainly is both a DDI and >DKI for *BSD. There are MI functions (even in FreeBSD which is >historically less sensitive to MI vs MD issues) such as bcopy (DKI) or >devswitch functions. There are MD functions such as isa_configure (DDI). 1. Mispelling of `dependent' is annoying. 2. Nothing is really machine independent. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message