Date: Wed, 02 May 2018 23:21:13 +0000 From: Adrian Chadd <adrian.chadd@gmail.com> To: freebsd@tim.thechases.com Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath0: could not map interrupt (again?) Message-ID: <CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw@mail.gmail.com> In-Reply-To: <20180502165745.59a5bfc4@bigbox.christie.dr> References: <20180502165745.59a5bfc4@bigbox.christie.dr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! I'm not sure. It should be able to map it as a shared interrupt because plenty of things could be downstream of that using a legacy interrupt. I wonder if it's being mapped as a shared interrupt. CAn you try booting freebsd-head and see if it's any better? -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw>