From owner-freebsd-drivers@FreeBSD.ORG Fri Sep 26 01:19:46 2014 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33D30629; Fri, 26 Sep 2014 01:19:46 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 86574DE3; Fri, 26 Sep 2014 01:19:44 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s8Q1Hwkb061239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Sep 2014 09:17:59 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s8Q1Hwja061238; Fri, 26 Sep 2014 09:17:58 +0800 (CST) (envelope-from kevlo) Date: Fri, 26 Sep 2014 09:17:57 +0800 From: Kevin Lo To: Nils Beyer Subject: Re: Success with Qualcomm Atheros QCA8171 Message-ID: <20140926011757.GA61226@ns.kevlo.org> References: <3320661411119387@web21h.yandex.ru> <20140925094736.F2E71AE5@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140925094736.F2E71AE5@hub.freebsd.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-net@freebsd.org, freebsd-drivers@freebsd.org X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 01:19:46 -0000 On Thu, Sep 25, 2014 at 11:44:24AM +0200, Nils Beyer wrote: > > Hi Gulyaev, > > Gulyaev Ghosh wrote: > > Since I ask on the FreeBSD forums, there is a proposition to check > > alx-freebsd and have initialized interface. > > > > So if someone have similar hardware, you can got your experience with > > that project and share info. > > I've got an onboard "AR8161 Gigabit Ethernet" adapter. With your proposed GIT- > repository and using its branch "master" I'm able to rudimentarily use the > NIC. But only if the network cable is short (< 2m). Using longer cables gives > me a "no carrier" status. When it is connected, speed is abysmal and functio- > nality ceases as soon as I perform an "iperf" benchmark until I reboot. > > But for small data transfers (SSH, RSYNC, RDP) it's okay. Mark has done a good > job so far: > =============================================================================== > #dmesg | grep alx > alx0: port 0x2000-0x207f mem 0xd0400000-0xd043ffff irq 16 at device 0.0 on pci2 > alx0: Ethernet address: 5c:f9:dd:55:c9:fb > > #ifconfig alx0 > alx0: flags=8843 metric 0 mtu 1500 > ether 5c:f9:dd:55:c9:fb > inet6 fe80::5ef9:ddff:fe55:c9fb%alx0 prefixlen 64 scopeid 0x2 > nd6 options=29 > media: Ethernet autoselect > status: no carrier > > #pciconf -evl | tail -13 > alx0@pci0:2:0:0: class=0x020000 card=0x05621028 chip=0x10911969 rev=0x10 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR8161 Gigabit Ethernet' > class = network > subclass = ethernet > PCI-e errors = Correctable Error Detected > Non-Fatal Error Detected > Unsupported Request Detected > Non-fatal = Unsupported Request > Corrected = Bad TLP > Bad DLLP > REPLAY_NUM Rollover > Replay Timer Timeout > =============================================================================== AFAIK yongari@ is working on it. > Regards, > Nils Kevin