On 12 March 2015 at 07:02, Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: > Oleksij Rempel <linux@xxxxxxxxxxxxxxxx> writes: > >> Am 10.03.2015 um 16:35 schrieb Adrian Chadd: >>> Yeah, let's have it warn for a month or two. >>> >>> There's some pending work that will break the API with 1.3 firmware, >>> so it has to happen sooner rather than later. But yeah, maybe warn for >>> about a month would be good. the older firmware is still in the git >>> tree in case people want it. >> >> I'm not sure if warning patch will do the trick. >> Let me resend this patch in one or two months. Are you ok with it? >> Like Adrian said, there are pending patches (since 2013) which will >> brake compatibility with 1.3 > > Yeah, that's better. The crystall ball[1] says that 4.2 will be released > in August, that should be plenty of time for user space to catch up. So > if you resend this end of April or so the patch should go to 4.2. > > [1] http://phb-crystal-ball.org/ > *laugh* ok. i've just spoken with Linus about what should be done, and then Kyle for linux-firmware maintainer bits. The 1.3.1 firmware will appear again shortly, and then a new subdirectory with per-version firmware images. So moving forward ath9k_htc can just check to see if the newer firmware is available, and fall back to the older firmware if needs be. If earlier kernels are booted then the linux-firmware install will still have htc_{7010,9271}.fw as 1.3.1, so those kernels will still work. Now - as for how long the tip of ath9k_htc development should work with older firmware - that's a good question. I think yes, waiting a couple more months before merging it in so userspace can catch up is fine. Thanks! -a -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
