Date: Wed, 16 Nov 2016 11:02:49 -0800 From: Alexander Motin <mav@FreeBSD.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Intel 8265 Message-ID: <b099ceb0-54b5-9e52-d2cd-3e7b07de5593@FreeBSD.org> In-Reply-To: <CAJ-VmonD%2Bub1VdMS-keQV3RG9BA28Ts-VXPvnUggC6wSK5ihOQ@mail.gmail.com> References: <be978385-6250-f1b0-72fe-91fe45b07ef3@FreeBSD.org> <CAJ-VmonD%2Bub1VdMS-keQV3RG9BA28Ts-VXPvnUggC6wSK5ihOQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Without firmware this patch is not very significant and quite useless. All it does is adding new device ID and blocking logs about some firmware event spamming too heavy for real life use. But here is it, if you like: https://people.freebsd.org/~mav/iwm8265_nofw.patch That blocked even is not the only unclear message that driver logs, but it is much more noisy then everything else together. On 15.11.2016 11:40, Adrian Chadd wrote: > hiya, > > can you split out the firmware from the non-firmware bit? It's making > reading the diff kinda hard. :) > > On 11 November 2016 at 21:55, Alexander Motin <mav@freebsd.org> wrote: >> After buying new laptop including Intel 8265 WiFi I've found that it is >> not supported by the iwm driver. By adding the respective firmware and >> minor hacks to the driver I've made it kind of work: >> https://people.freebsd.org/~mav/iwm8265.patch >> >> It seems to be quite buggy right now now (though I am typing this over >> it). So if anybody is working on proper support for it, I'd be happy to >> try new patches. Thanks. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b099ceb0-54b5-9e52-d2cd-3e7b07de5593>