Date: Mon, 31 Aug 1998 13:28:06 -0400 (EDT) From: Bill Paul <wpaul@skynet.ctr.columbia.edu> To: hackers@FreeBSD.ORG Subject: Call for testers for new ThunderLAN driver Message-ID: <199808311728.NAA04332@skynet.ctr.columbia.edu>
next in thread | raw e-mail | index | archive | help
I've rewritten the TI ThunderLAN driver in preparation for integrating it into the 2.2 branch. The major changes are as follows: - Rewrote the multicast support to use the three spare entries in the perfect filter table before rolling over to the hash table. This means the first three groups are always filtered perfectly (which means we save a bit from the hash table that would normally be used by the 224.0.0.1 entry, which is always present). - Did a major overhaul of the register access macros. Hopefully things are somewhat less grotty now. - Did away with the notion of attaching each PHY as a separate interface. This doesn't really apply; this being the first driver I ever wrote, I got a few concepts wrong, and this was one of them. This simplifys the interface attach somewhat. - Cleaned up the PHY autonegotiation code based on what I learned with the XL driver. - Added support for newer versions of the Olicom 2326 10/100 adapter with the Micro Linear ML6692 100baseTX PHY. This is a sort of oddball component in that it provides autonegotiation for all modes (100Mbps, 10Mbps, full duplex, half duplex) but relies on the ThunderLAN's internal PHY for actual 10Mbps support. It also does not have vendor/device ID registers, which makes it a little tricky to detect. Older versions of the 2326 have a NatSemi NS83840A; using the ML 6692 is probably more cost effective since using the NS83840A means the ThunderLAN's internal PHY goes unused. - Tried to fix support the BNC port on those adapters that have them. This is untested as I don't have access to a device with a BNC connector. - Added code to raise the PCI latency timer value all the way up, as recommended by the manual. - Added new routine tl_hardreset() to attempt to insure that the internal PHY is brought online correctly, again as specified by the manual. The internal PHY is now always activated by default, although it may be kept isolated and unused in certain configurations. The driver code can be obtained from the following URLs: http://www.freebsd.org/~wpaul/ThunderLAN/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/ThunderLAN/2.2 source for FreeBSD 2.2.x If you have a recent 3.0 snapshot that already has the older ThunderLAN driver, you can simply copy if_tl.c and if_tlreg.h over the existing copies in /sys/pci and recompile, otherwise follow the instructions at http://www.freebsd.org/~wpaul/ThunderLAN for adding the driver to an existing system. This driver supports the following list of Compaq and Olicom network adapters and integrated NICs: Compaq Netelligent 10 Compaq Netelligent 10/100 Compaq Netelligent 10/100 Proliant Compaq Netelligent 10/100 Dual Port Compaq NetFlex-3/P Integrated Compaq NetFlex-3/P Compaq NetFlex 3/P w/ BNC Compaq Netelligent 10/100 TX Embedded UTP Compaq Netelligent 10 T/2 PCI UTP/Coax Compaq Netelligent 10/100 TX UTP Olicom OC-2183/2185 Olicom OC-2325 Olicom OC-2326 10/100 TX UTP Compaq machines with built-in ThunderLAN NICs include the Compaq Deskpro 4000 series and the Compaq Proliant servers. If you have one of these adapters or integrated controllers, please give this driver a try and report on the results. Also, if anyone happens to know of any other ethernet adapters that use the ThunderLAN chip, I'd be interested to hear about it. PCI vendor and device IDs would also be greatly appreciated. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808311728.NAA04332>