From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 1 17:23:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7BA7100 for ; Thu, 1 Nov 2012 17:23:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 789FE8FC16 for ; Thu, 1 Nov 2012 17:23:54 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1343205dad.13 for ; Thu, 01 Nov 2012 10:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=s6jkQcwh8J+GDG0eh2kTS/H5mZ1T2xBiWAo7xN9iaIQ=; b=xb5oBIqCSaQXHcpyvjXKAIqUhj8qKGyYXpwZWQDn488tiMUhyJufHgHqPqEIoF96LW aRBJ2hrFVEX02tdrBQLvWC/rtDaj8MHBI3XMIPPSmVjNaEtlGI4vZiccjl0dPr1RSkS0 Ee2GMvQcAinWgwP/d0VzNgFU3UVOiBDynbNdNArsyLRAOPapV6uHI+qoxQ0AV8xaLsOw roEk3511nGp679oTp2bOSet3whWsB20g3IMlPTluEkwUbNRqlXiVvnjvQXN1zy3hmyp2 StL/R9QzeExscSvHfownX+ckPwF0lYhFsOtBSxSVz/T3UgoUPsY7Qeu/pu/EW4hjABFc 0H2Q== MIME-Version: 1.0 Received: by 10.68.193.228 with SMTP id hr4mr122791560pbc.95.1351790627883; Thu, 01 Nov 2012 10:23:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Thu, 1 Nov 2012 10:23:47 -0700 (PDT) In-Reply-To: <20121101114634.DC1406F446@smtp.hushmail.com> References: <20121101114634.DC1406F446@smtp.hushmail.com> Date: Thu, 1 Nov 2012 10:23:47 -0700 X-Google-Sender-Auth: IfvgoYgc9SeojJZjs0j4CdFn3hs Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: husyh@hush.com 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: Thu, 01 Nov 2012 17:23:54 -0000 Hi, There doesn't seem to be any information about where in memory the ath NIC was mapped to in Linux. I'm not sure how to extract this information. I'm really sorry, I can't help out more than that, as it's very unlikely a driver problem. I've seen this before; the fact it's coming back with 0xffffffff means its not even correctly mapped at the address its supposed to be. Please try a recent -HEAD i386 and amd64 snapshot and if that doesn't work, you could try posting for help on freebsd-current. But please stress that I think it's a bus enumeration and PCI bridge programming problem, _not_ a driver problem. Thanks, Adrian