From owner-freebsd-net Mon Dec 30 20:48:13 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6095237B401 for ; Mon, 30 Dec 2002 20:48:12 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A38343EA9 for ; Mon, 30 Dec 2002 20:48:11 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.6/8.12.3) with ESMTP id gBV4mA1e014462; Mon, 30 Dec 2002 21:48:10 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 30 Dec 2002 22:47:58 -0600 (CST) Message-Id: <20021230.224758.94106280.imp@bsdimp.com> To: silby@silby.com Cc: eugen@grosbein.pp.ru, net@freebsd.org Subject: Re: ep(4) does not support mediaopt full-duplex From: "M. Warner Losh" In-Reply-To: <20021230223442.D25468-100000@patrocles.silby.com> References: <20021230221357.H25392-100000@patrocles.silby.com> <20021230.222103.07268910.imp@bsdimp.com> <20021230223442.D25468-100000@patrocles.silby.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message: <20021230223442.D25468-100000@patrocles.silby.com> Mike Silbersack writes: : >From what I've read, the vortex cards do resemble the older Etherlink : IIIs, so yes those two could probably be merged. They are merged in NetBSD. I think Matt Dodd has some patches that do this. : However, the 3c900+ : cards have a true bus mastering PCI architecture, so it makes sense to fit : them into a seperate driver, such as if_xl. Just because it is true bus mastering doesn't mean that it makes sense to have a different driver... I haven't looked at the structure of these two drivers to know if this makes sense or not. I was mostly speculating out loud... : Here's another thing I'm confused about: : : from if_xlreg.h: : : #define TC_DEVICEID_HURRICANE_556 0x6055 : : from if_ep_pccard.c: : : case 0x6055: /* 3C556 */ : : Is it possible that 3Com used the same chip in mini-pci and pccard : designs? This does seem possible, as 3c905 (pre-B, I don't know about the : mini-PCI version) cards support the 3c509 interface. Likely just a compat thing. The 3com interfaces seem to have lots backward compat stuff (did you know you can get the EISA id out of pcmcia devices, at least the 3c1?) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message