Re: ethernet driver problem

• To: Kristin Wright <kwright@cs.utah.edu>
• Subject: Re: ethernet driver problem
• From: Bart Robinson <lomew@ffnet.com>
• Date: Mon, 19 Jul 1999 14:47:53 -0700 (PDT)
• Cc: danderse@cs.utah.edu, roland@cs.utah.edu, rob@darkstar.welcomehome.org, oskit-users@cs.utah.edu
• In-Reply-To: <199907192106.PAA11987@marker.cs.utah.edu>
• References: <14227.36431.865172.148648@polk.ffnet.com> <199907192106.PAA11987@marker.cs.utah.edu>
• Sender: owner-oskit-users@fast.cs.utah.edu

On 1999-7-19 Kristin Wright <kwright@cs.utah.edu> wrote:
 > autodetect didn't work for me...at least a few months
 > ago it didn't. 

I think it only works if you hardcode TULIP_PORT to 10TP.

I know that when I would install a new netboot there it would
work whether the machine had a 100 or 10 speed link.
Unless I had TULIP_PORT hardcoded to 100.

>From looking at the driver this makes sense.  When the
driver has a xmit timeout it bumps the if_port and calls
port_select.  TULIP_100TP_PORT is one more than TULIP_10TP_PORT.
So if you hardcode TULIP_PORT to 10TP, then it will try 100TP
next.  But if you hardcode it to 100TP, tickssofar will cause
tulip_start_xmit to fail before it wraps back to TULIP_10TP_PORT.

-- bart

• Re: ethernet driver problem
• From: Bart Robinson <lomew@ffnet.com>
• Re: ethernet driver problem
• From: Kristin Wright <kwright@cs.utah.edu>

• Prev: Re: ethernet driver problem
• Next: New OSKit Snapshot oskit-990722
• Index(es):
  • Main
  • Thread