Subject: Re: Compaq NetFlex 3/P (fwd)
To: Bill Paul <wpaul@ctr.columbia.edu>
From: Gregory McGarry <g.mcgarry@qut.edu.au>
List: tech-net
Date: 03/31/1999 08:01:54
Bill Paul wrote:
 
> > > With recent (26/3) changes to the ThunderLAN (tl) attach code, I can get a
> > > Compaq NetFlex 3/P board to probe successfully.  The board uses LXT901PC
> > > and DP8392CV-1 line driver chips for 10baseT and 10base5 respectively.
> > > These aren't PHYs, so the the board must be wired to use the internal
> > > PHY.  It should be located at PHY no. 31 according to the ThunderLAN
> > > Programmer's Guide, shouldn't it?
> > 
> > Yes.
> 
> No. This chip doesn't have an internal MII PHY. It's not a TNETE100.

Oh, didn't check that.  Just assumed they were all the same.

> I have one of the Netflex-3/P cards in question here. This card is
> different from the Netflex-3/P integrated NIC on certain Compaq machines.
> The chip on my board is labeled L10000PCE, and the section with the Level1
> and NatSemi chips is modular and can be removed.

Yep, that is the one.  Unusual, isn't it.

> I'm not certain if this
> is a core version of the ThunderLAN with external PCI glue or if it's
> a mislabeled TNETE110 chip, which according to the manual doesn't have
> MII support. In any case, in order to make it work, you have to
> set the 'bitrate' bit in the netconfig register. You can then use the
> lower 4 bits in the acommit register to control the media mode (see pages
> A-27 and A-35 of the ThunderLAN programmer's manual).

> I made some changes
> to the FreeBSD ThunderLAN driver to make this card work, which I just
> committed to -current and -stable.

Well, I was just going to say that the FreeBSD driver didn't work
either.  I will look at your patches.

> The modifications are fairly
> straightforward. I think that for the NetBSD driver, if the MII probe
> doesn't find any PHY instances, you should switch to bitrate mode.

Are you happy that this is the right thing to do Manuel?
 
> Note: depending on how you initialize the ThunderLAN chip, all of the
> bits in the ACOMMIT register may default to 0. This is fine except for
> the MTXD3 bit, which controls full-duplex/half-duplex mode: it must
> be set to 1 for half-duplex, which is the mode that people will likely
> want by default.
> 
> -Bill

Thanks Bill.

Regards,
Greg