Parameter of Hal

NTDEV
1

Hi all

the DDK function HalGetInterruptVector includes a Parameter
BusInterruptVector. In the book from G. Viscarola i found that for
ISA-devices, this parameter is not used. But what does it mean for PCI
devices.

Thanks for any help

F.X.Mayer

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

It means you pass the vector of the interrupt returned to you in the
CM_PARTIAL_RESOURCE_DESCRIPTOR.

Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731

-----Original Message-----
From: F.X. Mayer [mailto:xxxxx@fxm.de]
Sent: Sunday, December 09, 2001 3:15 AM
To: NT Developers Interest List
Subject: [ntdev] Parameter of Hal

Hi all

the DDK function HalGetInterruptVector includes a Parameter
BusInterruptVector. In the book from G. Viscarola i found that for
ISA-devices, this parameter is not used. But what does it mean for PCI
devices.

Thanks for any help

F.X.Mayer

You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

It’s not used. It doesn’t mean anything for PCI devices.

In fact, the combination of a bus number, a device number and a function
number uniquely identify a PCI interrupt. So there is no reason for a
driver try to interpret its interrupt at all.

With that said, this is an obsolete API. Don’t use if you aren’t
targetting your driver at old versions of Windows NT. Your WDM
IRP_MN_START_DEVICE gives you the same information that this API does,
but without using a bus number. And it’s important to get the concept
of bus number out of driver code, since the Plug and Play system may
change the bus number at any time.

Jake Oshins
(author of HalGetInterruptVector in most exising HALs)

-----Original Message-----
Subject: Parameter of Hal
From: “F.X. Mayer”
Date: Sun, 9 Dec 2001 12:14:37 +0100
X-Message-Number: 1

Hi all

the DDK function HalGetInterruptVector includes a Parameter
BusInterruptVector. In the book from G. Viscarola i found that for
ISA-devices, this parameter is not used. But what does it mean for PCI
devices.

Thanks for any help

F.X.Mayer

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Jake

thank you for help. The driver is for NT 4.0, so I have to use this obsolete
API.

F.X.Mayer

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jake Oshins
Sent: Monday, December 10, 2001 11:03 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Parameter of Hal

It’s not used. It doesn’t mean anything for PCI devices.

In fact, the combination of a bus number, a device number and a function
number uniquely identify a PCI interrupt. So there is no reason for a
driver try to interpret its interrupt at all.

With that said, this is an obsolete API. Don’t use if you aren’t
targetting your driver at old versions of Windows NT. Your WDM
IRP_MN_START_DEVICE gives you the same information that this API does,
but without using a bus number. And it’s important to get the concept
of bus number out of driver code, since the Plug and Play system may
change the bus number at any time.

Jake Oshins
(author of HalGetInterruptVector in most exising HALs)

-----Original Message-----
Subject: Parameter of Hal
From: “F.X. Mayer”
> Date: Sun, 9 Dec 2001 12:14:37 +0100
> X-Message-Number: 1
>
> Hi all
>
> the DDK function HalGetInterruptVector includes a Parameter
> BusInterruptVector. In the book from G. Viscarola i found that for
> ISA-devices, this parameter is not used. But what does it mean for PCI
> devices.
>
> Thanks for any help
>
> F.X.Mayer
>
> —
> You are currently subscribed to ntdev as: xxxxx@fxm.de
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com