From owner-freebsd-hackers  Mon Aug  7 14:35:49 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 618)
	id C933237BAC8; Mon,  7 Aug 2000 14:35:44 -0700 (PDT)
Subject: Re: 3Com 10/100 Mini PCI Ethernet
In-Reply-To: <20000807195147.BC7FB1F1C@bert.kts.org> from Hellmuth Michaelis at "Aug 7, 2000 09:51:47 pm"
To: hm@kts.org
Date: Mon, 7 Aug 2000 14:35:44 -0700 (PDT)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20000807213544.C933237BAC8@hub.freebsd.org>
From: wpaul@FreeBSD.ORG (Bill Paul)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> AFAIK, this card is a 3Com OEM product which is not available for purchase,
> all i can give you is an HP part number. It is also not a "normal" PCI card
> but a so called "Mini PCI" card and its about as large as a matchbox or
> even a bit smaller.
> 
> Anyway, i have replaced the card, and i will try hard not to make the same
> mistakes again (before this whole mess, i was under the impression that
> only monitors can be destroyed by software, now i know better ...).
> 
> But, i want to get this card supported. In case you have one or the other
> good suggestion (except "stay away from the card, don't even look at it !!")
> on how to proceed in a more orderly fashion, please let me hear them.

Type "pciconf -l" and show us the results so we can actually see the
vendor/device ID data. If it is indeed vendor ID 0x10B7 and device ID
0x6055, then try the patch included with this e-mail. To apply it, do
the following:

- Save this message to a file, e.g. /tmp/xl.diff
- cd /sys/pci
- patch < /tmp/xl.diff

Then make a new kernel and/or if_xl.ko module and test it. If it works
correctly, you should see the ethernet address and proper media selections
in the dmesg output. And, more importantly, you should be able to send
and receive traffic. If it doesn't probe correctly, then it's probably
not a Cyclone/Hurricane/Tornado chipset and the xl driver won't support
it. I believe that it is a Cyclone/Hurricane/Tornado chipset though,
since 3Com doesn't make any other 10/100 devices except for what's on
the 3CR990 card, which is a) undocumented and b) overkill for an embedded
laptop ethernet adapter.

-Bill


*** if_xl.c.orig	Mon Aug  7 14:25:39 2000
--- if_xl.c	Mon Aug  7 14:25:03 2000
***************
*** 55,60 ****
--- 55,61 ----
   * 3Com 3c980C-TX	10/100Mbps server adapter (Tornado ASIC)
   * 3Com 3cSOHO100-TX	10/100Mbps/RJ-45 (Hurricane ASIC)
   * 3Com 3c450-TX	10/100Mbps/RJ-45 (Tornado ASIC)
+  * 3Com 3cN3AV1556	10/100Mpps/RJ-45 HP laptop ethernet (Tornado ASIC?)
   * Dell Optiplex GX1 on-board 3c918 10/100Mbps/RJ-45
   * Dell on-board 3c920 10/100Mbps/RJ-45
   * Dell Precision on-board 3c905B 10/100Mbps/RJ-45
***************
*** 184,189 ****
--- 185,192 ----
  		"3Com 3cSOHO100-TX OfficeConnect" },
  	{ TC_VENDORID, TC_DEVICEID_TORNADO_HOMECONNECT,
  		"3Com 3c450-TX HomeConnect" },
+ 	{ TC_VENDORID, TC_DEVICEID_3CN3AV1556,
+ 		"3Com 3CN3AV1556 Fast Etherlink XL" },
  	{ 0, 0, NULL }
  };
  
***************
*** 1142,1147 ****
--- 1145,1151 ----
  	case TC_DEVICEID_HURRICANE_SOHO100TX:	/* 3cSOHO100-TX */
  	case TC_DEVICEID_TORNADO_10_100BT:	/* 3c905C-TX */
  	case TC_DEVICEID_TORNADO_HOMECONNECT:	/* 3c450-TX */
+ 	case TC_DEVICEID_3CN3AV1556:		/* 3cN3AV1556 */
  		sc->xl_media = XL_MEDIAOPT_BTX;
  		sc->xl_xcvr = XL_XCVR_AUTO;
  		if (verbose)



*** if_xlreg.h.orig	Mon Aug  7 14:25:39 2000
--- if_xlreg.h	Mon Aug  7 14:20:14 2000
***************
*** 641,646 ****
--- 641,647 ----
  #define TC_DEVICEID_TORNADO_10_100BT_SERV	0x9805
  #define TC_DEVICEID_HURRICANE_SOHO100TX		0x7646
  #define TC_DEVICEID_TORNADO_HOMECONNECT		0x4500
+ #define TC_DEVICEID_3CN3AV1556			0x6055
  
  /*
   * PCI low memory base and low I/O base register, and


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message