Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Mon, 20 Jan 2003 19:06:23 +0100
From: Marcel Telka <marcel AT telka DOT sk>
To: Max Bowsher <maxb AT ukf DOT net>
Cc: cygwin AT cygwin DOT com
Subject: Re: Announce: ioperm-0.2.1 for cygwin released
Message-ID: <20030120180623.GE28535@tortuga.etc.sk>
References: <20030120145735 DOT GC28535 AT tortuga DOT etc DOT sk> <20030120150543 DOT GC27717 AT redhat DOT com> <20030120175247 DOT GD28535 AT tortuga DOT etc DOT sk> <004b01c2c0ad$6dea9300$78d96f83 AT pomello>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004b01c2c0ad$6dea9300$78d96f83@pomello>
User-Agent: Mutt/1.4i

On Mon, Jan 20, 2003 at 05:57:42PM -0000, Max Bowsher wrote:
> Marcel Telka wrote:
> > On Mon, Jan 20, 2003 at 10:05:43AM -0500, Christopher Faylor wrote:
> >> On Mon, Jan 20, 2003 at 03:57:35PM +0100, Marcel Telka wrote:
> >>> This software adds support for ioperm() function to Cygwin. This
> >>> support includes sys/io.h and sys/perm.h header files (not included
> >>> in Cygwin by default) together with development and runtime
> >>> libraries.
> >>>
> >>> News in this release:
> >>> * Windows DDK is optional for compilation now
> >>> * --prefix=/usr parameter for ./configure script is not mandatory
> >>> now
> >>>
> >>> Homepage: http://openwince.sourceforge.net/ioperm/
> >>
> >> Is there some reason you're not proposing this as a standard cygwin
> >> package?
> >
> > There are at least two reasons:
> > 1. A device driver (ioperm.sys) is required for running ioperm with
> > NT/2000/XP
> > 2. Windows DDK is required for the driver compilation.
> >
> > If these drawbacks are acceptable for a standard cygwin package I
> > could start ioperm integration with mainstream cygwin net
> > distribution.
> 
> Personal opinion ONLY:
> 1. is annoying but probably acceptable if there is some way to install it.

Installation is simple (reboot is not required - tested with 2000/XP).

$ ioperm -i
Installing ioperm.sys...
OpenSCManager       ok
CreateService       ok
StartService        ok

Installation ok.

> 2. is likely a problem. Are you aware that w32api has some ddk support now?

Yes. But this is only at .h level. I need a linker (binutils)...

$ objdump -x ioperm.sys 
BFD: ioperm.sys (.text): Section flag IMAGE_SCN_MEM_NOT_PAGED (0x8000000) ignored
BFD: ioperm.sys (.text): Section flag IMAGE_SCN_MEM_NOT_PAGED (0x8000000) ignored
objdump: ioperm.sys: File format not recognized

:-(

> That might be a way around this problem.

I'm unaware about any way to compile & link a device driver using cygwin-only tools
:-(


-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel AT telka DOT sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel AT jabber DOT sk |
+-------------------------------------------+

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/