From: Franz Fehringer <fehrin2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ioperm / iopl / pciutils
Date: Thu, 2 Feb 2023 08:40:28 +0100 [thread overview]
Message-ID: <trfpdc$2j2$1@ciao.gmane.io> (raw)
In-Reply-To: <trfp08$jkd$1@ciao.gmane.io>
Am 02.02.2023 um 08:33 schrieb Franz Fehringer via Cygwin:
> Am 31.01.2023 um 10:27 schrieb Corinna Vinschen via Cygwin:
>> On Jan 29 18:22, Franz Fehringer via Cygwin wrote:
>>> Hi all,
>>>
>>> Is there any Cygwin package providing the iopl et al. routines?
>>> Google uncovers an ioperm package but that seems to be nothing current.
>>> My goal is to compile https://github.com/pciutils/pciutils with Cygwin.
>>
>> Cygwin doesn't have any Linux-like or POSIX-like API (device names,
>> ioctl's and whatnot) to access PCI directly.
>>
>>
>> Corinna
>>
>
> On https://github.com/pciutils/pciutils the claim is
>
> In runs on the following systems:
> Linux (via /sys/bus/pci, /proc/bus/pci or i386 ports)
>
> and http://ftp.uni-kl.de/pub/windows/cygwin/release/ioperm/setup.hint says
>
> # $Id: setup.hint,v 1.4 2003/01/31 14:58:56 telka Exp $
>
> sdesc: "support for ioperm()/iopl() functions"
> ldesc: "This package adds support for ioperm()/iopl() functions to Cygwin.
> This support includes sys/io.h and sys/perm.h header files together
> with development and runtime libraries."
> category: Devel Libs System
> requires: cygwin libpopt0
>
> So there possibly was once iopl support?
>
>
>
Just guessing this was possibly 32bit only.
next prev parent reply other threads:[~2023-02-02 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:22 Franz Fehringer
2023-01-30 2:35 ` Eliot Moss
2023-01-30 7:09 ` Franz Fehringer
2023-01-31 9:27 ` Corinna Vinschen
2023-02-01 19:31 ` Franz Fehringer
2023-02-02 7:33 ` Franz Fehringer
2023-02-02 7:40 ` Franz Fehringer [this message]
2023-02-02 11:07 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='trfpdc$2j2$1@ciao.gmane.io' \
--to=fehrin2@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).