From: Robert Vojta <vojta@ipex.cz>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c905C-TX [Fast Etherlink] problem ...
Date: Mon, 21 May 2001 16:17:25 +0200 [thread overview]
Message-ID: <20010521161724.G8397@ipex.cz> (raw)
In-Reply-To: <20010521090946.D769@ipex.cz> <3B08C15E.264AE074@uow.edu.au>, <3B08C15E.264AE074@uow.edu.au> <20010521140443.C8397@ipex.cz> <3B090645.9D54574F@uow.edu.au>
In-Reply-To: <3B090645.9D54574F@uow.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
> mm.. It _should_ autonegotiate. Perhaps the device at
> the other end is old or not very good.
Hi,
it should but do not autonegotiating. All computers are connected to switch
CentreCOM FH716SW and there are several types of cards on this computers
like 3COM Tornado, 8139 chip, NE2000, etc.
> http://www.scyld.com/network/vortex.html is the official
> place. It doesn't tell you much.
>
> vortex.txt has a pointer to 3com's documentation. Heavy
> going.
>
> When the NIC is running in full-duplex mode it *assumes*
> that once (by default) 128 bytes of a frame have gone
> onto the wire, the remainder of the frame will be sent
> without any collisions. This assumption allows it to reuse
> part on the on-board memory - it transfers more data from
> the host into the place where the currently-transmitting
> frame used to reside.
>
> If another host then comes along and generates a collision
> this late into the frame, the NIC detects it but cannot
> back off and retransmit the frame as it would normally do.
> Because the frame's memory has been "reclaimed". All it
> can do is raise an interrupt and complain.
Thanks for this informations ...
Best,
.R.V.
--
_
|-| __ Robert Vojta <vojta-at-ipex.cz> -= Oo.oO =-
|=| [Ll] IPEX, s.r.o.
"^" ====`o
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-05-21 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 7:09 3c905C-TX [Fast Etherlink] problem Robert Vojta
2001-05-21 7:18 ` Andrew Morton
2001-05-21 12:04 ` Robert Vojta
2001-05-21 12:12 ` Andrew Morton
2001-05-21 14:17 ` Robert Vojta [this message]
2001-05-21 17:13 ` 3C905C and error e401 : problem solved francois.cami
2001-05-21 18:51 ` 3c905C-TX [Fast Etherlink] problem Wilfried Weissmann
2001-05-22 7:20 ` Robert Vojta
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=20010521161724.G8397@ipex.cz \
--to=vojta@ipex.cz \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@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