netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: P@draigBrady.com
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
	e1000-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: strange e1000 interface freeze
Date: Wed, 11 Aug 2004 17:08:53 +0200	[thread overview]
Message-ID: <16666.13957.266124.967306@robur.slu.se> (raw)
In-Reply-To: <411A3238.6060400@draigBrady.com>


P@draigBrady.com writes:

 > Interesting.
 > We've noticed the problems on 133MHz but not on 100MHz
 > We're double checking 100MHz at the moment.

 I've guess you have seen that the QUAD board which uses
 2 * 82546EB plus a PCI-bridge sets the speed between the 
 onboard bridge and 82546 chips to 120 MHz.

 Cheers.
					--ro

      parent reply	other threads:[~2004-08-11 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 10:54 strange e1000 interface freeze P
2004-08-11 14:26 ` Robert Olsson
     [not found]   ` <411A3238.6060400@draigBrady.com>
2004-08-11 15:08     ` Robert Olsson [this message]

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=16666.13957.266124.967306@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=P@draigBrady.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=netdev@oss.sgi.com \
    /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).