Hi Ben,
On Tue, Mar 04, 2008 at 08:41:33AM +1100, Benjamin Herrenschmidt wrote:
>
> > Thanks
> >
> > The following seems important also :
> >
> > /*
> > interrupts = <18 2>;
> > */
> > /* interrupts number are coded in hexa ! */
> > interrupts = <12 2 19 2 1a 2 1b 2 35 2 36 2 37 2>;
> >
> > I have replaced the interrupts spec in comments by the longer interrupts
> > spec
> > below, and it seems to have some positive effect, but I do not know
> > precisely what I have described there.
> >
> > I know that 25, 26, 27, 53, 54 and 55 decimal i(hence 19, 1a etc...) are the
> > interrupts numbers that I had in the ARCH=ppc version. I added 18 because
> > of the error message, but it did not help.
>
> Where is this ? (What node ?) The above looks like the interrupt spec
> for a single device with 7 interrupts, is that what you are trying to
> do ?
Well, the yenta device is a multi-function PCI peripheral that has two
pcmcia/pccard/compactflash slots and one ohci1394 interface.
Here's what uboot shows :
PCI Scan: Found Bus 0, Device 18, Function 0
00 12 104c ac46 0607 ff
PCI Scan: Found Bus 0, Device 18, Function 1
00 12 104c ac46 0607 ff
PCI Scan: Found Bus 0, Device 18, Function 2
00 12 104c 802a 0c00 00
and here is what /proc/interrupts shows in my ARCH=ppc dts-less running linux :
root:~# cat /proc/interrupts
CPU0
25: 0 OpenPIC Level gfar_interrupt
26: 245 OpenPIC Level serial
27: 0 OpenPIC Level i2c-mpc
55: 18797 OpenPIC Level yenta, ide0
54: 1 OpenPIC Level yenta
55: 79 OpenPIC Level ohci1394
BAD: 0
>
> If not, then it's incorrect, you have to figure the interrupt-map out
> (it's really not -that- hard).
If I knew where to look at, and what I must produce, I'd agree with you :)
Philippe
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
