From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 04:08:39 2008 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 37BDD1065678 for ; Thu, 30 Oct 2008 04:08:39 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id EFF978FC26 for ; Thu, 30 Oct 2008 04:08:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so351760rvf.43 for ; Wed, 29 Oct 2008 21:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:subject:message-id:reply-to:mime-version:content-type :content-disposition:user-agent; bh=5kn/dUGhdaoPo62JIUfUVkKaxOcY5i/pbNKOQyXKmtg=; b=r6tN74svqc79CAR3r2f9vfqyx8u6t86AKXh8fquI9LjupC3+Pg1gi4lfhICkpxAIF2 P3YSHg63odq4S+/zogDlHCWNoC00DT//dFgnsAqnJCRiuLWsd4xTa8wZdLzqZFS9lTkE nqzwiYYXtz2zsEKNVaz8FsuB2R+o3jCx2Yu1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:reply-to:mime-version:content-type :content-disposition:user-agent; b=PSA6OOpGwbZ25XiwufqJ9+tOLJdwqDr+2TspXBPNkcFNSN0Ssl3QxcKO3YwWiTKvCa gDZbxcrodmYaab3FNjsLzKZTiWxk9mjbB/Faxwlvr0/2K8q9kmL8d/pkXKiqS3rljrJZ LwmH7yBhrmtTn2+kZwfCXfOLQI/ltdDaBHBKM= Received: by 10.141.68.12 with SMTP id v12mr5369871rvk.111.1225339718504; Wed, 29 Oct 2008 21:08:38 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id f21sm2204715rvb.5.2008.10.29.21.08.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 29 Oct 2008 21:08:37 -0700 (PDT) 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 m9U46b6t079527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Oct 2008 13:06:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m9U46bSO079526 for freebsd-current@FreeBSD.org; Thu, 30 Oct 2008 13:06:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 30 Oct 2008 13:06:37 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20081030040637.GA78796@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet 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: Thu, 30 Oct 2008 04:08:39 -0000 Hi, I had been working on writing a driver for Atheros AR8121(L1E), AR8113/AR8114(L2E) ethernet controllers since Jeremy Chadwick sent the hardware to me. I think it's feature complete state and time for more testing for stability or some edge cases. I guess AR81xx is commonly found on newer Asus EeePC or P5Q series of Asus motherboard. If you have AR81xx controller would you give it spin and let me know how it goes? You can get the latest driver at the following URL. http://people.freebsd.org/~yongari/ate/if_ate.c http://people.freebsd.org/~yongari/ate/if_atereg.h http://people.freebsd.org/~yongari/ate/if_atevar.h http://people.freebsd.org/~yongari/ate/Makefile or http://people.freebsd.org/~yongari/ate/ate.20081030.tar.gz The driver should build without problems on CURRENT, stable/7. ATM the driver supports the following hardware features. - TSO - Rx TCP/UDP/IP checksum offload - VLAN tag insertion/stripping - Jumbo frame - WOL It seems that hardware supports Tx checksum offload but I couldn't make it work for TCP segments. Only short TCP segments seem to work so I disabled Tx checksum offload. Note, the hardware does not support descriptor based DMA on Rx side so driver have to copy recevied frames to pass them to upper stack so it will consume a lot of CPU cycles if you push the hardware to the limit. Thanks. -- Regards, Pyun YongHyeon