From owner-freebsd-net@freebsd.org Fri Oct 21 07:13:19 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE9CDC1A027 for ; Fri, 21 Oct 2016 07:13:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8652F8F4 for ; Fri, 21 Oct 2016 07:13:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 409671FE022; Fri, 21 Oct 2016 09:13:11 +0200 (CEST) Subject: Re: Adding RTL8153 support to rue(4) USB to Ethernet driver To: David Horwitt , freebsd-net@freebsd.org References: <5807B630.1060806@aogsquid.ucsd.edu> <3622755d-b0cd-60bf-0f81-469d06e65595@selasky.org> <58092C6D.8080105@aogsquid.ucsd.edu> From: Hans Petter Selasky Message-ID: <30de3b9c-98c4-0bbc-dce2-eddc52e98b10@selasky.org> Date: Fri, 21 Oct 2016 09:18:11 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <58092C6D.8080105@aogsquid.ucsd.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 07:13:19 -0000 On 10/20/16 22:43, David Horwitt wrote: > On 10/19/16 11:25, Hans Petter Selasky wrote: >> >> Hi, >> >> Search the idVendor and idProduct values in the Linux kernel. I think you need to implement some propritary miibus to >> get it working. CDC ethernet does not define any miibus. >> >> --HPS >> > Thank you for the quick response. > > Do you mean that I need to implement a small driver at VID:PID (0bda:8153 for this device) using cfg 0 to initialize the > built-in MII (using the Linux RTL8152/8153 driver as a model), and then switch to cfg 1 to use the CDC device for actual > operation? > No, I think the cfg 1 with CDC has the additional interface. Look at what the Linux driver does or get another ethernet adapter :-) --HPS