X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
From:	Daniel Noll <daniel AT nuix DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ioperm() with ports above 0x3ff
Date:	Fri, 22 Feb 2008 08:50:37 +1100
User-Agent:	KMail/1.9.6 (enterprise 0.20070907.709405)
References:	<loom DOT 20080218T210001-512 AT post DOT gmane DOT org> <20080221204618 DOT GB10976 AT implementation>
In-Reply-To:	<20080221204618.GB10976@implementation>
MIME-Version:	1.0
Message-Id:	<200802220850.37455.daniel@nuix.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

On Friday 22 February 2008 07:46:18 Samuel Thibault wrote:
> Yes: on Linux ioperm doesn't work above 0x400.  On Linux, so as to
> access ports above 0x400 you need to use iopl(), that's why ioperm in
> cygwin does this.  Now, allowing >= 0x400 would be possible in cygwin's
> ioperm, but then you'd get problems when using the code on Linux...  The
> truly proper way is really to use iopl().

On the other hand the iopl() man page specifically says that it shouldn't be 
used in processes intended to be portable. ;-D

Daniel

--
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/

- Raw text -