From owner-freebsd-stable Fri Dec 20 0:45:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CF3F37B401 for ; Fri, 20 Dec 2002 00:45:24 -0800 (PST) Received: from saeab.se (ture.saeab.se [213.80.3.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE7543EEC for ; Fri, 20 Dec 2002 00:45:22 -0800 (PST) (envelope-from thn@saeab.se) Received: from saeab.se (omar.int.saeab.se [10.0.1.32]) by saeab.se (8.12.6/8.12.6) with ESMTP id gBK8j2II046414; Fri, 20 Dec 2002 09:45:02 +0100 (CET) (envelope-from thn@saeab.se) Message-ID: <3E02D88D.2A22FBD6@saeab.se> Date: Fri, 20 Dec 2002 09:45:01 +0100 From: Thomas Nystrom Organization: Sv. Aktuell Elektronik AB X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: sv,en MIME-Version: 1.0 To: Barry Pederson Cc: Steve Burton , stable@FreeBSD.ORG Subject: Re: VIA VT6103 Ethernet Controller Question References: <3DFBACE7.1D60335F@saeab.se> <3E01DE5A.265553D0@sliderule.demon.co.uk> <3E026002.5CDDA536@sliderule.demon.co.uk> <3E028E50.9080602@barryp.org> <3E029339.1050601@barryp.org> Content-Type: multipart/mixed; boundary="------------20A548C44F24CDBCB678D91E" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------20A548C44F24CDBCB678D91E Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Barry Pederson wrote: > > Oops, guess the 6103 is just a tranceiver, the 6102 is the controller - the > two go together. > > http://www.via.com.tw/en/datasheet/DS6103110.pdf > > which explains why the old EPIA boards show up as VT6102 in dmesg, even > though the website and manual only mentions VT6103. I think I'll shut up > now (but I'd still guess the EPIA-M networking is the same as the plain EPIA) Yeah, but it seems that there are some obscure differences between the integrated 6102 and the standalone 6102. Some reports saying that the integrated one can't connect to the 6103 (the PHY). I have looked at VIA's drivers and they are settning one bit to turn on the MII-interface (to the PHY). The attached patch does this, someone wants to try...? Please report the result (including an output of a 'pciconf -lv')! /thn -- --------------------------------------------------------------- Svensk Aktuell Elektronik AB Thomas Nyström Box 10 Phone: +46 8 35 92 85 S-191 21 Sollentuna Fax: +46 8 59 47 45 36 Sweden Email: thn@saeab.se --------------------------------------------------------------- --------------20A548C44F24CDBCB678D91E Content-Type: text/plain; charset=us-ascii; name="vr.patch.miion" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="vr.patch.miion" diff -u org/if_vr.c ./if_vr.c --- org/if_vr.c Thu Dec 19 19:51:51 2002 +++ ./if_vr.c Thu Dec 19 19:53:52 2002 @@ -739,6 +739,9 @@ /* Reset the adapter. */ vr_reset(sc); + /* Turn on bit2 (MIION) in PCI configuration register 0x53 during initialization */ + pci_write_config(dev, VR_PCI_MODE, pci_read_config(dev, VR_PCI_MODE, 4)|(VR_MODE3_MIION<<24), 4); + /* * Get station address. The way the Rhine chips work, * you're not allowed to directly access the EEPROM once diff -u org/if_vrreg.h ./if_vrreg.h --- org/if_vrreg.h Thu Dec 19 19:52:43 2002 +++ ./if_vrreg.h Thu Dec 19 19:53:47 2002 @@ -540,6 +540,9 @@ #define VR_PCI_MINLAT 0x0F #define VR_PCI_RESETOPT 0x48 #define VR_PCI_EEPROM_DATA 0x4C +#define VR_PCI_MODE 0x50 + +#define VR_MODE3_MIION 0x04 /* power management registers */ #define VR_PCI_CAPID 0xDC /* 8 bits */ --------------20A548C44F24CDBCB678D91E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message