PCI driver on EB8347
Rajan.Rai at ingenient.com
Sat Aug 12 22:34:00 EST 2006
Thanks IRQ problem is resolved. As pointed out it was problem
with IRQ IDSEL mapping. Mapping needs to be different on Eval board I'm
using and our custom design. But my driver is still not working on our
custom design. PCI device doesn't receive any messages from MPC8347 on
our custom design mother board which uses pci-bridge where as it works
fine on Eval board which doesn't use PCI bridge.
I guess problem lies at the kernel level and
not the driver. Any tips apart from IDSEL IRQ settings at kernel level
what else I need to change when I move from 1 mother board to another.
My PCI devices do get base address 0 and 1 allocated properly by the
OS. But when I try to write any messages on those addresses PCI device
doesn't see them
Kumar Gala wrote:
> On Aug 11, 2006, at 4:15 AM, rajan rai wrote:
>> I'm using polling mechanism and not interrupts
>> in my driver. Although I'm not using polling I see strange behavior
>> When I do lspci -v I don't see any interrupts being allocated to PCI
>> device behind PCI bridge !!!! But when I use same card directly on
>> primary bus I do see interrupt being allocated to PCI device. Any
>> advise why IRQ's being not allocated in case its attached to PCI
>> bridge ?
>> Do I need to take care of any extra
>> configuration in case of PCI card is attached to PCI bridge ?
> You need to make sure that the pci_map_irq/mpc83xx_map_irq function
> handles the right swizziling for the P2P bridge for your setup. If
> you are just connected directly its pretty straight forward. However
> IRQ assignment behind the bridge can be very board specific and so you
> need to make sure that the code is doing the right think for you.
> What ever strangeness do you see from lspci?
> - k
More information about the Linuxppc-embedded