From owner-freebsd-hackers Tue Jul 7 07:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04425 for freebsd-hackers-outgoing; Tue, 7 Jul 1998 07:28:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA04412 for ; Tue, 7 Jul 1998 07:28:35 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id KAA18265; Tue, 7 Jul 1998 10:31:42 -0400 From: Bill Paul Message-Id: <199807071431.KAA18265@skynet.ctr.columbia.edu> Subject: Re: Object library formats To: lile@stdio.com (Larry S. Lile) Date: Tue, 7 Jul 1998 10:31:41 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Larry S. Lile" at Jul 6, 98 01:16:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Larry S. Lile had to walk into mine and say: > Could this library be linked into a kernel? > > COFF/TRLLD.O: 80386 COFF executable not stripped - version 30821 > > It is part of the Olicom device driver development kit for their token > ring cards. They seem to think it would be compatible with a.out. Also > would this library be compatible with an elf'd system? > > ELF/TRLLD.O: ELF 32-bit LSB relocatable, Intel 80386, version 1, > not stripped I would avoid trying to accomodate foreign object modules. It sets a bad precedent. Repeat after me: "You want source code. You want source code. These aren't the droids you're looking for." On a totally different note, somebody brought Olicom to my attention the other day: they also make PCI ethernet NICs based on the ThunderLAN chip. These are almost completely identical to the Compaq ThunderLAN NICs, except they use a different PCI vendor and product ID, and they have the station address encoded at a different location within the EEPROM (most ThunderLAN NICs have it at 0x83, they have it at 0xF8; accomodating this is easy). Unfortunately, I don't know where to find the PCI vendor and product IDs for their cards: all the 'datasheets' on their web server are basically just marketing hype. I found one place with patches for the Linux driver that claim to add Olicom support, but in typical Linux fashion, the patches are broken: the patch for the header file is incomplete and lists only the Olicom vendor ID, whereas the patch for the C code refers to product IDs for the OC-2183/2185, OC-2326 and 2326 NICs. These are nowhere to be found. I asked Olicom about getting more useful datasheets via their 'feedback' section on the web server but haven't heard anything back yet. May I ask where you got the token ring device driver kit? Do they have it available for download anywhere or did you have to speak to someone in particular at Olicom to get it? Do you know if they have kits for the ethernet NICs too? -Bill PS: The ThunderLAN chip appears to support both ethernet and token rin PHYs; if this is a PCI token-ring NIC thay you have, it may have this chip on it, in which case I would visit the Texas Instruments web server and obtain the programmer's guide from there. -- ============================================================================= -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