From: David Gardiner <daveg@sonartech.com.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: powerpc with gigabit card hanging
Date: Tue, 28 Sep 2004 13:41:28 +1000 [thread overview]
Message-ID: <4158DD68.2060707@sonartech.com.au> (raw)
In-Reply-To: <AE8972FB-0E3A-11D9-BC8B-000A95A4DC02@kernel.crashing.org>
> 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!
dmesg from 2.6 series:
Broadcom Gigabit Ethernet Driver bcm5700 with Broadcom NIC Extension
(NICE) ver. 7.3.5 (06/23/04)
eth2: Broadcom BCM5704 1000Base-SX found at mem f2ef0000, IRQ 0, node
addr 0030f76e4eee
eth2: Broadcom BCM5704 Integrated SerDes transceiver found
eth2: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON,
802.1Q VLAN ON, TSO ON
eth3: Broadcom BCM5704 1000Base-SX found at mem f2ed0000, IRQ 0, node
addr 0030f76e4eef
eth3: Broadcom BCM5704 Integrated SerDes transceiver found
eth3: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON,
802.1Q VLAN ON, TSO ON
dmesg from 2.4 series:
Broadcom Gigabit Ethernet Driver bcm5700 with Broadcom NIC Extension
(NICE) ver. 7.1.22 (01/07/04)
eth2: Broadcom BCM5704 1000Base-T found at mem f2ef0000, IRQ 12, node
addr 0030f74d479c
eth2: Broadcom BCM5704 Integrated Copper transceiver found
eth2: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON,
802.1Q VLAN ON, NAPI ON
eth3: Broadcom BCM5704 1000Base-T found at mem f2ee0000, IRQ 9, node
addr 0030f74d479d
eth3: Broadcom BCM5704 Integrated Copper transceiver found
eth3: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON,
802.1Q VLAN ON, NAPI ON
next prev parent reply other threads:[~2004-09-28 3:40 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 [this message]
2004-09-28 5:13 ` Matt Porter
[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=4158DD68.2060707@sonartech.com.au \
--to=daveg@sonartech.com.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).