On Mon, Nov 04, 2019 at 05:11:07PM +0100, Stefan Sperling wrote:
> Great, thank you! Please keep running it and let me know if you come
> across anything wonky :-)
Everything has been stable since yesterday. No wonkiness observed! :D
--
Tracey Emery
On Mon, Nov 04, 2019 at 09:06:03AM -0700, Tracey Emery wrote:
> On Mon, Nov 04, 2019 at 04:56:14PM +0100, Stefan Sperling wrote:
> > If you want to test -34 you can copy the -34 firmware file on top of
> > the -22 file. (Keep a backup!)
> >
> > Alternatively, you could change the filename the
On Mon, Nov 04, 2019 at 04:56:14PM +0100, Stefan Sperling wrote:
> If you want to test -34 you can copy the -34 firmware file on top of
> the -22 file. (Keep a backup!)
>
> Alternatively, you could change the filename the driver will look for.
> The lines in if_iwm.c which would need to be
On Mon, Nov 04, 2019 at 08:31:07AM -0700, Tracey Emery wrote:
> Both diffs work fine here. However, it appears I'm still only loading
> the -22 firmware:
>
> iwm0: hw rev 0x230, fw ver 22.391740.0
>
> Am I missing something obvious to get it to load the -34 firmware, or do
> the two work in
Both diffs work fine here. However, it appears I'm still only loading
the -22 firmware:
iwm0: hw rev 0x230, fw ver 22.391740.0
Am I missing something obvious to get it to load the -34 firmware, or do
the two work in conjunction? I tried moving the -22 firmware out of the
way, but that caused a
This diff adds support for new iwm firmare's umac scan API.
It is required to make scanning work on -34 firmware.
Combined with the 'new ADD_STA' diff I just sent out, this is the last
change we need to get -34 firmware working.
This adds a couple of lines under #ifdef notyet for ax200 devices
