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]
Message-ID: <f41a692f-c3a4-4948-8179-4628542f90f6@oss.qualcomm.com>
Date: Mon, 19 Jan 2026 12:03:30 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
 <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Cc: Abel Vesa <abel.vesa@....qualcomm.com>
Subject: Re: [PATCH 0/2] arm64: qcom: Add SoC ID for CQ7790S

On 19/01/2026 11:50, Konrad Dybcio wrote:
> On 1/19/26 10:59 AM, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> This is early and first/initial posting for upstreaming Eliza SoC, e.g.
>> CQ7790S IoT variant. AFAIK, there is also CQ7790M variant with different
>> ID, but I do not have such hardware, thus only "S" goes here.
> 
> If you're sure about this marketing name being assigned to a specific
> SMEM ID, those *never* change after they're assigned, so it's fine if
> you just add it to the list

I don't know if I ever going to work on the M (modem) variant, so do you
want to document it just for completeness?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ