Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!swrinde!cs.utexas.edu!utnut!torn!uunet.ca!uunet.ca!fw.novatel.ca!sidney.novatel.ca!hpeyerl
From: hpeyerl@sidney.novatel.ca (Herb Peyerl)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD 1.1 and 3Com 509 trouble
Date: 2 May 1994 20:16:37 GMT
Organization: NovAtel Communications Ltd.
Lines: 26
Message-ID: <2q3n35$m1c@fw.novatel.ca>
References: <CosoGv.HKn@noose.ecn.purdue.edu>
NNTP-Posting-Host: sidney.novatel.ca
X-Newsreader: TIN [version 1.2 PL1]
Curtis Smith (smithc@chainsaw.ecn.purdue.edu) wrote:
: The kernel boot and recognises my card, ie. it prints the address of the
: card, but no packets are exchanged. I question the configuration line. I
: put in the card at a specific I/O address, and a specific interrupt number.
: But I leave out a memory address. Should I put one in and if so what should
: it be? I didn't see an example of use of the "ep" driver.
The 'ep' driver works extremely well for me under NetBSD. The 3c5x9 cards
don't use shared memory so you needn't include the memory address field in
config. All you should need is a base address and an irq.
Under NetBSD; the following config lines work for me:
device ep0 at isa? port 0x350 net irq 7 vector epintr
device ep1 at isa? port ? net irq ? vector epintr
What this says is "the first ep card has a base address of 0x350 and irq 7.
assign 'ep1' to the next ep card that you find".
Though I'm not sure if the FreeBSD version of the 'ep' driver has support
for 'port ? net irq ?'.
--
hpeyerl@novatel.ca | NovAtel Commnications Ltd.
hpeyerl@fsa.ca | <nothing I say matters anyway>
strcmp(3): When you want to just relax and cruise down memory lane.