> > Maybe your PCI interrupt-map is wrong... > > Is the PCI-interrupt map that part of the dts file : > > interrupt-map = < > > /* IDSEL 0x02 */ > 1000 0 0 1 &mpic 1 1 > 1000 0 0 2 &mpic 2 1 > 1000 0 0 3 &mpic 3 1 > 1000 0 0 4 &mpic 4 1 > > /* IDSEL 0x03 */ > 1800 0 0 1 &mpic 4 1 > 1800 0 0 2 &mpic 1 1 > 1800 0 0 3 &mpic 2 1 > 1800 0 0 4 &mpic 3 1 > > ... > > I do not understand anything there :(
It's documented in booting-without-of.txt afaik... The interrupt-map goes along with the interrupt-map-mask. The later defines which bits of the map are relevant. The first part of the map is 3 cells containing a PCI address, followed by a cell containing a PCI IRQ line (1=A....4=D). The next is the parent interrupt controller, followed by the IRQ specification, which for MPIC is the interrupt number on that controller, followed by an encoding of the interrupt polarity & trigger type (1 for level-low). The first part, the PCI address, has a special format, which should be documented as well in the document I pointed out. For readability, we ommited the top 16 bits of the first cell, which are the address type and bus number, mostly irrelevant for interrupt mapping. The next bits are the device/function. Usually only the device part is unmasked. Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
