[lkml]   [2001]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 3c905C-TX [Fast Etherlink] problem ...
> mm..  It _should_ autonegotiate.  Perhaps the device at
> the other end is old or not very good.

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.

> 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 ...


|-| __ Robert Vojta <> -= Oo.oO =-
|=| [Ll] IPEX, s.r.o.
"^" ====`o
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 12:53    [W:0.028 / U:0.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site