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:   Wed, 11 Apr 2018 23:04:06 +1000
From:   Ian W MORRISON <ianwmorrison@...il.com>
To:     Jani Nikula <jani.nikula@...ux.intel.com>
Cc:     rodrigo.vivi@...el.com, anusha.srivatsa@...el.com,
        michal.wajdeczko@...el.com, Greg KH <gregkh@...uxfoundation.org>,
        airlied@...ux.ie, joonas.lahtinen@...ux.intel.com,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake

On 11 April 2018 at 22:27, Jani Nikula <jani.nikula@...ux.intel.com> wrote:
> On Wed, 11 Apr 2018, Ian W MORRISON <ianwmorrison@...il.com> wrote:
>> <snip>
>>
>>>
>>> NAK on indiscriminate Cc: stable. There are zero guarantees that older
>>> kernels will work with whatever firmware you throw at them.
>>>
>>
>> I included 'Cc: stable' so the patch would get added to the v4.16 and
>> v4.15 kernels which I have tested with the patch. I found that earlier
>> kernels didn't support the 'linux-firmware' package required to get
>> wifi working on Intel's new Gemini Lake NUC.
>
> You realize that this patch should have nothing to do with wifi?
>

Yes. Runtime power management depends on the patch but when distros
such as Ubuntu are installed on a Intel Gemini Lake NUC as an example,
wifi/bluetooth depends on Intel Wireless-AC 9462 which in turn depends
on v4.15 as a minimum so my logic was to add the patch to 4.15 and later.

> Rodrigo, Anusha, if you think Cc: stable is appropriate, please indicate
> the specific versions of stable it is appropriate for.
>

Thanks you..

Best regards,
Ian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ