netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: netdev@vger.kernel.org, linuxppc64-dev@ozlabs.org
Subject: Re: GigE on PowerMac G5
Date: Sun, 05 Mar 2006 08:16:40 +1100	[thread overview]
Message-ID: <1141507000.17127.4.camel@localhost.localdomain> (raw)
In-Reply-To: <jebqwmfeh9.fsf@sykes.suse.de>

On Sat, 2006-03-04 at 15:53 +0100, Andreas Schwab wrote:
> [Sorry for duplicate posting, I've used the wrong list address.]
> 
> I suppose the NIC in the PowerMac G5 can do GigE, yet when plugged into a
> GB switch it is only willing to talk 100MB with it.  Any idea why?  Kernel
> is 2.6.16-rc5-git2.

Works for me... Must be a problem with auto-neg and your switch, or the
cable.... Can you check how the switch is configured maybe ? You can
also try forcing the link speed with ethtool.

Ben.
 
> # lsprop /proc/device-tree/ht@0,f2000000/pci@6/ethernet@f
> name             "ethernet"
> linux,phandle    ff9c53d8
> interrupt-parent ff9779b0
> gbit-phy        
> assigned-addresses 82047810 00000000 80400000 00000000 00200000
>                  82047830 00000000 80300000 00000000 00100000
> local-mac-address 00 0a 95 ba b8 70                              .....p
> stats            00000000 00000000 00000000 00000000 00000000
> reg              00047800 00000000 00000000 00000000 00000000
>                  02047810 00000000 00000000 00000000 00020000
>                  02047830 00000000 00000000 00000000 00010000
> max-frame-size   000005ee (1518)
> address-bits     00000030 (48)
> built-in        
> compatible       "K2-GMAC"
> category         "net"
> removable        "network"
> network-type     "ethernet"
> device_type      "network"
> fast-back-to-back
> devsel-speed     00000002
> max-latency      00000040 (64)
> min-grant        00000040 (64)
> interrupts       00000029 00000001
> class-code       00020000 (131072)
> revision-id      00000000
> device-id        0000004c (76)
> vendor-id        0000106b (4203)
> # ethtool eth0
> Settings for eth0:
>         Supported ports: [ TP MII ]
>         Supported link modes:   10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>                                 1000baseT/Half 1000baseT/Full 
>         Supports auto-negotiation: Yes
>         Advertised link modes:  10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>                                 1000baseT/Half 1000baseT/Full 
>         Advertised auto-negotiation: No
>         Speed: 100Mb/s
>         Duplex: Full
>         Port: MII
>         PHYAD: 0
>         Transceiver: external
>         Auto-negotiation: on
>         Supports Wake-on: g
>         Wake-on: d
>         Current message level: 0x00000007 (7)
>         Link detected: yes
> 
> Andreas.
> 

  reply	other threads:[~2006-03-04 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-04 14:53 GigE on PowerMac G5 Andreas Schwab
2006-03-04 21:16 ` Benjamin Herrenschmidt [this message]
2006-03-06 10:40   ` Andreas Schwab
2006-03-06 13:15     ` Benjamin Herrenschmidt
2006-03-07 12:53       ` Andreas Schwab
2006-03-13 14:49         ` Andreas Schwab
2006-03-04 23:36 ` Paul Mackerras

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=1141507000.17127.4.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=schwab@suse.de \
    /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).