All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Roman Mashak <mrv@corecom.co.kr>
Cc: linux-mips@linux-mips.org
Subject: Re: Ethernet bridging on 2.6.12-rc3 (PMC-sierra patched)
Date: Mon, 19 Jun 2006 14:51:56 +0100	[thread overview]
Message-ID: <20060619135156.GA9701@linux-mips.org> (raw)
In-Reply-To: <000601c6937f$0bed5270$9d0ba8c0@mrv>

On Mon, Jun 19, 2006 at 06:02:08PM +0900, Roman Mashak wrote:

> I was observing this strange problem today while verifying performance of 
> Sequoia board.
> 
> Initial conditions:
> 1) 2.6.12-rc3_L002 kernel from PMCS ftp, compiled for 32bit mode
> 2) bridge code is compiled into kernel
> 3) four 100Mbps ethernet devices and one onboard Gigabit link are joined 
> into bridge using bridge-utils-1.1
> 4) I connected board gigabit link to SmartBit Gb interface and four 100mbps 
> links to SmartBit FastEthernet interfaces
> 
> But 'brctl showmacs br0' shows only fast ethernet links being learned, but 
> never gigabit. We have suspicion that Titan driver affects this somehow.

The Titan driver (the version on linux-mips.org and any other version I've
seen) are pretty broken and remarkably ugly pieces of code.  The authors
of the Basler eXcite platform have contributed their driver and I hope it
will show up upstream soon.  Afaik it has not been tested with any of
PMC's eval boards but the necessary changes should not be hard.

  Ralf

  reply	other threads:[~2006-06-19 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  9:02 Ethernet bridging on 2.6.12-rc3 (PMC-sierra patched) Roman Mashak
2006-06-19  9:02 ` Roman Mashak
2006-06-19 13:51 ` Ralf Baechle [this message]
2006-06-20  0:36   ` Roman Mashak
2006-06-20  0:36     ` Roman Mashak
  -- strict thread matches above, loose matches on Subject: below --
2006-06-20 16:15 Raj Palani
2006-06-20 16:45 ` Ralf Baechle
2006-06-21  0:34 ` Roman Mashak
2006-06-21  0:34   ` Roman Mashak
2006-06-20 17:07 Raj Palani
2006-06-21  7:01 Raj Palani

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=20060619135156.GA9701@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mrv@corecom.co.kr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.