From: "Michael Gibson" <mgibson@esesixtech.com>
To: <linux-net@vger.kernel.org>
Subject: pcnet32 fiberoptic
Date: Tue, 23 Apr 2002 09:31:37 +0200 [thread overview]
Message-ID: <028601c1ea98$e75bb480$3201a8c0@thinstuff.com> (raw)
Hi All,
Maybe somebody can help us with this issue:
1. We have applied following patch to the pcnet32 driver for kernel 2.4.17
http://www.uwsg.iu.edu/hypermail/linux/net/0102.0/0019.html
to make the fiberoptic port work for Allied Telesyn AT-2450FTX NW card.
This card has 2 interfaces: a Fiberoptic 10Mbit (ST Inerface) and a TP
10/100Mbit interface
We are using it togeteher with the "MC13 Ethernet Media Converter" also from
allied telesyn.
This is a media converter from fiberoptic (10MBit) to 10MBit TP.
We connected it to a 10Mbit TP HUB.
We are using the 10Mbit Fiberoptic interface of this card and it is about 30
times slower then a normal 10Mbit TP Lan.
So IMHO that should be a driver problem and not normal.
But maybe I am wrong.
We are also using an Allied Telesyn AT-2700FX card.
This card has only one interface: a Fiberoptic 100Mbit (ST Inerface)
We are using this one together with the "MC101XL Fast Ethernet Media
Converter" also from Allied Telesyn.
This is a media converter from fiberoptic (100MBit) to 100MBit TP.
We connected it to a 100Mbit TP switch.
This card is about the same speed as a normal 100Mbit TP card.
Both above cards. The 10Mbit fiber and the 100Mbit fiber have exactely the
same AMD chip: PCnet Fast+, AM79C972BKC.
Does somebody have any idea what could be causing the problem that the
10Mbit fiber
card is so terribly slow?
Can this fiber patch be included into the pcnet32 driver?
Best regards
Michael Gibson
next reply other threads:[~2002-04-23 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 7:31 Michael Gibson [this message]
[not found] <014201c1ea01$07094740$3201a8c0@thinstuff.com>
2002-04-23 6:38 ` pcnet32 fiberoptic Carsten Langgaard
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='028601c1ea98$e75bb480$3201a8c0@thinstuff.com' \
--to=mgibson@esesixtech.com \
--cc=linux-net@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).