Re: Driver gets dwIRQ = ffffffff, sysINtr = 00000000

The one in the platform will be built. Assuming it's the same name as the
one in the public tree it will override due to order of operations in
buildrel.

If you're getting a dwIRQ of 0xFFFFFFFF, that means your call to the OAL to
get the IRQ for this PCI slot failed. That typically means the OAL doesn't
know anything about this particular PCI location, or it could mean there is
no IRQ support for this device, or it could mean the OAL hasn't been written
to support PCI interrupts in general.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Nick" <spameater@xxxxxxxxxx> wrote in message
news:ezqtFiLXGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
Remi,

It's a custom platform based on PXA255. We have the CE 5.0 BSP from the
platform provider and are adding our PCI card to it so there is no BIOS.

The setting is commented out. I assume this means it will config but I
can change it and try again.

; "NoConfig"=dword:0

In addition, I have found PCIBUS in two places.

C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\PCIBUS
C:\WINCE500\PLATFORM\CM_X255_BSP\SRC\DRIVERS\PCIBUS

The DIRS files in the DRIVERS folder both define PCIBUS as a folder to
compile. How do I know that the one I want (presumably NOT the
public/common/oak/drivers/pcibus) is the one I get?

Thanks,
Nick.


"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> wrote in message
news:%23nnWftuWGHA.3864@xxxxxxxxxxxxxxxxxxxxxxx
Hi Nick,

Did the mechanisms for assigning resorces for either of these change
significantly from 4.2 to 5.0?

I am afraid it did.

What is your platform (do you have a BIOS that configures the PCI bus
for you)?
What is your [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI].NoConfig setting?

Finally, you should break at PCICfgDevice() in
Public\Common\Oak\Drivers\Pcibus\PCICFG.C to see what happens when it
comes to assign an IRQ to your device.

Good luck.
Remi





.

Relevant Pages