* Re: EP405 PCI interrupt mapping
2002-02-25 1:47 EP405 PCI interrupt mapping David Gibson
@ 2002-02-24 20:38 ` Armin
2002-02-25 19:06 ` Matthew Locke
1 sibling, 0 replies; 4+ messages in thread
From: Armin @ 2002-02-24 20:38 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-embedded
David Gibson wrote:
> 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.
>
> --
> David Gibson | For every complex problem there is a
> david@gibson.dropbear.id.au | 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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* EP405 PCI interrupt mapping
@ 2002-02-25 1:47 David Gibson
2002-02-24 20:38 ` Armin
2002-02-25 19:06 ` Matthew Locke
0 siblings, 2 replies; 4+ messages in thread
From: David Gibson @ 2002-02-25 1:47 UTC (permalink / raw)
To: linuxppc-embedded
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.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | 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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: EP405 PCI interrupt mapping
2002-02-25 1:47 EP405 PCI interrupt mapping David Gibson
2002-02-24 20:38 ` Armin
@ 2002-02-25 19:06 ` Matthew Locke
2002-02-25 23:19 ` David Gibson
1 sibling, 1 reply; 4+ messages in thread
From: Matthew Locke @ 2002-02-25 19:06 UTC (permalink / raw)
To: David Gibson; +Cc: linuxppc-embedded
David Gibson wrote:
>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;)
>
>--
>David Gibson | For every complex problem there is a
>david@gibson.dropbear.id.au | 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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: EP405 PCI interrupt mapping
2002-02-25 19:06 ` Matthew Locke
@ 2002-02-25 23:19 ` David Gibson
0 siblings, 0 replies; 4+ messages in thread
From: David Gibson @ 2002-02-25 23:19 UTC (permalink / raw)
To: linuxppc-embedded
On Mon, Feb 25, 2002 at 11:06:53AM -0800, Matthew Locke wrote:
>
> David Gibson wrote:
>
> >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
david@gibson.dropbear.id.au | 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/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-02-25 23:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-25 1:47 EP405 PCI interrupt mapping David Gibson
2002-02-24 20:38 ` Armin
2002-02-25 19:06 ` Matthew Locke
2002-02-25 23:19 ` David Gibson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).