[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2af9b75a-b8f9-4ee8-efbe-53dd04365a18@somainline.org>
Date: Mon, 15 Nov 2021 11:26:02 +0100
From: Konrad Dybcio <konrad.dybcio@...ainline.org>
To: Trilok Soni <quic_tsoni@...cinc.com>,
~postmarketos/upstreaming@...ts.sr.ht
Cc: martin.botka@...ainline.org,
angelogioacchino.delregno@...ainline.org,
marijn.suijten@...ainline.org, jamipkettunen@...ainline.org,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/16] arm64: dts: qcom: Add support for Xperia 1 III / 5
III
On 14/11/2021 20:47, Trilok Soni wrote:
> Hi Konrad,
>
> On 11/13/2021 5:27 PM, Konrad Dybcio wrote:
>>
>> Then, you need to flash it on the device and get rid of all the
>> vendor_boot/dtbo mess:
>>
>> fastboot flash boot boot.img-sony-xperia-pdx215
>> fastboot erase vendor_boot
>> fastboot flash dtbo emptydtbo.img
>> fastboot reboot
>>
>> Where emptydtbo.img is a tiny file that consists of 2 bytes (all
>> zeroes), doing
>> a "fastboot erase" won't cut it, the bootloader will go crazy and
>> things will
>> fall apart when it tries to overlay random bytes from an empty
>> partition onto a
>> perfectly good appended DTB.
>
>
> I will check on this part and see if we can make simpler support
> fastboot erase dtbo without the extra emptydtbo.
>
> ---Trilok Soni
Hi Trilok,
that sounds great, thanks for looking into it! Could you also check why
using a boot.img header version 2 (with a dtb embedded into the boot
image using the --dtb option in mkbootimg) seems to be broken on 8350, too?
I get a "your device is corrupted and will not boot" error, even though
I disabled vbmeta/vbmeta_system and performed the same steps described
in this commit message to dtbo/vendor_boot. It worked fine on
4.19-release SoCs without vendor_boot (8250, 6350), but it seems it
doesn't anymore.
Konrad
Powered by blists - more mailing lists