linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "selvamuthukumar v" <v.selvamuthukumar@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: MPC8313 ERDB has proper interrupt mapping for TSEC?
Date: Mon, 14 Jul 2008 17:44:38 +0530	[thread overview]
Message-ID: <790896390807140514r6074ec7j6d3eaf38787e3444@mail.gmail.com> (raw)

From, arch/powerpc/boot/dts/mpc8313erdb.dts,

212                 enet0: ethernet@24000 {
                                   .
                                   .
219                         interrupts = <37 0x8 36 0x8 35 0x8>;
                                   .
                                   .
222                 };
223
224                 enet1: ethernet@25000 {
                                   .
                                   .
231                         interrupts = <34 0x8 33 0x8 32 0x8>;
                                   .
234                 };
235

But as per 8313 Reference manual interrups 32, 33, 34 are for
TSEC1@24000 and 35, 36, 37 are for TSEC2@25000. Any idea why interrupt
numbers are swapped for enet0 and enet1?

-- 
Selva

             reply	other threads:[~2008-07-14 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 12:14 selvamuthukumar v [this message]
2008-07-15 22:11 ` MPC8313 ERDB has proper interrupt mapping for TSEC? Kumar Gala

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=790896390807140514r6074ec7j6d3eaf38787e3444@mail.gmail.com \
    --to=v.selvamuthukumar@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).