From owner-freebsd-chat Tue Sep 29 21:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18894 for freebsd-chat-outgoing; Tue, 29 Sep 1998 21:28:12 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18889 for ; Tue, 29 Sep 1998 21:28:10 -0700 (PDT) (envelope-from gene@nttlabs.com) Received: from localhost (gene@localhost) by seera.nttlabs.com (8.9.1/8.9.1) with SMTP id VAA14656 for ; Tue, 29 Sep 1998 21:27:53 -0700 (PDT) (envelope-from gene@nttlabs.com) X-Authentication-Warning: seera.nttlabs.com: gene owned process doing -bs Date: Tue, 29 Sep 1998 21:27:52 -0700 (PDT) From: "Eugene M. Kim" To: FreeBSD Chat Mailing List Subject: Win95/NT drivers on FreeBSD? In-Reply-To: <19980930092623.F15172@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, this is just a wild idea, so please don't throw a stone at me :-) If we could provide a device driver framework that is identical to M$ Win95/98 DDK's one, then it would be a good incentive to the device driver developers to release a FreeBSD driver. It's a sort of ``get the FreeBSD Win95 Compatibility DDK, compile your source on it, and there you go!'' type of thing. Well, the resulting driver code probably will be less efficient than FreeBSD ``native'' drivers, but it's still better than nothing... Or maybe we could even maintain the binary compatibility with Win95 device drivers, if Microsoft didn't plant anything secret in their DDK so that every device driver file would have some ``blackbox'' code. Would this be a technically/legally possible way? Just wondering... Cheers, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message