From owner-freebsd-current@FreeBSD.ORG Fri Dec 15 02:14:35 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3A2716A492 for ; Fri, 15 Dec 2006 02:14:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id E16A143CB3 for ; Fri, 15 Dec 2006 02:12:46 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by wr-out-0506.google.com with SMTP id i28so350567wra for ; Thu, 14 Dec 2006 18:14:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=nB0uphOEyaMT5uSCyrbP4gtEDMv6fiDUIXsIHGaw14Khjruu+7VvmNSEWmi20PtZKCjJQ8AYXRULwUJu/EyKWMkJcBBtKySztvSHZ8LF1uEUv9bEPqifBh5lEfkz89kcw9KZJso0EWyrAAYCu/XquqlAFedVXpq2pzomf23QvpE= Received: by 10.90.72.10 with SMTP id u10mr142162aga.1166148864696; Thu, 14 Dec 2006 18:14:24 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 67sm4243551wra.2006.12.14.18.14.22; Thu, 14 Dec 2006 18:14:23 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id kBF2EAhx026074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Dec 2006 11:14:10 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id kBF2EA9H026073; Fri, 15 Dec 2006 11:14:10 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 15 Dec 2006 11:14:10 +0900 From: Pyun YongHyeon To: Pascal Hofstee Message-ID: <20061215021410.GA25508@cdnetworks.co.kr> References: <45807C05.8040703@FreeBSD.org> <1166050020.1640.6.camel@chekov> <45808382.7000802@FreeBSD.org> <1166088126.1125.12.camel@chekov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1166088126.1125.12.camel@chekov> User-Agent: Mutt/1.4.2.1i Cc: "Bruce M. Simpson" , current@FreeBSD.org Subject: Re: D-Link DGE-350T and if_sk (no go) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2006 02:14:35 -0000 On Thu, Dec 14, 2006 at 10:22:06AM +0100, Pascal Hofstee wrote: > On Wed, 2006-12-13 at 22:49 +0000, Bruce M. Simpson wrote: > > Yes. It looks like (from dmesg) that your card is a Yukon 1. I think I > > managed to get the sk driver to attach to the PCI-e Yukon in my ASUS > > machine and had similar problems, though this was many months ago. The > > msk driver might work for you. > > Well .. i got around to trying the msk driver this morning and > unfortunately (after adding the pci-id to the msk driver) the card > probes, but doesn't attach because of the msk-driver rejecting > device-id's that are't Yukon II chips. (the if-section below in > if_msk.c) > > if (sc->msk_hw_id < CHIP_ID_YUKON_XL || > sc->msk_hw_id > CHIP_ID_YUKON_FE) { > > device_printf(dev, "unknown device: id=0x%02x, rev=0x%02x\n", > sc->msk_hw_id, sc->msk_hw_rev); > error = ENXIO; > goto fail; > } > > My DGE-530T however has id=0xb1, rev=0x09 which seems to be what if_msk > considers CHIP_ID_YUKON_LITE. So it looks that without further hacking > on the msk driver trying to use if_msk instead of if_sk is an excercise > in futility, though it was definitely worth a shot. > Please don't waste time. The msk(4) does not work for your DGE-530T. Yukon and Yukon II is completly different in hardware. That is main reason why I have to write msk(4) instead of adding Yukon II support code to sk(4). > I'll be watching the interrupts as soon as i can get a hold of my > neighbour which should probably be sometime later today. If in the > meanwhile people have other suggestions i might try, send them my way > and i'll give it a shot :) > It could be related with PHY which is under power down/uninitialized state. I'm still wonder why sk(4) doesn't work at all. -- Regards, Pyun YongHyeon