* MPC8313 ERDB has proper interrupt mapping for TSEC?
@ 2008-07-14 12:14 selvamuthukumar v
2008-07-15 22:11 ` Kumar Gala
0 siblings, 1 reply; 2+ messages in thread
From: selvamuthukumar v @ 2008-07-14 12:14 UTC (permalink / raw)
To: linuxppc-embedded
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
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: MPC8313 ERDB has proper interrupt mapping for TSEC?
2008-07-14 12:14 MPC8313 ERDB has proper interrupt mapping for TSEC? selvamuthukumar v
@ 2008-07-15 22:11 ` Kumar Gala
0 siblings, 0 replies; 2+ messages in thread
From: Kumar Gala @ 2008-07-15 22:11 UTC (permalink / raw)
To: selvamuthukumar v; +Cc: linuxppc-embedded
On Jul 14, 2008, at 7:14 AM, selvamuthukumar v wrote:
> 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?
I believe different revisions of the part had different mappings.
- k
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-07-15 22:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-14 12:14 MPC8313 ERDB has proper interrupt mapping for TSEC? selvamuthukumar v
2008-07-15 22:11 ` Kumar Gala
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).