From owner-freebsd-hackers Mon Jan 20 13:41:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00330 for hackers-outgoing; Mon, 20 Jan 1997 13:41:44 -0800 (PST) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA00322 for ; Mon, 20 Jan 1997 13:41:42 -0800 (PST) Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id PAA03035 for ; Mon, 20 Jan 1997 15:41:40 -0600 (CST) Received: from jaguar (jaguar.vale.com [204.117.217.146]) by crocodile.vale.com (8.8.3/8.7.3) with SMTP id PAA13425 for ; Mon, 20 Jan 1997 15:41:40 -0600 (CST) Message-ID: <32E3E693.2364@vailsys.com> Date: Mon, 20 Jan 1997 15:41:40 -0600 From: Hal Snyder Reply-To: hal@vailsys.com Organization: Vail Systems, Inc. X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: IBM Token ring driver References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Molnar wrote: > have you tried olicom? I heard that they are more forgiving > with opening up eith driver info. I would like to do it, but > I am not a programer, I am a silly person. I talked to Olicom a year ago about writing a FreeBSD token driver for their PCI token ring card, since my employer at the time was stuck with a lot of legacy dinosaur equipment. The response I got was that driver writers' documentation was trade secret and they had absolutely no intention of telling anyone how their superlative token ring card works. After that, all nodes added to the LAN were ether. We had that luxury, since cabling was CAT-5 and the main router had both types of interface. :) Hal