From owner-freebsd-current Tue Apr 13 12:48:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C2D8E1551B for ; Tue, 13 Apr 1999 12:48:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA28822; Tue, 13 Apr 1999 12:45:29 -0700 Date: Tue, 13 Apr 1999 12:45:28 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Rick Whitesel Cc: Doug Rabson , current@FreeBSD.ORG, UCHIYAMA Yasushi Subject: Re: newconfig/new-bus In-Reply-To: <001101be85e3$77fd1e20$d3e4b38c@xyplex.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi: > I should have been more clear. BSD driver interoperability is a seperate > issue from Linux application interoperability but I think both are > important. For an example of Linux/*BSD driver interoperability and the grief and difficulties therein, you might want to look at the Qlogic SCSI/FibreChannel driver I've done. It exists for FreeBSD,OpenBSD,NetBSD and Linux. It's a dicey business trying to straddle this broad of a set of fences. The take home lesson here is that in order to make a dirver work without overloading a platform specific areas is that the core driver has to be single threaded, not do locking and not do too much porpoising in and out of the platform layers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message