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>
index | next in thread | previous in thread | raw e-mail
> On Jun 8, 2023, at 6:34 PM, Adrian Chadd <adrian@freebsd.org> wrote: > > hm, does ath9k do a specific pci bus reset somewhere? Not that I’ve encountered but I’ll take another look. On a side note, is AH_DEBUG broken for anyone else or am I doing something wrong? I’m trying to get some of the built-in debug messages as well as adding my own but not having any luck. I’ve compiled it in and have ‘hw.ath.hal.debug=“0xffffffff”’ but never get any messages at boot and once I can log in the sysctl is set to 0. (ATH_DEBUG seems to work fine, but I need the HAL messages.) I’m running 14-CURRENT from a few weeks ago.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B0F165-F0A8-4221-BF44-1A3221192EFB>