From owner-freebsd-current@FreeBSD.ORG Fri Dec 7 10:29:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF6D8455 for ; Fri, 7 Dec 2012 10:29:47 +0000 (UTC) (envelope-from husyh@hush.com) Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id AE36A8FC14 for ; Fri, 7 Dec 2012 10:29:47 +0000 (UTC) Received: from smtp1.hushmail.com (localhost.localdomain [127.0.0.1]) by smtp1.hushmail.com (Postfix) with SMTP id 3566F30240 for ; Fri, 7 Dec 2012 09:59:38 +0000 (UTC) Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp1.hushmail.com (Postfix) with ESMTP; Fri, 7 Dec 2012 09:59:38 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id ECB38E6726; Fri, 7 Dec 2012 09:59:37 +0000 (UTC) MIME-Version: 1.0 Date: Fri, 07 Dec 2012 10:59:37 +0100 To: "John Baldwin" , "Adrian Chadd" Subject: Re: ath0: unable to attach hardware From: husyh@hush.com In-Reply-To: <201212041106.50645.jhb@freebsd.org> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212041106.50645.jhb@freebsd.org> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20121207095937.ECB38E6726@smtp.hushmail.com> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2012 10:29:48 -0000 Hello, thank you for your answer. Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar with hardware specifics. During this mail conversion, I have heard abour BAR for the first time, and therefore, I know neither what exactly I should do (e.g. how I can find the start of bar, which register offsets would be interesting, etc.), nor what the results would tell me. I'm sorry if I'm tedious, but I would be very grateful if you could provide some more guidance. Thank you very much! On Dienstag, 4. Dezember 2012 at 7:43 PM, "John Baldwin" wrote: > >On Friday, November 23, 2012 5:56:02 pm Adrian Chadd wrote: >> Thanks for this! >> >> I'm sorry it hasn't gotten any more attention. I've cc'ed john >because >> he understands the PCI-PCI resource allocation stuff and I >currently >> don't; I'm hoping he can stare at this and see what's going on. >> >> But yes, if it were an ath(4) problem, the NIC would be returning >> 0xdeadbeef, 0xdeadc0de, etc. It wouldn't return 0xffffffff - that >> happens when there's nothing mapped at that address. >> >> The PCI config space that you've provided shows BAR(0) is >programmed >correctly.. > >Your dmesg shows that another device behind the same PCI-PCI >bridge is working >fine (fxp0), so the bridge is configured correctly. Also, the PCI >command >register for ath0 has memory decoding enabled, so everything >should be fine >from PCI's perspective. Note that if you want to examine specific >registers >you can use dd with /dev/mem (albeit carefully), e.g. > > dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) >count=1 | hd > >to read a single 32-bit register. I think that the card is in >fact returning >the value you see from its registers. I would do some reads of >other >registers using dd to see if all of the device registers are >returning -1 or >if only certain registers are. > >-- >John Baldwin