linux-kernel - Re: [PATCH] firmware: qcom: enable qseecom on Lenovo Yoga C630

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] [day] [month] [year] [list]

Message-ID: <CAA8EJpqaJQZaL3h2Eho4_HQ9Z8dLLYpwyOiyc0iFn_CzeWaG7Q@mail.gmail.com>
Date: Fri, 26 Jul 2024 13:43:04 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Johan Hovold <johan@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, 
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: qcom: enable qseecom on Lenovo Yoga C630

On Thu, 25 Jul 2024 at 14:38, Johan Hovold <johan@...nel.org> wrote:
>
> On Thu, Jul 25, 2024 at 02:27:39PM +0300, Dmitry Baryshkov wrote:
> > qseecom driver end uefi vars access works on the Lenovo Yoga C630.
>
> Really? Wasn't it the yoga where you could not write variables (you can
> try but they don't persist after a reboot)? Perhaps I'm confusing it
> with another machine.

No, you were right, I checked only the read operations and that write
succeeds, but I didn't check that writing persists across the reboot.
Either I will fix that, or I will post it as a read-only
implementation.



-- 
With best wishes
Dmitry