From owner-freebsd-net@FreeBSD.ORG Tue Nov 16 22:46:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59F3216A4CE for ; Tue, 16 Nov 2004 22:46:27 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A04E43D60 for ; Tue, 16 Nov 2004 22:46:26 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAGMlLxv030916; Tue, 16 Nov 2004 14:47:21 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAGMlLO2030915; Tue, 16 Nov 2004 14:47:21 -0800 Date: Tue, 16 Nov 2004 14:47:21 -0800 From: Brooks Davis To: David Gilbert Message-ID: <20041116224721.GA30024@odin.ac.hmc.edu> References: <16789.23604.767942.781443@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <16789.23604.767942.781443@canoe.dclg.ca> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: Trendnet TU-ET100C X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 22:46:27 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 12, 2004 at 07:58:28PM -0500, David Gilbert wrote: > Has anyone seen, or is anyone working on a driver for the TrendNet > TU-ET100C ... which is a USB to Ethernet product. Alternatively, is > anyone working on a USB to Ethernet driver that's not yet in the tree? >=20 > Alternatively again, do USB drivers recognise themselves via product > numbers and is there a chance that there's a known chipset in there? > How might I tell? Odds are, it's supposed by one of the aue, cue, kue, or rue drivers. If you pry the case open you should be able to figure out which from reading the chips and looking in the driver sources. Once you know that, it's a fairly simple matter to add product and vendor ids to the driver. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBmoN4XY6L6fI4GtQRAoZHAKCNWfz8X7MGnRJhLA89h2Bz6/+IOgCgr490 TG+vjHXrEGZvwLERUKim7w0= =cJSU -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--