Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<005901bef01c$9e94b950$26c256d1@hercules>
From:	"Chris Telting" <telting AT sprynet DOT com>
To:	"Emanuele Aliberti" <ealiberti AT hotmail DOT com>
Cc:	<cygwin AT sourceware DOT cygnus DOT com>
References:	<19990826174128 DOT 56045 DOT qmail AT hotmail DOT com>
Subject:	Re: Cygwin NT DDK Project
Date:	Thu, 26 Aug 1999 16:40:18 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300

----- Original Message -----
From: Emanuele Aliberti <ealiberti AT hotmail DOT com>
To: <bianchi AT www DOT arte DOT unipi DOT it>; <telting AT sprynet DOT com>
Cc: <cygwin AT sourceware DOT cygnus DOT com>
Sent: Thursday, August 26, 1999 12:41 PM
Subject: Re: Cygwin NT DDK Project


> >In short: CygWin is a (_GREAT_) porting tool, with MinGW a very good
> >target for "usual" applications. Using it for driver purposes looks to
me,
> >at this stage, a waste of time; full support for all the available user
> >mode APIs would be a much more useful project.
>
> I use the Cygwin's little child: mingw32. Ld can build native applications
> (*) and, since kernel mode drivers are native DLLs, it probably can build
> them too. Unfortunately, as Mumit confirmed prevately, gcc can not handle
> the __fastcall calling convention which is required to call some
frequently
> used system calls from kernel mode, so it is not complete yet for a free
WNT
> DDK.

That's all that's needed?  It only requires a keyword and code to generate
the fastcalls which is minimal.  Even I can do that.  If that's what's
needed then
I volunteer to do it myself.  I also know as a fact that the linker needs to
be
changed.

There actually needs to be a flag set in the pe header in order for it to be
a
valid but again that's minimal.

Does anyone actually want this?  I figured that it would be minimal to
implement if it weren't already implemented.  I personally think that the
gnu tools would be a superior build environment than currently exists
with the NT DDK.

And I'd personally like to see a free nt fs kit; at a minimal all the
required
include headers and import libraries.  Possibly minimal documentation
of what people have so far figured out indipendently about making such
drivers.

<PONDERING>
On a seperate issue.  I was posdering the possibility of a virtual
 subsystem for nt drivers for linux.  Mostly the mini drivers such as
printers
and possibly video.  While it wouldn't be as good as native drivers; still
slow drivers are better than no drivers.  Anyone see any problems with
this?  It's certianly is alot of work but can anyone suggest as fundimental
or legal reasons why it wouldn't be possible?
</PONDERING>


BlueCoder
bluecoder AT rocketmail DOT com
May you live as long as you wish and love as long as you live.




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

- Raw text -