Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 16 Aug 2000 01:51:12 +0300
From: Marc Esipovich <marc AT corky DOT net>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: What's the status of cygwin on NT device drivers?
Message-ID: <20000816015112.B19665@marcellos.corky.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

 Hi,

	I would like very much to avoid using MSVC or similar packages
to make an NT device driver. paying cygnus is way better than paying MS :)

	I've  skimmed through the lists, and found some old (1999) notes
about cygwin already supporting native PE's, but not __fastcall, what
has changed since then?

	So, who has some updated info for me on building them pesky drivers
w/ the help of that butt-ugly NT DDK?

	It needn't be a comlex driver,  basically hooking some syscalls and
talking to a userland app. maybe even write a device which emulates /dev
so no changes will be needed in my Unixified userland code. ;)

	I'd also be glad to land a hand to those with things in progress
concerning this issue.

	Any help would be greatly appreciated.

 bye,
	Marc.

 P.S, Please CC to me as I'm not subscribed to the list.

--
marc @ corky.net

fingerprint = D1F0 5689 967F B87A 98EB  C64D 256A D6BF 80DE 6D3C

          /"\
          \ /     ASCII Ribbon Campaign
           X      Against HTML Mail
          / \

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com