Re: Windows PCI devices... (and Code 12) resolved...

NTDEV
1

Peter W. Morreale wrote:

Thanks for the inspiration Russ.

We needed to add an interrupt pin in our PCI configuration for Windows
to be happy.

My driver now installs and loads and locates its resources. Greatly
appreciate all the help.

I love happy endings. It’s interesting that there was such a simple
solution for what seemed like an incredibly vexing problem.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

2

I am smack dab in the middle of a design of a huge turnkey system that
involves many PCIe switches and endpoints, so I have had to get used to
“interpreting” the PCI specs from several different angles.

I don’t know as much about the Windows internals though, we are using
Linux, but a lot of the principles are similar (and some are quite
different!).

Russ Poffenberger
xxxxx@ltx-credence.com

From:
“Peter W. Morreale”
To:
“Windows System Software Devs Interest List”
Date:
11/24/2009 05:23 PM
Subject:
Re: Re:[ntdev] Windows PCI devices… (and Code 12) resolved…
Sent by:


Thanks for the inspiration Russ.

We needed to add an interrupt pin in our PCI configuration for Windows
to be happy.

My driver now installs and loads and locates its resources. Greatly
appreciate all the help.

Best,
-PWM

On Tue, 2009-11-24 at 19:44 +0000, Peter W. Morreale wrote:
> On Tue, 2009-11-24 at 11:21 -0800, xxxxx@ltx-credence.com
> wrote:
> >
> > Peter,
> >
> > I don’t think it is quite that clear. The spec states “Therefore,
> > system configuration software must not assume that a message capable
> > device has an interrupt pin”
> >
> > The key here is “System Configuration Software” which would be the
> > BIOS and operating system. If you had full control of the behavior of
> > these two then you could make the assumption, but you don’t have
> > control over them and have to work with what is given you.
> >
> > You have to understand that parts of the spec are written more for the
> > benefit of the system designer rather than the device or driver
> > developer.
> >
> Ahhh… Thank you Russ. This was very helpful.
>
>
> Best,
> -PWM
>
>
>
> > Russ Poffenberger
> > xxxxx@ltx-credence.com
> >
> >
> >
> > From:
> > “Peter W. Morreale”
> >
> > To:
> > “Windows System Software Devs
> > Interest List”
> >
> > Date:
> > 11/24/2009 10:59 AM
> > Subject:
> > Re: Re:[ntdev] Windows PCI
> > devices…
> > Sent by:
> >
> >
> >
> > ______________________________________________________________________
> >
> >
> >
> > Hi Pavel;
> >
> >
> > The PCI standard is quite clear (section 6.8, paragraph 3) that
> > devices
> > can present MSI and not require/need a line based interrupt (INT#).
> > If
> > Win7 adheres to that standard, then perhaps our config data and/or
> > bios
> > is at issue.
> >
> >
> > Thanks,
> > -PWM
> >
> >
> >
> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
> > and other seminars visit: http://www.osr.com/seminars To unsubscribe,
> > visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer