From owner-freebsd-current@FreeBSD.ORG Fri Oct 8 17:02:32 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00FD1106566B for ; Fri, 8 Oct 2010 17:02:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id C6B2B8FC17 for ; Fri, 8 Oct 2010 17:02:31 +0000 (UTC) Received: by pxi17 with SMTP id 17so399345pxi.13 for ; Fri, 08 Oct 2010 10:02:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=w/xHa35DOVmvOtk2XxbzzKYHXbNPrxEDelru7/ZsT/M=; b=vEYNDVjz5UgUkPFOY3u+5mKO9hC4Cb22Wo3pUTEkBT8adXfCchnz79/Jarezz3B2G1 gpZ+SeGJ1NZHOH4fQJVDZAK/lcrSuUNn30AEv31inFDtgliT9sfol4AJ8N+UXceaXBdY 1frni5Xrcv1WlnFSixI5kpTLwd/Ui1IJOdXEE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=GZl74tZ2yZe6S7oScKHPHg+0Q8QuxpUUMGipdbIXUFUSrsnepSqWqT9IruMGTgXOf9 VOq0oFo9czp0eK8TKQYxfr6lfjv3+9HwmrLWw24p54d8vQbiVC62q2WGF3Ug4DsP7QEA gD7fNEON4fjBlvjVdGED2Z/NvtOWH8J3rRyx4= Received: by 10.142.13.19 with SMTP id 19mr2228183wfm.406.1286557351196; Fri, 08 Oct 2010 10:02:31 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id p8sm3914944wff.4.2010.10.08.10.02.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 08 Oct 2010 10:02:29 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 8 Oct 2010 10:00:46 -0700 From: Pyun YongHyeon Date: Fri, 8 Oct 2010 10:00:45 -0700 To: Mark Martinec Message-ID: <20101008170045.GA25411@michelle.cdnetworks.com> References: <201010081731.04127.Mark.Martinec+freebsd@ijs.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201010081731.04127.Mark.Martinec+freebsd@ijs.si> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Support for newer Ethernet chips in RE(4) driver? 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, 08 Oct 2010 17:02:32 -0000 On Fri, Oct 08, 2010 at 05:31:03PM +0200, Mark Martinec wrote: > The current re(4) Realtek Ethernet adapter driver supports the > 8139C+/8169/816xS/811xS/8101E chips, but lacks support for newer > Realtek network interface controllers such as RTL8111 C/E/D, > the RTL8168 series and some other. > Actually re(4) supports much more controllers than that. Man page needs updating to reflect this. > This is unfortunate as the RTL8111E and RTL8111D controllers > found their way (in singles or in pairs) into the current families > of GigaByte motherboards (such as GA-X58A-UD9/7/5/3R, GA-H55M*, ...), > and RTL8111C found its way into Asus motherboards (such as P6T), > and quite likely into other newer products. > RTL8111C/D/DP are supported. Because there are too many variants there might be some revisions which are not supported yet but I didn't see any other reports that request supports for newer RealTek controllers. > An updated re driver source for FreeBSD 8.0 is available from > the Realtek's web site ( http://www.realtek.com.tw/downloads/ ) > and claims to add support for chips and chipsets: > > RTL8111/RTL8111B/RTL8111C/RTL8111CP/RTL8111D(L)/RTL8111DP/RTL8111E > RTL8168/RTL8168B/RTL8168C/RTL8168CP/RTL8168D/RTL8168E > RTL8169S/RTL8169SB/RTL8169SC > RTL8101E/RTL8102E/RTL8103E/RTL8401E/RTL8105E > Specifically I don't know RTL8104E/RTL8105E controllers but others would be supported by re(4). > I tested the new Realtek driver with RTL8111E on FreeBSD 8.1-RELEASE, > works well. > Does stock re(4) fail to recognize your controller? If yes, please send me dmesg output(pciconf output is useless for RealTek controllers). > Any chance of importing the updated driver (or adding support I don't see any reason importing their driver. > for newer chips in some other way) into CURRENT so that it > could find its way to the 9.0 ? > As I said if your controller is not supported by re(4), show me more information about your controller.