Skip to contentSkip to conversation

EP405 PCI interrupt mapping

DISCUSSION David Gibson 3 participants 4 messages Feb 24, 2002 – Feb 25, 2002

lore
Share & tools
lore
#1 lore raw
In reply to David Gibson
Quoted 5 lines · David Gibson

Is the current PCI interrupt mapping stuff for the EP405 (i.e. ppc405_map_irq() in ep405.c) expected to work, or has it just been copied from walnut and never updated for ep405? It looks bogus to me.

Quoted 10 lines

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

AFAIK it was just copied.

--armin

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#2 lore raw
Quoted 5 lines · David Gibson

Is the current PCI interrupt mapping stuff for the EP405 (i.e. ppc405_map_irq() in ep405.c) expected to work, or has it just been copied from walnut and never updated for ep405? It looks bogus to me.

I just copied it from the walnut. I didn't get that far. I was told you were going to make it all work;)

Quoted 9 lines

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#3 lore raw
Quoted 11 lines · Matthew Locke
Quoted 5 lines · David Gibson

Is the current PCI interrupt mapping stuff for the EP405 (i.e. ppc405_map_irq() in ep405.c) expected to work, or has it just been copied from walnut and never updated for ep405? It looks bogus to me.

I just copied it from the walnut. I didn't get that far. I was told you were going to make it all work;)

Fair enough. I'll get onto that then shall I :-)

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/