From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:11:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 76FA3BC0 for ; Mon, 1 Apr 2013 21:11:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by mx1.freebsd.org (Postfix) with ESMTP id 11D17188 for ; Mon, 1 Apr 2013 21:11:14 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id hn17so1914174wib.12 for ; Mon, 01 Apr 2013 14:11:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UmKcD4JJyP86PCiGrGlw61KlxlfT4CqtZmDEDm8alqU=; b=X7mTTRsFpAnHGAKCuQZYnVVKht6B/F0dEZhDIDhmILJDZftEwV389koKy4LvV+3dxJ Hk9FjvM7gsswukQpRIIo/8Vm0dkyjp2eQeJU84PNDDQ4irSr7tfgCCrLbk3UgWPkZMi8 0XFRzew9HiHXwAJbCHNrpM1TLod4G/oINxSDPZ5/Mn4/Nn+QZvruSyRqEDajn/WuaTeb TaZC4sBP34Iqz+gPU39XsxhyMRVAErQWwEQq+pNKiCXFSfLZY94FSuzx9/hcPOiRHh5C 0KH8F0kEup44oEYlb2cNvSssDAsMiZoAieaUwkWX1ze7dCWld5JR5c/CEZ+V3fRM0Gi/ 6K3g== MIME-Version: 1.0 X-Received: by 10.180.89.105 with SMTP id bn9mr11767122wib.26.1364850673922; Mon, 01 Apr 2013 14:11:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 14:11:13 -0700 (PDT) In-Reply-To: <5159F66B.2040600@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> Date: Mon, 1 Apr 2013 14:11:13 -0700 X-Google-Sender-Auth: SSz0gXMLFEqIVNJyU4z8o-NNsnc Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Apr 2013 21:11:15 -0000 update again again; I just did some TX related changes. adrian On 1 April 2013 14:04, Joshua Isom wrote: > I just tested it, the network problem's the same. > > > On 4/1/2013 3:22 PM, Adrian Chadd wrote: >> >> On 31 March 2013 15:24, Adrian Chadd wrote: >>> >>> The problem isn't contigmalloc, it's making sure that it gets bounced via >>> the local 32 bits of address space right. >>> >>> I'll talk with other developers and see what the deal is with 64 bit >>> address >>> space for 32 bit nics. >> >> >> Please do an svn update in sys/dev/ath/ and rebuild. >> >> I've fixed something in the RX side. I haven't yet gone and fully >> reviewed all the descriptor / buffer gymnastics on the TX side so it's >> very possible things will stay broken until I do that. >> >> Thanks, >> >> >> >> Adrian >> >