Date: Thu, 3 May 2018 19:45:36 -0500 From: Tim Chase <freebsd@tim.thechases.com> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath0: could not map interrupt (again?) Message-ID: <20180503194536.05c45884@bigbox.christie.dr> In-Reply-To: <CAJ-Vmok9T8KXeY_nnpr0n32moRL4r2H4EXk=GznNBdcOTv7FBw@mail.gmail.com> References: <20180502165745.59a5bfc4@bigbox.christie.dr> <CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw@mail.gmail.com> <20180502211001.550d290c@bigbox.christie.dr> <20180503192743.639240d0@bigbox.christie.dr> <CAJ-Vmok9T8KXeY_nnpr0n32moRL4r2H4EXk=GznNBdcOTv7FBw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-05-04 00:33, Adrian Chadd wrote: > Yeah it does look like that. I'm sorry, I don't have the > time/energy to figure out why allocating that interrupt doesn't > work on FreeBSD. :( If this is more of an interrupt/kernel thing than a wifi thing, would this be better moved to a different freebsd-*@ mailing-list? Perhaps freebsd-drivers@ ? -tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180503194536.05c45884>