Hi there,
Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
Windows 2003 servers.
I have been reading contradictory statements that Message Signaled Interrupt
(MSI) has been supported in Windows 2000/2003, but the neither of these DDK
document has IoConnectInterruptEx() API.
Regards
Don’t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
I think none of 2000/2003 has this. To best of my knowledge,
IoConnectInterruptEx was planned to add somewhere after Windows 2003 release
(if I am right then I read about IoConnectInterruptEx in one if NT insider
paper).
Regards,
Dev
-----Original Message-----
From: Bill Wells [mailto:xxxxx@hotmail.com]
Sent: Wednesday, November 24, 2004 6:40 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] IoConnectInterruptEx in Windows 2000/2003
Hi there,
Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
Windows 2003 servers.
I have been reading contradictory statements that Message Signaled Interrupt
(MSI) has been supported in Windows 2000/2003, but the neither of these DDK
document has IoConnectInterruptEx() API.
Regards
Don’t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: dsingh@in.safenet-inc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
RE: [ntdev] IoConnectInterruptEx in Windows 2000/2003The whole story is that
we’re providing a library that will allow you to use IoConnectInterruptEx (a
stub version) with down-level systems. This won’t give you MSI support.
That’s only in Longhorn. (It’s a fairly large piece of work and the release
management crew decided it was too risky for a backport to Server 2003.)
But it will simplify the driver that you’re trying to write that needs to
detect whether or not MSI is supported and act differently based on whether
you find support. The library will take care of almost all of that.
–
Jake Oshins
Windows Kernel Group
Engineer behind the MSI suppport in Longhorn
This posting is provided “AS IS” with no warranties, and confers no rights.
wrote in message news:xxxxx@ntdev…
I think none of 2000/2003 has this. To best of my knowledge,
IoConnectInterruptEx was planned to add somewhere after Windows 2003 release
(if I am right then I read about IoConnectInterruptEx in one if NT insider
paper).
Regards,
Dev
-----Original Message-----
From: Bill Wells [mailto:xxxxx@hotmail.com]
Sent: Wednesday, November 24, 2004 6:40 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] IoConnectInterruptEx in Windows 2000/2003
Hi there,
Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
Windows 2003 servers.
I have been reading contradictory statements that Message Signaled Interrupt
(MSI) has been supported in Windows 2000/2003, but the neither of these DDK
document has IoConnectInterruptEx() API.
Regards
- Bill
_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: dsingh@in.safenet-inc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks Jake
That means is it correct to assume that from the interrupt point of view,
for Windows 2000/2003, PCI Express device must be consider as PCI device
with line based interrupt… ?
Regards
From: “Jake Oshins”
>Reply-To: “Windows System Software Devs Interest List”
>
>To: “Windows System Software Devs Interest List”
>Subject: Re:[ntdev] IoConnectInterruptEx in Windows 2000/2003
>Date: Mon, 29 Nov 2004 10:27:18 -0800
>
>RE: [ntdev] IoConnectInterruptEx in Windows 2000/2003The whole story is
>that
>we’re providing a library that will allow you to use IoConnectInterruptEx
>(a
>stub version) with down-level systems. This won’t give you MSI support.
>That’s only in Longhorn. (It’s a fairly large piece of work and the
>release
>management crew decided it was too risky for a backport to Server 2003.)
>But it will simplify the driver that you’re trying to write that needs to
>detect whether or not MSI is supported and act differently based on whether
>you find support. The library will take care of almost all of that.
>
>–
>Jake Oshins
>Windows Kernel Group
>Engineer behind the MSI suppport in Longhorn
>
>This posting is provided “AS IS” with no warranties, and confers no rights.
>
>
> wrote in message news:xxxxx@ntdev…
>I think none of 2000/2003 has this. To best of my knowledge,
>IoConnectInterruptEx was planned to add somewhere after Windows 2003
>release
>(if I am right then I read about IoConnectInterruptEx in one if NT insider
>paper).
>Regards,
>Dev
>-----Original Message-----
>From: Bill Wells [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, November 24, 2004 6:40 AM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] IoConnectInterruptEx in Windows 2000/2003
>
>
>Hi there,
>Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
>Windows 2003 servers.
>I have been reading contradictory statements that Message Signaled
>Interrupt
>(MSI) has been supported in Windows 2000/2003, but the neither of these DDK
>document has IoConnectInterruptEx() API.
>Regards
>- Bill
>
>Don’t just search. Find. Check out the new MSN Search!
>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>You are currently subscribed to ntdev as: dsingh@in.safenet-inc.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
FREE pop-up blocking with the new MSN Toolbar – get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
Yes.
–
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no rights.
“Bill Wells” wrote in message
news:xxxxx@ntdev…
> Thanks Jake
>
> That means is it correct to assume that from the interrupt point of view,
> for Windows 2000/2003, PCI Express device must be consider as PCI device
> with line based interrupt… ?
>
> Regards
> - Bill
>
>>From: “Jake Oshins”
>>Reply-To: “Windows System Software Devs Interest List”
>>
>>To: “Windows System Software Devs Interest List”
>>Subject: Re:[ntdev] IoConnectInterruptEx in Windows 2000/2003
>>Date: Mon, 29 Nov 2004 10:27:18 -0800
>>
>>RE: [ntdev] IoConnectInterruptEx in Windows 2000/2003The whole story is
>>that
>>we’re providing a library that will allow you to use IoConnectInterruptEx
>>(a
>>stub version) with down-level systems. This won’t give you MSI support.
>>That’s only in Longhorn. (It’s a fairly large piece of work and the
>>release
>>management crew decided it was too risky for a backport to Server 2003.)
>>But it will simplify the driver that you’re trying to write that needs to
>>detect whether or not MSI is supported and act differently based on
>>whether
>>you find support. The library will take care of almost all of that.
>>
>>–
>>Jake Oshins
>>Windows Kernel Group
>>Engineer behind the MSI suppport in Longhorn
>>
>>This posting is provided “AS IS” with no warranties, and confers no
>>rights.
>>
>>
>> wrote in message news:xxxxx@ntdev…
>>I think none of 2000/2003 has this. To best of my knowledge,
>>IoConnectInterruptEx was planned to add somewhere after Windows 2003
>>release
>>(if I am right then I read about IoConnectInterruptEx in one if NT insider
>>paper).
>>Regards,
>>Dev
>>-----Original Message-----
>>From: Bill Wells [mailto:xxxxx@hotmail.com]
>>Sent: Wednesday, November 24, 2004 6:40 AM
>>To: Windows System Software Devs Interest List
>>Subject: [ntdev] IoConnectInterruptEx in Windows 2000/2003
>>
>>
>>Hi there,
>>Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
>>Windows 2003 servers.
>>I have been reading contradictory statements that Message Signaled
>>Interrupt
>>(MSI) has been supported in Windows 2000/2003, but the neither of these
>>DDK
>>document has IoConnectInterruptEx() API.
>>Regards
>>- Bill
>>
>>Don’t just search. Find. Check out the new MSN Search!
>>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>>
>>
>>—
>>Questions? First check the Kernel Driver FAQ at
>>http://www.osronline.com/article.cfm?id=256
>>You are currently subscribed to ntdev as: dsingh@in.safenet-inc.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>>—
>>Questions? First check the Kernel Driver FAQ at
>>http://www.osronline.com/article.cfm?id=256
>>
>>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> FREE pop-up blocking with the new MSN Toolbar - get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
Yes.
MSI support will be in Longhorn only.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Bill Wells”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, November 30, 2004 8:04 PM
Subject: Re:[ntdev] IoConnectInterruptEx in Windows 2000/2003
> Thanks Jake
>
> That means is it correct to assume that from the interrupt point of view,
> for Windows 2000/2003, PCI Express device must be consider as PCI device
> with line based interrupt… ?
>
> Regards
> - Bill
>
> >From: “Jake Oshins”
> >Reply-To: “Windows System Software Devs Interest List”
> >
> >To: “Windows System Software Devs Interest List”
> >Subject: Re:[ntdev] IoConnectInterruptEx in Windows 2000/2003
> >Date: Mon, 29 Nov 2004 10:27:18 -0800
> >
> >RE: [ntdev] IoConnectInterruptEx in Windows 2000/2003The whole story is
> >that
> >we’re providing a library that will allow you to use IoConnectInterruptEx
> >(a
> >stub version) with down-level systems. This won’t give you MSI support.
> >That’s only in Longhorn. (It’s a fairly large piece of work and the
> >release
> >management crew decided it was too risky for a backport to Server 2003.)
> >But it will simplify the driver that you’re trying to write that needs to
> >detect whether or not MSI is supported and act differently based on whether
> >you find support. The library will take care of almost all of that.
> >
> >–
> >Jake Oshins
> >Windows Kernel Group
> >Engineer behind the MSI suppport in Longhorn
> >
> >This posting is provided “AS IS” with no warranties, and confers no rights.
> >
> >
> > wrote in message news:xxxxx@ntdev…
> >I think none of 2000/2003 has this. To best of my knowledge,
> >IoConnectInterruptEx was planned to add somewhere after Windows 2003
> >release
> >(if I am right then I read about IoConnectInterruptEx in one if NT insider
> >paper).
> >Regards,
> >Dev
> >-----Original Message-----
> >From: Bill Wells [mailto:xxxxx@hotmail.com]
> >Sent: Wednesday, November 24, 2004 6:40 AM
> >To: Windows System Software Devs Interest List
> >Subject: [ntdev] IoConnectInterruptEx in Windows 2000/2003
> >
> >
> >Hi there,
> >Any idea whether IoConnectInterruptEx be supported in Windows 2000 or
> >Windows 2003 servers.
> >I have been reading contradictory statements that Message Signaled
> >Interrupt
> >(MSI) has been supported in Windows 2000/2003, but the neither of these DDK
> >document has IoConnectInterruptEx() API.
> >Regards
> >- Bill
> >
> >Don’t just search. Find. Check out the new MSN Search!
> >http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >
> >
> >—
> >Questions? First check the Kernel Driver FAQ at
> >http://www.osronline.com/article.cfm?id=256
> >You are currently subscribed to ntdev as: dsingh@in.safenet-inc.com
> >To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> >
> >—
> >Questions? First check the Kernel Driver FAQ at
> >http://www.osronline.com/article.cfm?id=256
> >
> >You are currently subscribed to ntdev as: xxxxx@hotmail.com
> >To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> FREE pop-up blocking with the new MSN Toolbar – get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>