From owner-freebsd-hackers  Tue Feb 20 21:21:20 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA06913
          for hackers-outgoing; Tue, 20 Feb 1996 21:21:20 -0800 (PST)
Received: from baygull.rtd.com (baygull.rtd.com [198.102.68.5])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA06908
          for <hackers@freebsd.org>; Tue, 20 Feb 1996 21:21:19 -0800 (PST)
Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id WAA14779; Tue, 20 Feb 1996 22:21:06 -0700
To: hackers@freebsd.org
Path: freefall.freebsd.org!owner-freebsd-hackers
From: sclawson@bottles.cs.utah.edu (steve clawson)
Newsgroups: rtd.freebsd.hackers
Subject: Re: 3Com Etherlink II/16 device timeouts
Date: Tue, 20 Feb 96 19:53:12 MST
Lines: 23
Message-ID: <199602210253.TAA14765@bottles.cs.utah.edu>
NNTP-Posting-Host: seagull.rtd.com
Sender: owner-hackers@freebsd.org
Precedence: bulk

Jordan K. Hubbard uttered:
> > Hello,
> > 
> >   I'm getting the following error with my 3Com card:
> > 
> > ed0: device timeout
> 
> Wrong device.. :-)
> 
> You want to configure the ep0 device for this card.

     Not unless you really want to have problems. =) The ep driver is
for the 3com EtherLink III (3c509).  The Etherlink II/16 (3c503)
(which is what he's asking about; note the subject line) is supported
by the ed driver.  


steve

-- 
// stephen clawson				sclawson@cs.utah.edu
// university of utah