How to specify IRQ range in resource override INF section

NTDEV
1

Can we specify “any suitable/availble” interrupt in a resource override INF
section?

Background: I need to add another BAR window to a PCI device, but leave it’s
IRQ assignment as is.
However, the IRQ must be specified as well - otherwise I don’t get any.

Below is my override section:

[VMEBRIDGE.NTx86.LogConfigOverride]
LogConfig=VMEB_M2

[VMEB_M2]
ConfigPriority=DESIRED
MemConfig=dc000000-dc000FFF(DRW) ; existing window
MemConfig=200000@00000000-FFFFFFFF(DRW) ; additional window
IRQConfig=LS:24

The IRQ 24 is what Windows (or BIOS?) would assign automatically, without
override.
If I specfify any other value, it fails with problem 12.

So, is there any syntax like IRQConfig=* or IRQConfig=LS:1-256 just to let
Windows to assign what it wants,
or the only allowed is
IRQConfig=1,2,3,4,5…etc…255(?)

Regards,
Pavel

2

> The IRQ 24 is what Windows (or BIOS?) would assign automatically, without

override.
If I specfify any other value, it fails with problem 12.

Strange. Can you omit IRQConfig at all?

Look at other driver’s INF files.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

3

You can’t usefully use INFs to say anything about a PCI device’s resources.
Log Configs only really work for ISA/LPC devices.

If you need another BAR, just add another entry in your resource
requirements list with EvtDeviceFilterAddResourceRequirements.

–
Jake Oshins
Hyper-V I/O Architect
Windows Kernel Group

This post implies no warranties and confers no rights.

“Pavel A.” wrote in message news:xxxxx@ntdev…
> Can we specify “any suitable/availble” interrupt in a resource override
> INF section?
>
> Background: I need to add another BAR window to a PCI device, but leave
> it’s IRQ assignment as is.
> However, the IRQ must be specified as well - otherwise I don’t get any.
>
> Below is my override section:
>
> [VMEBRIDGE.NTx86.LogConfigOverride]
> LogConfig=VMEB_M2
>
> [VMEB_M2]
> ConfigPriority=DESIRED
> MemConfig=dc000000-dc000FFF(DRW) ; existing window
> MemConfig=200000@00000000-FFFFFFFF(DRW) ; additional window
> IRQConfig=LS:24
>
> The IRQ 24 is what Windows (or BIOS?) would assign automatically, without
> override.
> If I specfify any other value, it fails with problem 12.
>
> So, is there any syntax like IRQConfig=* or IRQConfig=LS:1-256 just to
> let Windows to assign what it wants,
> or the only allowed is
> IRQConfig=1,2,3,4,5…etc…255(?)
>
> Regards,
> Pavel
>
>
>

4

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
>> The IRQ 24 is what Windows (or BIOS?) would assign automatically,
>> without
>> override.
>> If I specfify any other value, it fails with problem 12.
>
> Strange. Can you omit IRQConfig at all?

Without IRQConfig I get no interrupt at all.
Ok, will try FilterResourceRequirements. A bit more work than couple of
lines in the INF

–pa