Re: lock down tulip driver

On Thu, 15 May 2003, James H. Laros wrote:

> Thanks but ultimately I would like to lock it down
> in the source itself. I used to do this for our
> clusters to avoid autonegotiation problems. I am
> trying to dig up what I did previously to see if
> it still applies to the new drivers. 

Read
   http://www.scyld.com/network/tulip.html
for the module options.

This isn't as clean as using the ioctl() from mii-diag.  There the
driver interprets the setting to work with either the internal
transceiver or an external transceiver.

When you pass a module option (or the equivalent kernel parameter) you
simultaneously force the
   specific transceiver connection and type
   speed
   duplex
That's because module options are intended to work around hardware bugs or
non-standard-conforming installations, rather than be a general
configuration mechanism.

> >   mii-diag -F 100baseTx
> By the way it seems that I wasn't specific. I want
> autonegotiation turned off.

The '-F' flag forces the speed and duplex, which implicitly turns off
  autonegotiation.
The '-A' flag limits autonegotiation, which has very specific
  semantics.  Those semantic might not make sense to someone that hasn't
  thought through the issues.
     http://scyld.com/expert/NWay.html

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip