Date: Tue, 11 Dec 2012 15:49:49 -0500 From: John Baldwin <jhb@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: husyh@hush.com, freebsd-current@freebsd.org Subject: Re: ath0: unable to attach hardware Message-ID: <201212111549.49942.jhb@freebsd.org> In-Reply-To: <CAJ-VmomM965-=QByhJZMPUn_PZAnSjafcm3cy3ojRaPc5fbWPg@mail.gmail.com> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212101437.54825.jhb@freebsd.org> <CAJ-VmomM965-=QByhJZMPUn_PZAnSjafcm3cy3ojRaPc5fbWPg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, December 10, 2012 5:20:53 pm Adrian Chadd wrote: > 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, Look, it's up to you to look at more registers if you want to debug this further. PCI says everything is ok, so the ball is in your court. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201212111549.49942.jhb>