Re: Mainstone PcCard + PCMCIA + KernelIoControl = ?
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Tue, 21 Oct 2008 10:08:30 -0400
Have you implemented IOCTL_HAL_REQUEST_SYSINTR in your OAL? This allows the
kernel to map a particular IRQ value to a SYSINTR.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"MSCENV" <mscenv@xxxxxxxxxxx> wrote in message
news:6b4ef135-c04f-4186-a559-780c6f601bce@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am working on getting a PCCard driver working for my platform. Using
the Mainstone Pccard driver, I have run into a problem when using a
Socket serial card.
The registry entry for the Pccard has a "ClientIrq" entry, but it does
not have a corresponding entry for the client (Ready) Sysintr value.
This causes a debugchk in Pccard\mdd\pcmciaen.cpp when the driver
calls RequestSysIntr\KernelIOControl looking for a sysintr value for
the ClientIrq value.
How do I resolve this?
.
- Follow-Ups:
- Re: Mainstone PcCard + PCMCIA + KernelIoControl = ?
- From: MSCENV
- Re: Mainstone PcCard + PCMCIA + KernelIoControl = ?
- References:
- Mainstone PcCard + PCMCIA + KernelIoControl = ?
- From: MSCENV
- Mainstone PcCard + PCMCIA + KernelIoControl = ?
- Prev by Date: Wireless Connection Settings
- Next by Date: Re: Can a touchscreen driver be written as a user mode driver?
- Previous by thread: Mainstone PcCard + PCMCIA + KernelIoControl = ?
- Next by thread: Re: Mainstone PcCard + PCMCIA + KernelIoControl = ?
- Index(es):