From owner-freebsd-hackers Mon Jul 6 10:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18655 for freebsd-hackers-outgoing; Mon, 6 Jul 1998 10:51:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18610 for ; Mon, 6 Jul 1998 10:51:41 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id NAA07930; Mon, 6 Jul 1998 13:48:40 -0400 (EDT) Date: Mon, 6 Jul 1998 13:48:39 -0400 (EDT) From: "Larry S. Lile" To: sbabkin@dcn.att.com cc: hackers@FreeBSD.ORG Subject: RE: Object library formats In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Jul 1998 sbabkin@dcn.att.com wrote: > > -----Original Message----- > > From: Larry S. Lile [SMTP:lile@stdio.com] > > > > 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 > > > Is Olicom part of Olivetti or something different ? I have no idea as to Olicom's lineage. > > 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 > > > A COFF binary file can be converted into a.out without much problems, > I have even written that converter once but it was lost during a crash > and I > felt no urge to write it again. The problem is that this driver is > probably > relying on the SysV Device Driver Interface to call the kernel library > functions that are missing in FreeBSD. For a network driver this is for > sure because it should use the STREAMS framework which is not used > in FreeBSD. It is not a network driver in and of itself, it is just the hardware interface library. In other words, it is just enough to glue a driver to the card. So the question still stands, can I link it into the kernel and write a driver around it? > -Serge > > P.S. A not stripped object file may be very useful for reverse > engineering. I have no intrest in reverse engineering their code, I just want to get a driver written for their card after I finish my driver for the IBM shared ram token ring cards. The IBM driver is just about to start passing packets, now that I have talked to the local network guru about SNAP headers and the like. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message