I’m trying to figure out how to tie in an interrupt generated by my
hardware, to my NDIS driver.
I see callbacks for HandleInterruptHandler and ISRHandler. Which one is my
ISR routine? What’s the other one?
And finally, how do I go about registering my driver for my specific
interrupt?
If all of this information is in the DDK somewhere, (or anywhere else for
that matter), and you can point me to it, I’d appreciate it. Otherwise,
any help you can provide is appreciated.
Brian
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
You ISR handler is defined by the NDIS_MINIPORT_CHARACTERISTICS that you
send down with NdisMRegisterMiniport().
Characteristics.HandleInterruptHandler = Function_Name;
Dennis Merrill
Embedded Systems Engineer
Thermo Electron Corporation
Spectroscopy Division
-----Original Message-----
From: Brian Franklin [mailto:xxxxx@hotmail.com]
Sent: Thursday, January 24, 2002 6:00 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS miniport with ISR on WinXP
I’m trying to figure out how to tie in an interrupt generated by my
hardware, to my NDIS driver.
I see callbacks for HandleInterruptHandler and ISRHandler. Which one is my
ISR routine? What’s the other one?
And finally, how do I go about registering my driver for my specific
interrupt?
If all of this information is in the DDK somewhere, (or anywhere else for
that matter), and you can point me to it, I’d appreciate it. Otherwise,
any help you can provide is appreciated.
Brian
You are currently subscribed to ntdev as: xxxxx@thermonicolet.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
Not quite. The ISRHandler is your interrupt handler. The
HandleInterruptHandler is your DPC.
Don’t forget to register your interrupt with NdisMRegisterInterrupt!
Scott
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
Never mind. I think I found it. I don’t know why it didn’t occur to me to
look up HandleInterruptHandler under MiniportHandleInterrupt.
This eventually also led me to NdisMRegisterInterrupt.
I’m on my way. But, I’m never one to turn down an actual example, if
someone has one.
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
Oops - meant DPC handler… Sorry!
Dennis Merrill
Embedded Systems Engineer
Thermo Electron Corporation
Spectroscopy Division
-----Original Message-----
From: xxxxx@thermonicolet.com [mailto:xxxxx@thermonicolet.com]
Sent: Friday, January 25, 2002 3:20 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS miniport with ISR on WinXP
You ISR handler is defined by the NDIS_MINIPORT_CHARACTERISTICS that you
send down with NdisMRegisterMiniport().
Characteristics.HandleInterruptHandler = Function_Name;
Dennis Merrill
Embedded Systems Engineer
Thermo Electron Corporation
Spectroscopy Division
-----Original Message-----
From: Brian Franklin [mailto:xxxxx@hotmail.com
mailto:xxxxx ]
Sent: Thursday, January 24, 2002 6:00 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS miniport with ISR on WinXP
I’m trying to figure out how to tie in an interrupt generated by my
hardware, to my NDIS driver.
I see callbacks for HandleInterruptHandler and ISRHandler. Which one is my
ISR routine? What’s the other one?
And finally, how do I go about registering my driver for my specific
interrupt?
If all of this information is in the DDK somewhere, (or anywhere else for
that matter), and you can point me to it, I’d appreciate it. Otherwise,
any help you can provide is appreciated.
Brian
—
You are currently subscribed to ntdev as: xxxxx@thermonicolet.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@thermonicolet.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</mailto:xxxxx>
Check the samples in the DDK under “\src\network\ndis”. There are
quite a few. W2K DDK is available for free download from:
http://www.microsoft.com/ddk/
Stephan
—
On Fri, 25 Jan 2002 16:51:54, “Brian Franklin”
wrote:
>
>Never mind. I think I found it. I don’t know why it didn’t occur to me to
>look up HandleInterruptHandler under MiniportHandleInterrupt.
>This eventually also led me to NdisMRegisterInterrupt.
>I’m on my way. But, I’m never one to turn down an actual example, if
>someone has one.
—
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