From owner-freebsd-tokenring Sun Oct 18 10:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18612 for freebsd-tokenring-outgoing; Sun, 18 Oct 1998 10:54:12 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18605 for ; Sun, 18 Oct 1998 10:54:09 -0700 (PDT) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566A1.006772A2 ; Sun, 18 Oct 1998 19:49:55 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-tokenring@FreeBSD.ORG Message-ID: <412566A1.00669FEF.00@bfc.dk> Date: Sun, 18 Oct 1998 19:51:07 +0100 Subject: Tokenring driver for IBM Turbo 16/4 Pccard Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello people on this great list. I'm started on doing some driver stuff for the IBM Turbo 16/4 Pccard, and would hear if there is a general interrest in a driver for that card. Unfortunately is this project the first BSD hacking I have ever tried but I keep thinking i actually could have a chance for getting it right. (in many years ;) My current problems is : 1) I'm having some problems getting the specs. for the card. 2) I know *nothing* to the FreeBSD driver structure (but have looked alot at the TOK driver) 3) I know *absolutely nothing* about the PCCARD programming stuff in FreeBSD. (Currently looking at ED driver) If any of you have some resources i should read the please mail me.. I'm desperately wanting(needing) a driver and does have a kind of spare time to make one. Regards, Nicolai Petri (npe@bfc.dk) System-Consultant WM-Data BFC - Denmark Ps. Help/comments/ideas/critic/etc. would also be nice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Sun Oct 18 16:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20537 for freebsd-tokenring-outgoing; Sun, 18 Oct 1998 16:45:00 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20525 for ; Sun, 18 Oct 1998 16:44:56 -0700 (PDT) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id TAA11129; Sun, 18 Oct 1998 19:46:58 -0400 (EDT) (envelope-from lile@heathers.stdio.com) Date: Sun, 18 Oct 1998 19:46:57 -0400 (EDT) From: "Larry S. Lile" To: npe@bfc.dk cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Tokenring driver for IBM Turbo 16/4 Pccard In-Reply-To: <412566A1.00669FEF.00@bfc.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Call IBM Publications: 1-800-879-2755, you want the IBM LAN Credit Card Adapter Technical reference, SC30-3585. Or if you have more patience than me goto: http://ppdbooks.pok.ibm.com:80/cgi-bin/bookmgr/bookmgr.cmd/Shelves/bk80bk03 Also you may find some of the information at http://anarchy.stdio.com usefull. The credit card adapters are the same as the ISA Shared Ram adapters, they just have the pcmcia bus registers. Larry Lile lile@stdio.com On Sun, 18 Oct 1998 npe@bfc.dk wrote: > Hello people on this great list. > I'm started on doing some driver stuff for the IBM Turbo 16/4 Pccard, and > would hear if there is a general interrest in a driver for that card. > Unfortunately is this project the first BSD hacking I have ever tried but I > keep thinking i actually could have a chance for getting it right. (in many > years ;) > My current problems is : > 1) I'm having some problems getting the specs. for the card. > 2) I know *nothing* to the FreeBSD driver structure (but have looked > alot at the TOK driver) > 3) I know *absolutely nothing* about the PCCARD programming stuff in > FreeBSD. (Currently looking at ED driver) > > If any of you have some resources i should read the please mail me.. I'm > desperately wanting(needing) a driver and does have a kind of spare time to > make one. > > Regards, > Nicolai Petri (npe@bfc.dk) > System-Consultant > WM-Data BFC - Denmark > > Ps. Help/comments/ideas/critic/etc. would also be nice. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-tokenring" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Oct 22 07:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08100 for freebsd-tokenring-outgoing; Thu, 22 Oct 1998 07:46:53 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08092 for ; Thu, 22 Oct 1998 07:46:52 -0700 (PDT) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id KAA18600 for ; Thu, 22 Oct 1998 10:48:51 -0400 (EDT) (envelope-from lile@heathers.stdio.com) Date: Thu, 22 Oct 1998 10:48:51 -0400 (EDT) From: "Larry S. Lile" To: tokenring@FreeBSD.ORG Subject: Olicom token-ring driver almost finished... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a lot of work on the IBM token ring driver I have finally decided to let it go for a while. Someone else is looking at the code and seeing what they can do for it. I have started working on a driver for the Olicom cards instead. The current state of the Olicom driver is pretty good, it probes, attaches, ifconfig's, and receives. I have had the driver running in this "read only" mode for several days without any problems, admittidly there is little load on the ring though. I an going to try and implement the transmit code this weekend it is the last step to basic functionality. Then I can begin shaking out the generic token ring functions. I am pretty hopeful about the driver, it has only taken about 7 days to get to this point and transmitting does not look that complicated. The caveats for the driver are that you MUST have an ELF kernel and you have to have the PowerMACH Works libraries from Olicom, it contatins the adapter microcode and interface library. I know that including foreign objects is considered bad but that is more of a religious discussion that can be taken up at a later date. The current driver source and information is available at http://anarchy.stdio.com You will need the generic code from that page and the driver code from the Olicom link at the bottom of the page. The PMW kit is also available at that page, I suggest you get the actual OC3300.EXE file and uncompress it, because I use the extracted kit on the page as a reference and is therefore subject to corruption. > netstat -I oltr0 Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll oltr0 1492 00.00.83.a9.da.3c 6014 0 0 0 0 oltr0 1492 10/24 anatok 6014 0 0 0 0 >ifconfig oltr0 oltr0: flags=8943 mtu 1492 inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 lladdr 00:00:83:a9:da:3c > Not bad for 7 days :) Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Fri Oct 23 09:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17539 for freebsd-tokenring-outgoing; Fri, 23 Oct 1998 09:36:41 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA17524 for ; Fri, 23 Oct 1998 09:36:29 -0700 (PDT) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566A6.00605113 ; Fri, 23 Oct 1998 18:32:02 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-tokenring@FreeBSD.ORG Message-ID: <412566A6.005FDF19.00@bfc.dk> Date: Fri, 23 Oct 1998 18:33:08 +0100 Subject: IBM Turbo 16/4 (pccard) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to know who is currently working on this adapter because I plan to implement pccard functionalities into the driver.. If anyone is currently working on it i would like know where i can get the most recent release. Maybe I could even get the if_tok.c mailed to me if there was any important changes! We should also get together by email so we could find out how what would be the easiest way! Into the same driver or a complete new driver. (I think we should integrate it into the tok driver.. But maybe somebody have a reason for not doing that!) Btw. Is there somebody who got an idea about when we can make a generic TR interface(rutines) into Current ?? Best regards, Nicolai Petri WM-Data BFC - Denmark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Fri Oct 23 10:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22279 for freebsd-tokenring-outgoing; Fri, 23 Oct 1998 10:25:58 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22274 for ; Fri, 23 Oct 1998 10:25:56 -0700 (PDT) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id NAA08308; Fri, 23 Oct 1998 13:27:48 -0400 (EDT) (envelope-from lile@heathers.stdio.com) Date: Fri, 23 Oct 1998 13:27:48 -0400 (EDT) From: "Larry S. Lile" Reply-To: "Larry S. Lile" To: npe@bfc.dk cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: IBM Turbo 16/4 (pccard) [Long: state of token ring] In-Reply-To: <412566A6.005FDF19.00@bfc.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG State of the world... I was working on the IBM driver, but it does not work. The only function it lacks is transmit, this will get it to basic function. I have written, or more accurately hacked, the generic token ring code into the net/inet areas and the if_iso88025subr.c. Some of it works fine some is flaky but mostly on the transmit side. Paul Norton is currently looking over the code to see if he can determine my problem and fix it (Hi Paul :) I am working on an Olicom driver for the ISA cards (and PCI soon). I will be writing the transmit code for that this weekend. That will allow the generic routines to finished and fixed up. As of yet I have not even attempted transmitting on this card but with the progess I have made already I am sure it will be near trivial. In 7 days I have caught back up to the state of the IBM driver which I have worked on (off and on) for the past 18 months. In general, there is currently no source routing involved in either driver they simply discard the route and turn off the sr bit. ARP is handled through the generic ethernet arp routines, with some small modifications. All AF_UNSPEC packets in the generic code must have an ethernet header for the time being, so that utilities that do not understand token ring will still work ie ping, arp ... These will be fixed later to use token ring headers as neeed. Tcpdump has been hacked to understand tokenring generically. I have send the patches off to the maintainers twice, but I have had no response from them. The hacked tcpdump understands source routing but also discards the information, should be trivial to add the code to print the routes but as of yet we cannot use them so it seemed unneccesary right now. Information about both drivers, generic FreeBSD token ring support and the tcpdump patches are available at http://anarchy.stdio.com. Information about all but the Olicom driver are available at http://www.jurai.net/~winter/tr/tr.html Information about the IBM token ring cards is avalable at http://ppdbooks.pok.ibm.com:80/cgi-bin/bookmgr/bookmgr.cmd/Shelves/bk80bk03 You can reach IBM Publications at 1-800-879-2755 if you would rather purchase hard copy of the adapter specs. They also have the general token ring information. Most of this information is listed under the IBM Lan Technical Reference collection. The IBM pcmcia token ring cards are the same as the ISA shared ram adapters, they just have the additional registers used for pcmcia. The biggest problem with the IBM driver right now is transmitting, occasionally the generic packet wrapper will blow a packet. I can fix that as soon as I get the Olicom driver transmitting. Both the packet roller and un-roller are grievious hacks based on the etherenet code so they are really a mess, I will clean it up though. If someone would get the tcpdump patches to -current I would be very pleased :) I don't think the generic token ring code is clean enough for inclusion yet. Larry Lile lile@stdio.com On Fri, 23 Oct 1998 npe@bfc.dk wrote: > I would like to know who is currently working on this adapter because I > plan to implement pccard functionalities into the driver.. If anyone is > currently working on it i would like know where i can get the most recent > release. Maybe I could even get the if_tok.c mailed to me if there was any > important changes! > > We should also get together by email so we could find out how what would be > the easiest way! Into the same driver or a complete new driver. (I think we > should integrate it into the tok driver.. But maybe somebody have a reason > for not doing that!) > > Btw. Is there somebody who got an idea about when we can make a generic TR > interface(rutines) into Current ?? > > Best regards, > Nicolai Petri > WM-Data BFC - Denmark. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-tokenring" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message