From owner-freebsd-hardware  Thu May 15 01:20:37 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA06995
          for hardware-outgoing; Thu, 15 May 1997 01:20:37 -0700 (PDT)
Received: from trifork.gu.net (trifork.gu.net [194.93.190.194])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06989
          for <freebsd-hardware@FreeBSD.ORG>; Thu, 15 May 1997 01:20:32 -0700 (PDT)
Received: from localhost (localhost.gu.kiev.ua [127.0.0.1])
	by trifork.gu.net (8.8.5/8.8.5) with SMTP id LAA10157;
	Thu, 15 May 1997 11:19:51 +0300 (EEST)
Date: Thu, 15 May 1997 11:19:51 +0300 (EEST)
From: Andrew Stesin <stesin@gu.net>
Reply-To: stesin@gu.net
To: Brett Glass <brett@lariat.org>
cc: sjr@zombie.ncsc.mil, freebsd-hardware@FreeBSD.ORG
Subject: Re: 2nd 3C509 card?
In-Reply-To: <3.0.1.32.19970513171935.00715d0c@lariat.org>
Message-ID: <Pine.BSF.3.95q.970515111417.9925G-100000@trifork.gu.net>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

What's so strange with 3c509-combo?  We use them here and there
with 0 problems (2.2 branch), just take it's _latest_ config utility
from ftp.3com.com and force the card to forget the words "Plug-n-Pray"
as a whole. Forcing the proper cabling type is nice too.

You want two/three/four cards? Ok, use the config utility
to put each card on different (it's own) IRQ and I/O range.  Then
describe ep0 and ep1 and ... in your kernel config file as
appropriate to your HW setup.  They will work.

EISA 3c5x9 cards also work with 2.2.*, tested.

Best regards,
Andrew Stesin

nic-hdl: ST73-RIPE