Date: Sat, 10 Jun 2023 11:30:11 -0600 From: John Nielsen <lists@jnielsen.net> To: Adrian Chadd <adrian@freebsd.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, wireless@freebsd.org Subject: Re: Help me grok the ath(4) device attach code Message-ID: <43B0F165-F0A8-4221-BF44-1A3221192EFB@jnielsen.net> In-Reply-To: <CAJ-Vmom3o=3VS9x0f4HCuu_bgZZvpcXyfFVbSexvZ-DKj3q%2BPg@mail.gmail.com> References: <CAJ-Vmom3o=3VS9x0f4HCuu_bgZZvpcXyfFVbSexvZ-DKj3q%2BPg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Jun 8, 2023, at 6:34 PM, Adrian Chadd <adrian@freebsd.org> wrote: >=20 > hm, does ath9k do a specific pci bus reset somewhere? Not that I=E2=80=99ve encountered but I=E2=80=99ll take another look. On a side note, is AH_DEBUG broken for anyone else or am I doing something w= rong? I=E2=80=99m trying to get some of the built-in debug messages as well a= s adding my own but not having any luck. I=E2=80=99ve compiled it in and hav= e =E2=80=98hw.ath.hal.debug=3D=E2=80=9C0xffffffff=E2=80=9D=E2=80=99 but neve= r get any messages at boot and once I can log in the sysctl is set to 0. (AT= H_DEBUG seems to work fine, but I need the HAL messages.) I=E2=80=99m runnin= g 14-CURRENT from a few weeks ago.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B0F165-F0A8-4221-BF44-1A3221192EFB>