netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: brctl shows output for pegasus ethernet device?
Date: Thu, 01 May 2008 15:55:44 -0700	[thread overview]
Message-ID: <481A4A70.1040806@candelatech.com> (raw)

I was expecting brctl to fail in this case, but it shows data
for the pegasus USB ethernet device??

brctl version 1.2  (FC8)
kernel 2.6.25 plus hacks


[root@eepc ]# brctl showstp eth3
eth3
  bridge id              0000.000018000000
  designated root        0200.000004000000
  root port               255                    path cost               7664
  max age                   0.00                 bridge max age             0.00
  hello time                0.00                 bridge hello time          0.00
  forward delay             0.00                 bridge forward delay       0.00
  ageing time               0.00
  hello timer               0.00                 tcn timer               11346042.76
  topology change timer  32183585.20                     gc timer                32183588.56
  flags                  TOPOLOGY_CHANGE TOPOLOGY_CHANGE_DETECTED


[root@eepc ]# ethtool eth3
Settings for eth3:
         Supported ports: [ TP MII ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Supports auto-negotiation: Yes
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Advertised auto-negotiation: Yes
         Speed: 100Mb/s
         Duplex: Full
         Port: MII
         PHYAD: 1
         Transceiver: internal
         Auto-negotiation: on
         Supports Wake-on: pg
         Wake-on: d
         Current message level: 0x00000007 (7)
         Link detected: yes
[root@eepc ]# ethtool -i eth3
driver: pegasus
version: v0.6.14 (2006/09/27)
firmware-version:
bus-info: usb-0000:00:10.0-2


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


                 reply	other threads:[~2008-05-01 23:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=481A4A70.1040806@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@vger.kernel.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).