Date: Mon, 10 Dec 2012 14:20:53 -0800 From: Adrian Chadd <adrian@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: husyh@hush.com, freebsd-current@freebsd.org Subject: Re: ath0: unable to attach hardware Message-ID: <CAJ-VmomM965-=QByhJZMPUn_PZAnSjafcm3cy3ojRaPc5fbWPg@mail.gmail.com> In-Reply-To: <201212101437.54825.jhb@freebsd.org> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212041106.50645.jhb@freebsd.org> <20121207095937.ECB38E6726@smtp.hushmail.com> <201212101437.54825.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, The fact the initial probe/attach fails by returning 0xffffffff means the chip isn't "right" on the bus. It's either just not mapped in correctly, or it's "powered off." If it were just asleep, it'd return 0xdeadc0de or 0xdeadbeef or something similar like that. Try AR_SCR (0x4004) and AR_PCICFG (0x4010) . Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomM965-=QByhJZMPUn_PZAnSjafcm3cy3ojRaPc5fbWPg>