delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
X-SBRS: | 3.5 |
X-MesageID: | 42987213 |
X-Ironport-Server: | ftlpip02.citrite.net |
X-Remote-IP: | 216.142.71.134 |
X-Policy: | $Relay |
X-IronPort-AV: | E=Sophos;i="4.25,388,1199682000"; d="scan'208";a="42987213" |
Date: | Thu, 21 Feb 2008 23:14:20 +0100 |
From: | Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: ioperm() with ports above 0x3ff |
Message-ID: | <20080221221420.GC19778@implementation> |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <loom DOT 20080218T210001-512 AT post DOT gmane DOT org> <20080221204618 DOT GB10976 AT implementation> <200802220850 DOT 37455 DOT daniel AT nuix DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <200802220850.37455.daniel@nuix.com> |
User-Agent: | Mutt/1.5.12-2006-07-14 |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
Daniel Noll, le Fri 22 Feb 2008 08:50:37 +1100, a écrit : > 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 To non-Linux environments, yes, but Cygwin is meant to be Linux-compatible. Anyway, tinkering with ports is definitely not portable ;) Samuel -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |