From owner-freebsd-net@FreeBSD.ORG  Tue Feb 19 20:12:28 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 628A616A41A
	for <freebsd-net@freebsd.org>; Tue, 19 Feb 2008 20:12:28 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214])
	by mx1.freebsd.org (Postfix) with ESMTP id DF25F13C459
	for <freebsd-net@freebsd.org>; Tue, 19 Feb 2008 20:12:27 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (localhost [127.0.0.1])
	by alchemy.franken.de (8.14.1/8.14.1/ALCHEMY.FRANKEN.DE) with ESMTP id
	m1JJnTID052440; Tue, 19 Feb 2008 20:49:29 +0100 (CET)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.14.1/8.14.1/Submit) id m1JJnTNp052439;
	Tue, 19 Feb 2008 20:49:29 +0100 (CET) (envelope-from marius)
Date: Tue, 19 Feb 2008 20:49:29 +0100
From: Marius Strobl <marius@alchemy.franken.de>
To: Pyun YongHyeon <pyunyh@gmail.com>
Message-ID: <20080219194929.GA52364@alchemy.franken.de>
References: <200802190010.m1J0A3cb019526@freefall.freebsd.org>
	<20080219004543.GA18299@cdnetworks.co.kr>
	<20080219021315.GB11748@voi.aagh.net>
	<20080219025121.GC18299@cdnetworks.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080219025121.GC18299@cdnetworks.co.kr>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-net@freebsd.org, Thomas Hurst <tom@hur.st>
Subject: Re: kern/64556: [sis] if_sis short cable fix problems with NetGear
	FA311's
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2008 20:12:28 -0000

On Tue, Feb 19, 2008 at 11:51:21AM +0900, Pyun YongHyeon wrote:
> On Tue, Feb 19, 2008 at 02:13:15AM +0000, Thomas Hurst wrote:
>  > * Pyun YongHyeon (pyunyh@gmail.com) wrote:
>  > 
>  > > I thought nsphyter(4) may handle PHY hardware but ukphy(4) was used.
>  > > Just curious, would you let me know OUI/MII model/revision number of
>  > > PHY?(ukphy(4) prints that information in verbosed boot.)
>  > 
>  > ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus0
>  > ukphy0: OUI 0x080017, model 0x0002, rev. 1
>  > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>  > ukphy1: <Generic IEEE 802.3u media interface> PHY 0 on miibus1
>  > ukphy1: OUI 0x080017, model 0x0002, rev. 1
>  > ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> 
> That's odd. The OUI/Model number indicates NATSEMI(National
> Semiconductor), DP83815 PHY and nsphyter(4) should serve your PHY.
> CCed marius, the author of nsphyter(4) port, to get more information
> how this can happen.

Easy, in an earlier mail Thomas reported that he's running
7.0-RC2 and nsphyter(4) isn't in RELENG_7_0. :)

Marius