Resources assignment

Hi!,

I have a couple of questions:

The device for which I'm writting a wdm driver has I/O
ports, memory ranges, DMA and IRQs. So I've been writing
a basic driver (just to read a port).

1. My first doubt is: If I only write in my start device
routine that I have I/O port resources, could be a
problem? I mean by just ignoring the other resorces, could
a problem arise?

2. When the PnP manager sends me a filter resource
requirements irp, does that mean that there is no
information about the resources "inside" my device? Or is
because of my driver??

Thanx

Mark
Thu Dec 11 06:59:02 CST 2003

On Thu, 11 Dec 2003 03:12:30 -0800, "Rodrigo Zimbron"
<rodzimbron@stopspam.hotmail.com> wrote:

>Hi!,
>
>I have a couple of questions:
>
>The device for which I'm writting a wdm driver has I/O
>ports, memory ranges, DMA and IRQs. So I've been writing
>a basic driver (just to read a port).
>
>1. My first doubt is: If I only write in my start device
>routine that I have I/O port resources, could be a
>problem? I mean by just ignoring the other resorces, could
>a problem arise?
>

Your interrupt resource is problematic. If your device ever generates
an interrupt, and if it is a PCI style device (level interrupts) your
system may be toast. You should always implement an ISR for your
interrupt resources.

>2. When the PnP manager sends me a filter resource
>requirements irp, does that mean that there is no
>information about the resources "inside" my device? Or is
>because of my driver??
>

Neither. This is always sent and can be generally ignored (using the
'ignoring' rules for the specific pnp IRP or verifier will have a
fit.)




=====================
Mark Roddy
Windows XP/2000/NT Consulting, Microsoft DDK MVP
Hollis Technology Solutions 603-321-1032
www.hollistech.com
markr@hollistech.com
For Windows Device Driver Training: see www.azius.com

John
Tue Dec 16 08:39:38 CST 2003

I was wrong, PCI boards can have ports.

>-----Original Message-----
>
>>>1. My first doubt is: If I only write in my start
device
>>>routine that I have I/O port resources, could be a
>>>problem? I mean by just ignoring the other resorces,
>could
>>>a problem arise?
>>>
>>
>>Your interrupt resource is problematic. If your device
>ever generates
>>an interrupt, and if it is a PCI style device (level
>interrupts) your
>>system may be toast. You should always implement an ISR
>for your
>>interrupt resources.
>
>For PCI boards, I haven't had any problems ignoring
>interrupt capabilities -- JUST DON'T GENERATE AN
>INTERRUPT :-)
>For ISA boards, I've always reserved the interrupt in
>order to avoid hardware conflicts.
>
>For PCI boards, there are no ports (that I know of) just
>memory mapped I/O.
>For ISA boards, I've always reserved the ports in order
to
>avoid hardware conflicts.
>
>For PCI boards, you can refrain from mapping some of your
>I/O windows. You can also map them multiple times.
>For ISA boards, I've always reserved the high memory
>requirements for the board to avoid hardware conflicts.
>
>For PCI boards, DMA is bus-master based and does not
>require resources.
>For ISA board, the DMA is based in the chipset and
>requires a resource. You shouldn't have any trouble AS
>LONG AS YOU DON'T TURN ON THE ISA DMA. :-)
>
>.
>