From: Eric Weigle <ehw@lanl.gov>
To: nick@snowman.net
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Sampson Fung <sampson@attglobal.net>,
linux-kernel@vger.kernel.org
Subject: Re: OT: Which Gigabit ethernet card?
Date: Mon, 23 Dec 2002 10:23:57 -0700 [thread overview]
Message-ID: <20021223172357.GS23388@lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.21.0212230949270.22216-100000@ns.snowman.net>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
> > > Can I just use a standard Cross Over UTP cable to link up two Intel
> > > Gigabit card, just like Fast Ethernet does?
> > yes, but be careful, as cat 5e is pretty tough when it comes to the
> > connector specs
> I belive this is incorrect. A traditional ethernet crossover crosses two
> pairs, as ethernet & fast ethernet use 2 pairs. Gigabit ethernet uses all
> 4 pairs, and would need all 4 pairs crossed I assume.
According to spec, maybe, but in practice not necessary. Modern gigE cards
will run just fine over all sorts of pin-outs (even non-crossed over cables)
See
http://www.intel.com/network/connectivity/products/pro1000mt_desktop_adapter.htm
"automatically compensates for cable issues such as crossover cable, wrong
pin-out and polarity"
Or
http://www.intel.com/design/network/products/lan/controllers/82546.htm
"PHY detects polarity, MDI-X, 2 pair vs. 4 pair cables, and cable length
... No need to know the difference between crossover and non-crossover cables"
-Eric
--
------------------------------------------------------------
Eric H. Weigle -- http://public.lanl.gov/ehw/
"They that can give up essential liberty to obtain a little
temporary safety deserve neither" -- Benjamin Franklin
------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-12-23 17:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 13:45 OT: Which Gigabit ethernet card? Jurgen Kramer
2002-12-20 18:29 ` Ben Greear
2002-12-20 18:48 ` Bill Davidsen
2002-12-20 20:15 ` Wes Felter
2002-12-20 21:06 ` Joel Jaeggli
2002-12-20 21:08 ` Dax Kelson
2002-12-20 21:13 ` Eric Weigle
2002-12-21 12:44 ` Jurgen Kramer
2002-12-21 17:28 ` Sampson Fung
2002-12-23 12:17 ` Roy Sigurd Karlsbakk
2002-12-23 14:50 ` nick
2002-12-23 17:23 ` Eric Weigle [this message]
2002-12-23 17:28 ` Justin Cormack
2002-12-23 17:35 ` Jeff Garzik
2002-12-24 1:43 ` nick
2002-12-23 18:57 ` Daniel Egger
2002-12-25 6:03 ` David Lloyd
2002-12-25 13:50 ` Gerhard Mack
2002-12-25 15:23 ` Michael Clark
2002-12-25 17:23 ` Jeff Garzik
2002-12-25 17:33 ` Sean Neakums
2002-12-27 9:45 ` daveman
2002-12-27 9:59 ` John Bradford
[not found] <fa.io6mq9v.11gou0n@ifi.uio.no>
2002-12-31 2:22 ` Bill Davidsen
2002-12-31 8:47 ` Filip djMedrzec Zyzniewski
2003-01-09 16:15 ` Bill Davidsen
2003-01-09 16:39 ` John Bradford
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=20021223172357.GS23388@lanl.gov \
--to=ehw@lanl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@snowman.net \
--cc=roy@karlsbakk.net \
--cc=sampson@attglobal.net \
/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.