From: Matt Porter <mporter@kernel.crashing.org>
To: David Gardiner <daveg@sonartech.com.au>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: powerpc with gigabit card hanging
Date: Mon, 27 Sep 2004 22:13:23 -0700 [thread overview]
Message-ID: <20040927221323.A30581@home.com> (raw)
In-Reply-To: <4158DD68.2060707@sonartech.com.au>; from daveg@sonartech.com.au on Tue, Sep 28, 2004 at 01:41:28PM +1000
[Followups to linuxppc-embedded, this is an embedded port question]
On Tue, Sep 28, 2004 at 01:41:28PM +1000, David Gardiner wrote:
>
> > It's not the platform; I've run both e1000 and tg3 successfully
> > on PowerPC systems, no problems getting it to work at all.
> >
> What kernel are you using? it's just that the irq's I'm getting for the
> gigabit devices are zero (dual gigabit ethernet card) for the 2.6.9-rc2
> plus patchs kernel but for the 2.4 series I was getting 12 and 9 as can
> be seen below and configuring the devices worked fine. I've also noticed
> that there have been recent changes made to the irq routing in the
> kernel so this may have something to do with it so I'll try one the
> i386's with gigabit with the 2.6.9-rc2 and see what I get!
What "changes made to the irq routing" have you noticed? Hopefully
not the i386-specific ACPI ones...
irqs for PCI devices do not come from the driver, they are platform
specific. If you are having problems with the interrupt reported
by xyz PCI driver then that is something wrong with your platform.
On pmac, interrupt routing is retrieved from OF. On prep, it's
retrieved from either residual data or in-kernel tables. If
embedded, then this is on the wrong list. Oops, looking at your
original message this appears to be the case (PowerPlus). Sounds
like the interrupt routing table for your board is wrong.
FWIW, e1000 works great here on my PowerPC platforms and 2.6.9-rc2
-Matt
next prev parent reply other threads:[~2004-09-28 5:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 4:32 powerpc with gigabit card hanging David Gardiner
2004-09-24 15:01 ` Segher Boessenkool
2004-09-28 3:41 ` David Gardiner
2004-09-28 5:13 ` Matt Porter [this message]
[not found] ` <C617C694-1110-11D9-8370-000A95A4DC02@kernel.crashing.org>
2004-09-28 5:48 ` Matt Porter
2004-09-28 5:58 ` Segher Boessenkool
2004-09-28 6:14 ` Matt Porter
2004-09-28 6:23 ` Segher Boessenkool
2004-09-28 6:37 ` Matt Porter
2004-09-28 6:45 ` Segher Boessenkool
2004-09-28 7:01 ` Matt Porter
2004-09-28 7:10 ` Segher Boessenkool
2004-09-28 6:46 ` David Gardiner
2004-09-28 6:59 ` Matt Porter
2004-09-28 22:45 ` David Gardiner
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=20040927221323.A30581@home.com \
--to=mporter@kernel.crashing.org \
--cc=daveg@sonartech.com.au \
--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).