linux-kernel - Re: [PATCH] [96/106] iwlagn: Support new 5000 microcode.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Apr 2011 00:41:25 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	wwguy <wey-yi.w.guy@...el.com>
Cc:	Andi Kleen <ak@...ux.intel.com>,
	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
	Andi Kleen <andi@...stfloor.org>,
	"Fry, Donald H" <donald.h.fry@...el.com>,
	"sgruszka@...hat.com" <sgruszka@...hat.com>,
	"gregkh@...e.de" <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...nel.org" <stable@...nel.org>,
	"tim.bird@...sony.com" <tim.bird@...sony.com>
Subject: Re: [PATCH] [96/106] iwlagn: Support new 5000 microcode.

> iwlwifi-5000-5.ucode is target to fix a 11n related issue we seen in the
> field (especially for Ubuntu), so it is important for people to use -5
> version of uCode. in order to allow driver to pick up the correct uCode
> (-5), we need to move the maximum API version to "5" which is what this
> patch does

But this means that anyone who just updates the kernel without
having the new firmware will lose their wireless. Not good.
longterm is not supposed to break existing userland like this

Possible would be a patch to try 5 first and then fall back to 
the older version. But that's not what this patch does, correct?

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/