From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 20:22:01 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 D84475B6; Mon, 1 Apr 2013 20:22:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 480EFE75; Mon, 1 Apr 2013 20:22:01 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id z2so2117059wey.1 for ; Mon, 01 Apr 2013 13:22:00 -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=M3QvKlC8evi0DdE8KukHdLKeeMM4YThptTPAC2noCLY=; b=nP2E8cASbq+3SqFGZPnb63jCRtHrmv45F8XCvef8Ychg7nGlbDcb1lj9N3MQOv9Vi2 j3ZFr2nigPVOSE0SVM6Vuvie5NPphCLHgMBwQgu+KaLRJbXlpVcr/AjkNZvsxq2nemEn 0N/PMSV8dlW6MpjpKJyDaWpbNEmpnfxBYuJTt+8Kq2licQdVK2Boh7qEB7o/FEsB444y r+6o3moNfldbITyEgXMUCB0gajlAgEMENXI3mWEvbdSrU9houXb5+ZG5AUlaKjWhDb0J gpbh5QSwAZ9t9KdGlAZNXImiHttUvS04EuJ1CCUUBi8OfSA/4sPb+RqpqnN2TGbRv+ay Vh8w== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr17513938wjb.24.1364847720517; Mon, 01 Apr 2013 13:22:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 13:22:00 -0700 (PDT) In-Reply-To: <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> Date: Mon, 1 Apr 2013 13:22:00 -0700 X-Google-Sender-Auth: S3RlNUBWTOPuFaCfiZ-ja-8b9lE Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom , Adrian Chadd 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 20:22:01 -0000 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