Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAMS8qEVZFBFv4VpFtijxnR8Z5-wWFkpZx8nKOmbm6U-vah7eLg@mail.gmail.com>
 <20201023170003.GC3908702@gmail.com> <CAMS8qEX766tggsR0DpJm8TVRwctwwvnRofiiDWhqsNDDK6exYA@mail.gmail.com>
 <X62nDWQNHy1pk+3t@sol.localdomain>
In-Reply-To: <X62nDWQNHy1pk+3t@sol.localdomain>
From:   Konrad Dybcio <konradybcio@gmail.com>
Date:   Sat, 14 Nov 2020 14:16:13 +0100
Message-ID: <CAMS8qEUg2cC5L9Y9kfZkinL5+YfT_i_BQgTkVSy5eQN0zcNRCg@mail.gmail.com>
Subject: Re: Qualcomm Crypto Engine driver
To:     Eric Biggers <ebiggers@kernel.org>
Cc:     linux-crypto@vger.kernel.org, Satya Tangirala <satyat@google.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

> I'm already using your v5.10-rc3 branch, but ninges_defconfig isn't working for
> me.  (Though I couldn't find the firmware file "qcom/a530_zap.elf", so I had to
> remove it from CONFIG_EXTRA_FIRMWARE.)  Instead I'm using a kconfig based on
> https://github.com/SoMainline/linux/blob/marijn/android/arch/arm64/configs/defconfig
> which is working for me.

That's kind of expected, but Marijn's defconfig is fine. I just like
baking my firmware into the kernel for faster boot times.

> I haven't been able to get a full Android userspace to work, and currently I'm
> instead just replacing the kernel in a TWRP image and booting into recovery.
> It's enough to get adb shell access and chroot into a Debian chroot on the
> userdata partition, which is enough to run android-xfstests to test the ICE
> support.  Earlier I tried AOSP using the instructions at
> https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-android-11-0-0,

These instructions are meant for use with Sony Open Devices trees
available at github.com/sonyxperiadev, currently with CAF-based kernel
4.14.

> and also LineageOS using the instuctions at
> https://wiki.lineageos.org/devices/kirin/build

This one is for use with stock-based (BSP 4.4 kernel) trees.

> but neither worked.  That was a
> couple weeks ago though, so I haven't tried the very latest kernel with full
> Android.  Let me know if you have any suggestions!

First of all, you're going to need to retrieve gpu firmware (530
pfp/pm4 and 508 ZAP) like I do here (please flash the latest ODM image
from here to the oem partition [1] with fastboot) [2].

We are successfully booting Android but need multiple patches around,
in particular to enable A508 in Mesa (basically find "case 510:" and
add "case 508:" above it, like here [3]. For basic functionality,
we're working on proper 508/509/512 support) and the android device
trees aren't in the best state.. We're going to focus on these when
other components are ready.


Konrad

[1] https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-14-ganges/

[2] https://gitlab.com/postmarketOS/pmaports/-/blob/b249d76d95107c7eeaf64ef6b58c1dc08cf3ca2b/device/testing/firmware-sony-ninges/enable_firmware.initd

[3] https://github.com/SoMainline/mesa/commit/13c197d956a7bf1761242a7d29e1a43904ecc9b3