RE: pci device support on nt4 (sp6) - more issues (windbg ...)

NTDEV
1

I have finished the coding, but I have the following questions:

  1. how to run the source level debugging? The host is win2k win windbg
    (5.00.2195.11), and the target (the one with the testing hw) is running nt
    4.0 (sp6)?

  2. How NT 4.0 handles shared IRQ for multiple PCI devices? I have boardA
    and boardB share the same irq. When I run A its OK, but when I run B I get
    The blue screen.

Thanks

From: Gary Little
>Reply-To: “NT Developers Interest List”
>To: “NT Developers Interest List”
>Subject: [ntdev] RE: pci device support on nt4 (sp6)
>Date: Mon, 9 Jul 2001 10:04:39 -0700
>
>Under NT 4 forget ISAPNP. NT 4 does not support PnP natively. For multiple
>devices on the PCI bus you call HalGetBusData until you have found all of
>your devices. You also call HalAssignSlotResources for each device you
>find.
>
>I would suggest you get INF-Tools to build your INF files. It makes life in
>the wonderful world of drivers much easier. Costs $40 and is faster,
>cheaper, and has less bulk than InstallShield.
>
>Gary G. Little
>Staff Engineer
>Broadband Storage, Inc.
>xxxxx@broadstor.com
>
>-----Original Message-----
>From: Ta H. [mailto:xxxxx@hotmail.com]
>Sent: Saturday, July 07, 2001 10:27 PM
>To: NT Developers Interest List
>Subject: [ntdev] pci device support on nt4 (sp6)
>
>1). How NT4 supports multiple PCI instances? Anything the driver needs to
>do so that can be done? I was told there’s ISAPNP for the limited PnP
>support. Is it helpful for my case? I know for WDM drivers, you can put
>PCI\VEN_XXXX&DEV_YYYY in their inf. Is it supported in NT4?
>
>2). Now I manually edit the registry to install the driver. I’d
>appreciate
>if someone can show me a sample oemsetup.inf for a PCI device. My device
>is
>a multimedia device (not audio though).
>
>Thanks
>
>Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
>—
>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: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


Get your FREE download of MSN Explorer at http://explorer.msn.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

2

> 1) how to run the source level debugging? The host is win2k win windbg

(5.00.2195.11), and the target (the one with the testing hw) is running nt
4.0 (sp6)?

Use more recent WinDbg - this one is broken and extremely buggy.
It can be downloaded from www.microsoft.com/ddk/debugging

  1. How NT 4.0 handles shared IRQ for multiple PCI devices? I have boardA
    and boardB share the same irq. When I run A its OK, but when I run B I
    get
    The blue screen.

Your ISR must immediately determine whether it is really your board which
asserted the IRQ (by reading the board’s registers) and return FALSE ASAP if
it is not so.
It must return TRUE in all other cases.

This (and correct hardware) is enough for things to get working on NT.

Max

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