Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!ysub!psuvm!n5x
From: N5X@psuvm.psu.edu (James C Mankin)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Problem with ka9q, wd8003e, clarkson
Message-ID: <91151.084457N5X@psuvm.psu.edu>
Date: 31 May 91 12:44:57 GMT
References: <1991May30.030706.12464@metro.ucc.su.OZ.AU>
 <9105301857.AA29500@ganges.ucop.edu>
Organization: Penn State University
Lines: 23

In article <9105301857.AA29500@ganges.ucop.edu>, opschk@GANGES.UCOP.EDU says:

>Stefan Tolhurst writes:
>>Drivers started with:
>>WD8003E 0x60 0x3 0x280 0xd000
>>WD8003E 0x61 0x4 0x2a0 0xce00

>>ka9q started as (for either WD or clarkson driver)
>>ip addr 129.78.66.77
>>attach packet 0x60 en0 8 1500
>>route add 129.78.66.64/26 en0

>If you start packet with  WD8003E 0x60 0x3 0x280 0xd000, it means you are
>using
>IRQ 3 => in ka9q, you must use:
>attach packet 0x60 en0 3 1500

>                Camille Iwanowitsch Kayruzian
>                opschk@ganges.ucop.edu, 415 987 03 62
No, if you are using the packet driver then ka9q doesnt need or care to know
which hardware interrupt is being used.  That parameter in the attach command
is the number of buffers.  See the response from typing 'attach packet ?'
73's Jim KB3KJ