Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <43060E64.B79EA0F1@dessent.net>
Date: Fri, 19 Aug 2005 09:52:52 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: building device drivers
References: <Pine DOT LNX DOT 4 DOT 62 DOT 0508191235570 DOT 31247 AT ns DOT pyerotechnics DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Jason Pyeron wrote:

> I am building a windows device driver (libraw1394), now I want to do it
> using cygwin (port of Linux device driver). I assume I will need to
> statically link to cygwin libs.
> 
> I am assuming the windows device drivers cannot have DLL dependencies.
> 
> So can things be linked statically? If so an example, please?

I don't think that's really going to work.  Cygwin cannot be linked
statically and even if it could, it was not designed to run in kernel
space at all.  Cygwin does not try to emulate the linux kernel, just a
POSIX api.  So low level things like device drivers are not going to
just port over.  What you need to do is get the Windows DDK and write a
true windows driver for your device.  Then you can port the userland
tools using Cygwin and interface with the windows driver.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/