Date: Thu, 24 Jan 2019 14:31:07 +0800 From: Wen-Jun Guo <wjguo@cs.nctu.edu.tw> To: waddlesplash <waddlesplash@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: failed to initialize Intel 9560 wifi driver Message-ID: <CAFotSmhATrcALT5AnwWC17NoO9UwBE635dj9thkdYzQj9ZoOKA@mail.gmail.com> In-Reply-To: <CAEesM763c2wpHOqZjq-F-_b95QR7G7Xx5-b0xJ9Paj_p7xbs7g@mail.gmail.com> References: <CAFotSmimcu06CfUztxZhaXCW3B2V09-3Unzfv_wPvuXGCqCiEg@mail.gmail.com> <CAEesM763c2wpHOqZjq-F-_b95QR7G7Xx5-b0xJ9Paj_p7xbs7g@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Yes. I am checking the difference and fixing the model-specific code for the new family 9000. Still, the firmware still responds 0xdead. I saw your work makes iwm driver more consistent to Linux's iwl. I will rebase to it and continue my work. waddlesplash <waddlesplash@gmail.com> 於 2019年1月24日 週四 下午12:15寫道： > On Sun, Jan 20, 2019 at 6:52 AM Wen-Chun KUO <blockk2000@gmail.com> wrote: > > lwhsu and I are trying to add intel 9560 to iwm(4), the preliminary patch > > adds 9000 series firmware module and skeleton is here: > > Hi, > > I just submitted and kevans91 just merged a rather large (18 > individual commits) changeset of DragonFlyBSD changes (ivadasz' work, > not mine) which refactor quite a bit of iwm's firmware and device > state tracking code, and bring a lot of it closer to Linux's behavior. > This might be relevant to your work? > > -waddlesplash > -- Wen-Jun Guohelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFotSmhATrcALT5AnwWC17NoO9UwBE635dj9thkdYzQj9ZoOKA>