This is the mail archive of the
cygwin
mailing list for the Cygwin project.
ioperm() with ports above 0x3ff
- From: Andrew Dyer <amdyer at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 18 Feb 2008 21:15:42 +0000 (UTC)
- Subject: ioperm() with ports above 0x3ff
I am having problems using ioperm() to try and access a parallel printer port on
a PCI card in my system running WinXP. The port is mapped to I/O port address
0xDCD8. I cannot access the port because the ioperm() driver has a check to
limit I/O port accesses to < 0x400.
from /usr/src/ioperm-0.4/driver/ioperm.c, lines 95-100
/* test input buffer size and parameters */
if ((io_stack->Parameters.DeviceIoControl.InputBufferLength < sizeof (struct
ioperm_data))
|| (!ioperm_data) || (ioperm_data->from + ioperm_data->num > 0x400))
{
Irp->IoStatus.Status = STATUS_INVALID_PARAMETER;
} else {
It looks like there is complete support for the bitmap that NT uses to allow I/O
permissions across a full x86 I/O port range of 0-0xFFFF, but the library
enforces this artificial port limit check. Is there a reason I can't see for
having this restrictive check in the driver (especially considering the nature
of what the driver does)?
I can't rebuild the driver as I don't have access to the DDK. Can someone
rebuild it with the check modified so I could test it?
Please cc: my email address as I am not subscribed to the list.
Thanks!
--
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/