From: Armin <akuster@pacbell.net>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EP405 PCI interrupt mapping
Date: Sun, 24 Feb 2002 20:38:14 +0000 [thread overview]
Message-ID: <3C794F36.2040400@pacbell.net> (raw)
In-Reply-To: 20020225014743.GD15788@zax
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/
next prev parent reply other threads:[~2002-02-24 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 1:47 EP405 PCI interrupt mapping David Gibson
2002-02-24 20:38 ` Armin [this message]
2002-02-25 19:06 ` Matthew Locke
2002-02-25 23:19 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C794F36.2040400@pacbell.net \
--to=akuster@pacbell.net \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).