Re: ioperm / iopl / pciutils
On Feb 2 08:40, Franz Fehringer via Cygwin wrote: > 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? I was just trying to say that Cygwin itself (i. e., the core DLL) does not provide any such calls or headers. > Just guessing this was possibly 32bit only. Very likely. Looks like we never had an ioperm package for 64 bit, and that makes sense. You'd have to build the ioperm package by yourself for 64 bit, and you'll have a few problems there. - Checking the package for type safety. Think LP64 vs. LLP64 https://cygwin.com/faq.html#faq.programming.64bitporting - The ioperm package can only provide these calls by installing a kernel driver (see the source, driver subdir). - This driver may or may not work on 64 bit, but if it works, you can only install it by switching your machine into debug mode: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/installing-an-unsigned-driver-during-development-and-test - For normal operations you have to sign the driver. Self-signed drivers won't run on any machine with UEFI secure boot enabled. Alternatively you can let Microsoft sign it. Only that version would be ok for inclusion into the Cygwin distro. - Alternatively you can try to convert the ioperm driver into an UMDF driver. Some kernel functionality is not allowed for UMDF drivers, but I never looked deeper into this. Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
setup 2.925 release candidate - please test
A new setup release candidate is available at: https://cygwin.com/setup/setup-2.925.x86_64.exe (64 bit version) https://cygwin.com/setup/setup-2.925.x86.exe(32 bit version) Please test, and report any problems here. This is not the place for setup feature requests. Changes compared to 2.924: - Show a deprecation warning for Windows 6.1 and 6.2 Show a warning if we're running on a Windows version for which support was deprecated in Cygwin 3.4, i.e: Windows 6.1 (Windows 7, Windows Server 2008R2) Windows 6.2 (Windows 8, Windows Server 2012). - Ignore attempts to select the reinstall action, if the installed version is not accessible (e.g. reinstall is run from local directory but the package is no longer cached) (thanks to Christian Franke) - Add an '(x86_64)' suffix to start menu folders names when installing x86_64 Cygwin on some other architecture (e.g ARM64). - Various fixes around "All Users/"Just For Me" (thanks to Christian Franke for investigating these problems): -- Fix a long-standing bug (since 2012), where installed files are owned by the user's primary group, rather than the Adminstrators group, when installing for "All Users". -- We no longer change group back to the user's primary group while running postinstall scripts, when installing for "All Users". This was only for the benefit of mkgroup/mkpasswd being run by the postinstall script, which we don't do any more. -- Fix "Just For Me" being ignored, when run with Admininstrator privileges -- Fix "All Users" being selectable but basically ineffectual, when not run with Admininstrator privileges - Fix a bug in handling (documented, but as yet unused) 'Source:' lines in setup.ini. - Add an experimental zn_CN GUI translation, contributed via weblate by Xiang Heng Wei - Various internal fixes to Unicode handling in GUI to support that. For instructions on obtaining and building the source code for setup, see https://sourceware.org/cygwin-apps/setup.html Please send bug reports, as usual, to the public mailing list cygwin AT cygwin DOT com. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Curious setup behavior?
1) Launch setup-x86_64 and go as far as the "Pending" list (assuming there are pending packages to be updated). Note "Best" is selected. 2) Then click "Back" to get to the mirror selection page 3) Click "Next" again. Now it says there is nothing pending. 4) Click back (mirror selection) and re-select the same or a different mirror and click "Next" Still nothing pending, "Best" is still selected. 5) Select "Sync" instead of "Best" All the pending packages reappear. Switching from "Sync" back to "Best" does not affect the display at this point. If you initially have "Sync" selected, then switching to "Best" reveals the missing pending items. I.e. restoring the list seems to be "edge-triggered" on the "Keep/Best/Sync" state. -- Jim Garrison j...@acm.org -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Setup reinstall incomplete script does nothing
Hi folks, Using previously posted reinstall incomplete packages script as a number of my packages are now flagged Incomplete. The script now seems to do nothing to any package as setup comes up with a blank list of packages. Also tried a number of variations including shell script invocations, and adding options. Are there any missing or identical package conditions, options required, cmd, shell script, or setup program arg limits that might affect a remove/install? The package list used for ...\setup-X86_64 -x ... -P ... is: alacarte,antiword,bash,cron,ctags,dbus,debianutils,e2fsprogs,email,f22-backgrounds-extras,fbpanel,flaw,GeoIP-database,getent,gnu-free-fonts,gnupg,htmldoc,icon-naming-utils,initscripts,libcaca-devel,libcrypt-devel,liberation-fonts,libiconv-devel,libnspr-devel,libnss-devel,libopts-devel,libpng-devel,libpng16-devel,libproj12,mksh,perl_manpages,poppler,postfix,postfix-tools,procmail,python27,recode,sendmail,statgrab,sysvinit,tcp_wrappers,usbredir,usbutils,vim-clang-format,wodim,xml2po,zsh -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirerbut when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
